User guide

C-25
Cisco Media Gateway Manager 5.0 User Guide
OL-5461-02
Appendix C Troubleshooting
Equipment Management Problems
3. OOEMC will receive bulk file creation related traps: 60901, 60902, and 60903.
4. OOEMC will FTP config upload files from switch after it has received 60901 and 60902 from
switch.
5. OOEMC will parse the config upload files
6. OOEMC will declare sync up done.
When mode 5 problem occurs on one of the nodes, you should ask yourself the following questions:
1. Is the problem caused by SNMP request? What can I do?
You can grep "RESYNC" from the ooemc log files. OOEMC will change node mode to 2 when it starts
node resync. You should see something like the following from the log:
NOTICE: N17 <EMC_Node_c::InSync> SENDING RESYNC STATUS 2 FOR NODE 17 TO GUI - Node is
synchronizing.
This message tells you that OOEMC will start node resync for node with ID equal to 17 (N17). If you
look further in the log, you should see log messages related to SNMP request and SNMP response. If the
SNMP request is successful, the switch will responds to the request. The OOEMC will then process the
SNMP response by invoking response function which may do nothing:
<EMC_SnmpFunc_c::ProcFunc_GenNodeBulkFile_1> entering
If the log messages indicate SNMP error, refer to snmpcomm log files for more failure information.
2. Is the problem caused by bulk creation traps? What can I do?
You can grep "60901", "60902", and "60903" from the log files. See C.5.1.3 Node Mode Remains in 1
for more information. Anyway, you should see something like the following:
INFO: <EMC_TrapClientImpl::onIncomingTrap> NTS NodeId 17 genericTrap 6 specificTrap 60901
INFO: <EMC_TrapClientImpl::onIncomingTrap> NTS NodeId 17 genericTrap 6 specificTrap 60902
3. Is the problem is caused by config file FTP? What can I do?
You can get "FTP" or "to ftp" plus config upload file name. You should see something like:
NOTICE: N17 <EMC_NodeFsmHandler_c::LoadShelf> to ftp /opt/svplus/tmp/CARD_01_CC.CF.17
INFO: <ParseFile_c::CheckFile> OOEMC9 CHECKSUM OK FOR FTP FILE
/opt/svplus/tmp/CARD_01_CC.CF.17
These messages indicate that FTP is successful and there is no checksum error in the file. Also from the
log file, you should able to find out if there is FTP problem. Then you should refer to cwmftpd log files
for more failure information.
4. Is the problem caused by shelf generic file or pnni file parsing? what can I do?
After you have located the starting pointing of checksum checking for shelf generic file
(CARD_01_CC.CF.17 for example) or pnni file (PNNI_01_CC.CF.17 for example), continue to trace
the log messages to see whether or not parsing error has occurred. If there is not error, you should see
the following:
INFO: N17 <EMC_NodeFsmHandler_c::FinishShelf> Parse /opt/svplus/tmp/CARD_01_CC.CF.17
successfully.
Defect Information—Collect ooemc log files, nts log files, snmpcomm log files, and cwmftpd log files
under /opt/svplus/log. Also collect config upload files in /opt/svplus/tmp
Possible alternative workaround—None