60
Catalyst6000 Family Network Analysis Module Installation and Configuration Note
78-10406-05
Troubleshooting the NAM
Symptom The user is unable to start the Traffic Director capture after using the NAM Traffic Analyzer
application capture with a large buffer size.
Possible Cause All of the buffer space available for capture sessions was requested and allocated for
capture sessions using the NAM Traffic Analyzer application (or the reverse). If you are using more
than one entity to simultaneously request NAM resources, such as the NAM Traffic Analyzer
application, and the external SNMP managers, such as nGenius RTM or Traffic Director, be sure that
you balance the resource allocations.
Recommended Action Do not request the maximum capture buffer size in one application and then
expect additional buffers available when interacting with the NAM from another application. Only
enable autostart when it is required. Autostart can consume more resources than just enabling
collections on specific data sources instead of all data sources. Ensure that only the specific capture
buffers and collections required are enabled on the NAM. Use the clear config and reboot commands
from the NAM CLI and then restart the applications for capture sessions that you want with minimum
buffer allocations. The NAM Traffic Analyzer application also shows all collections enabled on the
NAM in the Admin/Diagnostics/Monitor and Capture Configuration screen.
Symptom The user receives a verification failed message when installing a patch on the NAM.
Possible Cause The time and date on the NAM are not correct, or the patch is not the same as an
official Cisco patch. The FTP process may have failed, or the FTP image being pointed to is not a
patch (It may be a full application image.)
Recommended Action The signature verification used to ensure that the patch is an authentic patch
requires an accurate time and date on the NAM and only accepts official Cisco patches.
Symptom When a NAM is running in a switch with the Catalyst OS, the NAM may be shown as
unreachable by using the ping command or NAM Traffic Analyzer.
Possible Cause The NAM IP address and the IP address of the switch (interface sc0) are not in the
same subnet. This problem can occur if you change the switch IP address and the NAM VLAN
assignment. The NAM will automatically synchronize its VLAN assignment to the same VLAN in
which the switch (interface sc0) resides. When this occurs, the NAM IP address resides on a different
subnet than the VLAN assigned to the NAM. The router then drops any packet destined to the NAM
IP address. You cannot add a static route to the router because of route overlap caused by improper
VLAN assignments and subnetting.
Recommended Action Make sure the NAM IP address and the switch are in the same subnet and in the
same VLAN.
Symptom Cannot enable the HTTP server.
Possible Cause The NAM could not determine the server’s fully qualified domain name.
Recommended Action Reboot the NAM.