User guide

C-33
Cisco Media Gateway Manager 5.0 User Guide
OL-5461-02
Appendix C Troubleshooting
Configuration Center, Chassis View, Diagnostic Center and Statistics Report Problems
To verify that the trap has been put into queue, you can do the following
grep EMC_TrapQueue_c::append ooemc_log | grep trap_num
You should see something like the following:
INFO: <EMC_TrapQueue_c::append> entering. ======> append trap# 60303 to trap queue;
getHdlrLevel=5, getTrapLevel=5, #=174
Defect Information—Collect ooemc log files, nts log file, and snmpcomm log files under
/opt/svplus/log.
Possible alternative workaround—User can manually resync the node. If the problem persists, user
should try coldstart. If the problem is still not able to be resolved, collect log files and report the problem.
C.6 Configuration Center, Chassis View, Diagnostic Center and
Statistics Report Problems
This section includes the following information:
• C.6.1 Cisco MGM Configuration Center, Chassis View, Diagnostic Center or Statistics Report
Basics
• C.6.2 Basic Issues
• C.6.3 Topology Discovery Issues
• C.6.4 Network Element Discovery Issues
• C.6.5 Configuration Center, Chassis View, Diagnostic Center or Statistics Report GUI Alarm Issues
C.6.1 Cisco MGM Configuration Center, Chassis View, Diagnostic Center or
Statistics Report Basics
Cisco MGM manages MGX NEs. The Topology module discovers the nodes and trunks. Once the nodes
are discovered, the EM module syncs up with the nodes to discover the card, line, port, etc. All the
discovered nodes, trunks and its elements are published by NMServer, which in-turn are displayed in the
Configuration Center, Chassis View, Diagnostic Center or Statistics Report GUIs. The Configuration
Center, Chassis View, Diagnostic Center or Statistics Report GUIs have Tree View, Inspector View. The
Tree View and Inspector View are shared by Configuration Center, Diagnostic Center, Finder, Statistics
Report and Chassis View GUIs. The Tree View and InspectorView feed-off the data published by
NMserver.
Cisco MGM is notified of all subsequent changes in the network through traps.
Figure C-1 shows the end-to-end architecture.