The NIC does not resolve a request.
Troubleshooting NIC data resolution is a complex task that requires a good understanding of how NIC operates, how it resolves resolution requests, and how the NIC configuration scenario that you are using performs resolutions.
This topic provides high-level troubleshooting information. For further assistance troubleshooting NIC operation and NIC resolutions, contact the Juniper Technical Support Center.
Troubleshoot NIC operation:
user@host> show nic statistics process
Component Statistics Component Name process Heap in use 456194 bytes (87%) Heap limit 524288 bytes Threads 42 Up time 747848 seconds since Wed Jan 31 19:35:57 EST 2007
user@host> show nic statistics host
Component Statistics Component Name /hosts Number of Components Restart 0 Number of No Match Resolutions 0 Number of Resolution Errors 0 Number of Resolutions 0
If you are unsure whether NIC is resolving resolution requests, view data about those requests to see whether NIC is receiving data.
See Viewing Data for NIC Resolvers .
For each resolver, which is identified by a component name such as /realms/login/C1, the output should show a value, such as default@sys1 for the key Vr, and the NIC value for that key such as the IOR that identifies an SAE.
- [edit shared nic scenario OnePop]
- user@host# show