User guide

C-22
Cisco Media Gateway Manager 5.0 User Guide
OL-5461-02
Appendix C Troubleshooting
Equipment Management Problems
C.5.1.3 Node Mode Remains in 1
The node has been discovered by network topology process in Cisco MGM and its node mode has been
changed from -1 to 1 in node table entry, but it stays in mode 1 for a long period of time.
Step 1 If the Cisco MGM stays in mode 1 for a long time after Cisco MGM core has been started, you need to
check the trap manger on the switch. See C.5.1.2 Network Setup and Configuration Required for
OOEMC Sync Up Process for trap manager and trap IP setup.
Step 2 If steps 1 is not an issue, then check for rtm link up message that NTS sends to EMD. OOEMC will start
node resync once EMD notifies OOEMC that the node is active. Therefore, the second step for
debugging this mode 1 problem is to see whether rtm link up message has been received by EMD and
whether it has been forwarded to OOEMC.
For example, to find out the rtm link up messages received by EMD for node with id 9, do the following
grep RTM_LINK_UP emd* | grep "Node id 9"
Once the location of the rtm link up message is found in the log, view the log file for more information
on notification to OOEMC
Step 3 If rtm link up message for the node is found and the log indicates that notification to OOEMC has been
sent, then collect log files and report the problem.
Step 4 If rtm link up message cannot be found, then search for link down message. Grep "RTM_LINK_DOWN"
from emd log files. If rtm link down message is found, then the node is not reachable to the NTS process.
Check with the network administrator and see C.15.1 NTS if "RTM_LINK_UP" and
"RTM_LINK_DOWN" messages are not found.
Defect Information—Collect ooemc and nts log files under /opt/svplus/log.
Possible alternative workaround—None
C.5.1.4 Node Mode Remains in 2
After rtm link up message has been received by EMD and node active message has been sent to OOEMC,
OOEMC will change the node mode from 1 to 2 and trigger node resync. Depending on the switch
configuration and network activities, the node resync time varies. If the node mode stays in mode 2 for
longer than the node resync normally takes, there can be the problem with node resync process.
Step 1 The debugging process for this problem is mainly focus on log file inspection. Make sure that log level
of all related Cisco MGM processes is set at right level. See C.5.1.2 Network Setup and Configuration
Required for OOEMC Sync Up Process Cisco MGM configuration.
Step 2 The first thing to check is "cd" to "/opt/svplus/tmp" to check for configuration upload files. For example,
if the node's node_id is 9, then do "ls -ltr *.9" to see what files have been uploaded for this node. If you
see some files have been uploaded for this node, then the node resync is still proceeding. Make sure that
the time stamps for these files refer to current time. Refer to step 6 for list of config upload files.
Step 3 If you don't see any file being uploaded from step 1, it is possible that the trap IP on the switch does not
match the IP that is being used for node discovery. Or there is SNMP request failure. First check the trap
IP. On the Cisco MGM, find the Managed IP that is used for node discovery by using Cisco MGM CLI
"dbnds". Then use switch CLI "dsptrapip" to display the trap IP. If there is mismatch, use switch CLI
"cnftrapip" to reconfigure the trap IP to the one that is used by Cisco MGM. See C.5.1.2 Network Setup
and Configuration Required for OOEMC Sync Up Process.