User guide

C-26
Cisco Media Gateway Manager 5.0 User Guide
OL-5461-02
Appendix C Troubleshooting
Equipment Management Problems
C.5.1.6 Cisco MGM DB Inconsistent With Switch Data After Successful Coldstart (Cisco MGM
Server stop/start) or Periodic Resync
After successful node resync triggered by periodic resync, the Cisco MGM DB is found inconsistent
with switch data.
Step 1 For this issues, what user can do is to collect ooemc log files and all config upload files for the node.
OOEMC implement node based cache. User can dump and save the cache. First the user need to find out
the process ID of the OOEMC process that manage the node by using the following commands:
The child ID is calculated from the following formula remainder (NEDBACCSSID / No. of OOEMC
child) + 1
Save config upload files and ooemc log files.
Defect Information—Collect ooemc log files in /opt/svplus/log. Also collect all 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.7 Cisco MGM CM GUI Shows Incomplete Connections After Successful Node Resync and
Dbroker Sync Up
After EM node resync triggered by coldstart or periodic completes successfully and dbroker sync up also
completes, the Cisco MGM CM GUI shows that some of connections are incomplete.
Step 1 For this issues, users have to determine which OOEMC process manages the node. OOEMC will manage
the connection segment in Cisco MGM DB which terminates on the MGX. 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 kind of issue mainly focuses on log files inspection.
Step 2 After you have identified the OOEMC log files, then grep "NotifyDataBroker" from the files to see some
log message examples before you can modify your grep format to more efficiently grep the pair of log
messages which corresponds to the local and remote ends of one end (master end point or slave end
point) of a connection segment. In other words, each end (either master end or slave end) of a connection
segment managed by OOEMC should be logged with one pair of messages: one for local end and one
for remote end, and this pair of messages correspond to one atm_connection segment entry in DB for
example. Now, you can verify the information that OOEMC sends to dbroker. DBROKER will base on
these messages from OOEMC and constructs user_connection DB entry. Cisco MGM CM GUI will
display connection with information from user_connection DB entry. Whether or not the connection will
be displayed as complete or incomplete depends on the information in user_connection DB entry.
Therefore, it is important to verify that OOEMC has sent correct information to DBROKER. Also verify
that the segment DB entries are populated correctly.
Step 3 If you have made sure that correct number of messages have been forwarded to DBROKER and the data
in the messages is correct, but the user_connection DB entry still contains invalid data, you should see
C.15.2 Data Inconsistency for more debugging information, or contact DBROKER DE for further
investigation. If the problem is due to wrong data populated in segment DB entries, then EM DE should
look at the problem.