User guide

C-115
Cisco Media Gateway Manager 5.0 User Guide
OL-5461-02
Appendix C Troubleshooting
Miscellaneous Problems
Step 3 Check the Trap Manager List on the switch. SSH or Telnet to the switch. Run "dsptrapmgr" command
to show the trap manager list. Check whether the Cisco MGM is in the table. If so, go to Step. 4.
Otherwise, if the table is already full, remove unwanted entries with "deltrapmgr" command. The NTS
should be able to register the Cisco MGM into the table within a few minutes. If not, go to Step. 4.
Step 4 Check the SNMP community strings. In case the SNMP Community String on the switch has been
changed from the default setting, the SNMP Community Strings on the Cisco MGM have to match the
new ones on the switch. The SNMP Community Strings on the switch can be viewed with "dspsnmp"
command. The setting on the Cisco MGM can be viewed in Domain Explorer.
Defect Information—Collect the following information for further analysis:
• Save the output of "selnd", "dbnds", nts log and EM log of the node in question. < see EM log
section>
Possible alternative workaround—If community strings do not match, run the Cisco MGM Configurator
GUI to correct them. (/opt/svplus/java/bin/runConfigurator)
Related key index entries: nts, traps
C.15.1.2 Config Change or Provisioning Activity Not Reflected on Cisco MGM
The NTS does not receive any traps from a particular switch when it actually had generated traps.
Step 1 Check if the node is in OK state. If the ntsControl node information says the particular node is not in the
OK state, see C.15.2.1 Connection Inconsistency Between the Switch and GUI. If the node is indeed in
OK state, go to Step 2.
Step 2 Check the Trap IP address setting on the switch. The Trap IP address has to be the primary IP address
of the switch. Otherwise, NTS cannot correlate the trap with the Cisco MGM node information and has
to discard that trap. SSH or Telnet to the switch. The primary IP address can be found with "dspndparms"
and then "dspifip" commands. Enter "dsptrapip" to see the current Trap IP address setting. Use
"cnftrapip" to correct. See C.15.1.3 How To Interpret NTS Log.
Defect Information—None
Possible alternative workaround—None
Related key index entries: nts, traps
C.15.1.3 How To Interpret NTS Log
Locating a specific trap from a particular node in NTS log.
Step 1 Verify Trap Handling
NTS log has information about what are the traps delivered to a specific client. NTS by default keeps 20
old logs in addition to the current one. You can form your "grep" command with the key fields such as
node id, trap number, client name and pid. For example:
( 21359: 63) 19:24:40 WARNING: N42 Trap(6, 50017, #15668881) to EMC-5-24596
The above line says NTS delivered Node 42 Trap 50017 Sequence Number 15668881 to EMC child 5
PID 24610.