Troubleshooting NIC Data Resolution
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. See:
- SRC-PE Network Guide, Chapter 9, Locating Subscriber Information with the NIC
- SRC-PE Network Guide, Chapter 18, NIC Resolution Process
- SRC-PE Network Guide, Chapter 21, NIC Configuration Scenarios
This section presents high-level troubleshooting information. For assistance troubleshooting NIC operation and NIC resolutions, contact the Juniper Technical Support Center.
Troubleshooting NIC Operation
To troubleshoot NIC operation:
- Make sure that the heap size configured for NIC is adequate and that the process is up:
user@host>show nic statistics process
Component Statistics
Component Name processHeap in use 456194 bytes (87%)Heap limit 524288 bytesThreads 42Up time 747848 seconds since Wed Jan 31 19:35:57 EST 2007- Determine whether there are any NIC resolution errors and whether NIC successfully completed any resolution requests:
user@host>show nic statistics host
Component Statistics
Component Name /hostsNumber of Components Restart 0Number of No Match Resolutions 0Number of Resolution Errors 0Number of Resolutions 0- Test the resolution process by using the
test nic resolve
command.See SRC-PE Network Guide, Chapter 10, Configuring NIC with the SRC CLI.
Troubleshooting NIC Resolution
If you are unsure whether NIC is resolving resolution requests, you can 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 asdefault@sys1
for the key Vr, and the NIC value for that key such as the IOR that identifies an SAE.
- If NIC is not receiving data, determine which agent or agents are not receiving data by running the
show nic data
agent
command.