User guide

C-27
Cisco Media Gateway Manager 5.0 User Guide
OL-5461-02
Appendix C Troubleshooting
Equipment Management Problems
Defect Information—Collect ooemc log files and dbroker log files in /opt/svplus/log. Also collect config
upload files in /opt/svplus/tmp
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.5.1.8 Cisco MGM GUI Shows Mismatched Information Between GUI Views and DB Data
After OOEMC first time node resync such as coldstart, GUI views such as Network Monitor Tree View,
Inspector View, Chassis View etc. display information which is not matched to newly provisioned or
updated DB data. The problem persists even after each subsequent manual or periodic resync.
Step 1 For this issues, users have to determine which OOEMC process manages the node. We have discussed
in ISS: Node Mode Remains in 2 on how to find the child ID for the OOEMC process which manages
your node. The purpose of finding the child ID of the OOEMC process is to find the correct OOEMC
log files for inspection. The debugging process for this issue mainly focuses on log files inspection.
Step 2 After first time node resync such as coldstart, OOEMC will start sending newly provisioned or updated
DB data to NMServer. The current supported DB tables for NMServer message forwarding includes the
following
• node
• card
• line
• ausm_port
• cesm_port
• frp
• rpm_port
• svc_port
• virtual_port
• aps
• ima_group
• ima_link
• linedistribution
• au4tug3
• controller
• license_in_use
• mfr_bundle
• mfr_link
• peripheral
• redundantcard
• sensor