User guide

C-17
Cisco Media Gateway Manager 5.0 User Guide
OL-5461-02
Appendix C Troubleshooting
Topology Problems
Step 2 If the node table has alarm state of an MGX node as unreachable:
• Verify that the node is ipreachable from Cisco MGM
Ping the active ip address of the node. The active ip will be the ip address of the node that is populated
in the node table.
• Verify that the community string in the node_info table is the same as the community string on the
node. The community string of a node can be got using the CLI dspsnmp.
• Check nts logs to see if nts has declared the node as reachable. See C.15.1 NTS. If nts has declared
the node as reachable, check the topod.log for "nonRoutingNodeMsg" for this node. Verify that the
alarm status in this message is the correct alarm status
Defect Information—Collect the following information for further analysis:
• Save ILMITopoc.log, topod.log, NMServer.*.log, nts.*.log, ooemc*log
• Collect the dump outputs of ILMITopoc, topod and NMServer. The dump can be captured by issuing
a kill -USR1 signal to the process.
• Collect the output of the switch CLI, selnd and dbnds.
Possible alternative workaround—None
C.4.2.6 Cisco MGM State Is Incorrect
The management state of the node in the node table (column mgmt_state) shows as DOWN (2) or
UNKNOWN (0) even when the node is reachable by IP.
Step 1 Check the trap manager registration of the Cisco MGM station on the node.
Login to the node and do a "dsptrapmgr" to check if the particular Cisco MGM station has registered to
the node for traps. This is necessary for the node to be declared as manageable (mgmt_state = UP).
Step 2 Check the community strings of the node in the node-info table.
a. Enter the community strings (SNMP-GET and SNMP-SET) of the node through the Domain
Explorer GUIs "NE Authentication" tab. They may have been incorrect in the node-info table. This
can be verified if the decrypt tool for the encrypted strings in the database is available.
b. Check in NTS.log to see if trap registration has been successful for the node. See C.15.1 NTS.
Defect Information—Collect the following information for further analysis:
• Save ILMITopoc.log, topod.log and ooemc*.log
Possible alternative workaround—None