User guide

C-29
Cisco Media Gateway Manager 5.0 User Guide
OL-5461-02
Appendix C Troubleshooting
Equipment Management Problems
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.2 Cisco MGM DB and Switch Data Inconsistency Issues After Node
Provisioning for MGX
This section includes the following information:
• C.5.2.1 DB Table Population Through Traps and SNMP Upload
• C.5.2.2 Switch Data Does Not Match With Cisco MGM DB Table After Node Provisioning
C.5.2.1 DB Table Population Through Traps and SNMP Upload
Except for node and/or card resync, another mechanism that Cisco MGM OOEMC uses to populate the
DB table entries is through trap processing and followed by snmp upload if necessary. User can
provision the switch through switch CLI, Cisco MGM GUI or Cisco MGM service agents. All three
cases will involve trap processing and snmp upload on OOEMC. Only connections can be provisioned
by Cisco MGM CM GUI. Other provisioning such as line, port etc. have to go Cisco MGM service
agents. Of cause, switch CLI can do both.
C.5.2.2 Switch Data Does Not Match With Cisco MGM DB Table After Node Provisioning
After switch provisioning through switch CLI, Cisco MGM GUI or Cisco MGM service agent, the
switch data does not match to Cisco MGM DB.
Step 1 If the issue is caused by trap, for example, if user provisions a connection on a switch or through
Cisco MGM GUI or service agent, and the Cisco MGM does not populate the DB entry or the
information in the DB entry does not match with switch data, it is possible that the trap is not received
by Cisco MGM. Or the trap is received by Cisco MGM, but it is buffered in the trap queues of OOEMC
and the processing of the trap will be delayed. On the other hand, if the data in Cisco MGM DB is not
correct, it is also possible that the SNMP upload fails to upload correct data. In any case, we need to
study the log files and understand the root cause of the inconsistency problem.
Step 2 There are some key words in ooemc log files that you can grep and determine whether or not trap is
received and processed. For example, to find out the channel traps from node_id=4, slot = 6, vpi = 1 and
vci = 326, you can grep "TRAPLIST" as shown in the following:
cwmult60% grep "TRAPLIST: N4:" ooemc* | grep "Channel Trap" | grep "C6" | grep "vpi 1 vci
326"
ooemc10.5760.log.old.55:( 5760: 10) 23:21:12 INFO: TRAPLIST: N4: Channel Trap 60310 from
C6 B2 L1 P20 Ch299 ifIndex 17176597 vpi 1 vci 326 upCntr 0 vpcFlag 2 operS 1 alarm 67
ooemc10.5760.log.old.55:( 5760: 10) 23:21:12 INFO: TRAPLIST: N4: Channel Trap 60310 <
PROCESSED > from C6 B2 L1 P20 Ch299 ifIndex 17176597 vpi 1 vci 326 upCntr 0 vpcFlag 2
operS 1 alarm 67
ooemc10.5760.log.old.73:( 5760: 10) 23:23:48 INFO: TRAPLIST: N4: Channel Trap 60310 from
C6 B2 L1 P20 Ch299 ifIndex 17176597 vpi 1 vci 326 upCntr 0 vpcFlag 2 operS 1 alarm 66