User guide

C-32
Cisco Media Gateway Manager 5.0 User Guide
OL-5461-02
Appendix C Troubleshooting
Equipment Management Problems
75. VxsmAal2CrossConn Trap
76. VxsmAal25DataProfileTrap
77. VxsmSensor Trap
78. VxsmSensorThrhd Trap
79. VxsmModule Trap
80. DS0Grp Trap
81. VxsmAnnounce Trap
82. VxsmAudioFile Trap
83. VxsmDs0XConn Trap
84. VxsmMegaco Trap
85. VxsmCrr Trap
86. VxsmTone Trap
87. VxsmAs Trap
88. VxsmAsp Trap
89. VxsmAs Trap
90. VxsmLapd Trap
91. VismABCDBitTemplate Trap
Of cause, you may need to study the log messages with "TRAPLIST" and decide how you can grep the
messages for your need. In the above example, there is another key word "PROCESSED" which
indicates that the trap has been processed. This gives you the starting point in the log file so that you can
study the log messages. if the DB is not populate correctly, then the subsequent log messages in the log
messages should provide you information on DB inconsistency problem. Some trap processing may
invoke SNMP data upload. From the log messages, you can verify whether or uploaded data is correct.
Other possible reasons for DB inconsistency are:
1. SNMP upload failure and maximum retrials exceeded, SNMP timeout, or throttle error. You can
verify the problem in snmpcomm log files
2. DB operation error. You can verify the problem in ooemc log files
If you do not know exactly what traps sequence is sent by switch to Cisco MGM, you should try a
working scenario and study the log for the trap sequence, or you can use HPOV to determine the trap
sequence.
Step 3 The previous step takes care of the cases that trap has been received and processed. The grep in the
previous step also allow you to find out whether traps have been received and has been buffered in the
trap queues, or related traps are not received at all. For the latter case, you need to refer to NTS logs to
verify whether traps have been received by NTS from switch and forwarded by NTS to OOEMC. If the
trap has been buffered in trap queue, the possible reasons are:
1. Node is syncing due to regular node resync or due to -2 trap.
2. Card is syncing and the trap is related to the card. The traps will buffered in queue until card resync
completes.
3. Summary alarm trap is processed. Summary alarm is being uploaded or parsed. You can grep the
log files for information related to summary alarm traps