User guide

C-23
Cisco Media Gateway Manager 5.0 User Guide
OL-5461-02
Appendix C Troubleshooting
Equipment Management Problems
Step 4 If the trap IP is not an issue, then check whether there is SNMP request failure. Normally, after node
resync is triggered, OOEMC will send SNMP request to the switch to start configuration upload file
creation. If the request fails, then OOEMC will retry SNMP request until it exceeds maximum retrials
and declares node resync failure with node mode equal to 5. However, it shouldn't take very long to
declare node resync failure because of the SNMP request failure. To verify that there is SNMP failure,
you can start with ooemc log files and then proceed to check snmpcomm log files.
The child ID is calculated from the following formula remainder (NEDBACCSSID / No. of OOEMC
child) + 1
The file name format of OOEMC log file is given as ooemc10.6568.log for example. The "10" in the
example is the "child" ID, The "6568" in the examples is the OOEMC process ID which you can obtain
by using typing "psg em" at Cisco MGM CLI.
The starting point of log file inspection is to grep "RESYNC" of the log file. The grep result should
include node_id and node mode. Once you have locate the starting point in the file, open the file and
read the content after this starting point in the file. More or less, the log messages in the file should
provide you some information whether SNMP failure has occurred.
Step 5 Very often, the node mode 2 problem is caused by bulk file creation abort on the switch. Referring to
the discussion in step 4, if there is no SNMP request failure, the switch should send traps 60901 and
60902 to OOEMC. Trap 60901 indicates that the switch will start bulk file creation, while trap 60902
indicates bulk file creation done. When OOEMC receives trap 60902, it will start FTP the bulk file which
is shelf generic configuration file in this case. This is also the first file to be uploaded for every resync
mode, whether it is coldstart, warm start or periodic resync. The commonly seen mode 2 problem is that
the switch will abort the bulk file creation and send trap 60903 to Cisco MGM. Cisco MGM will
reschedule the next SNMP request unless it exceeds maximum retrials. Whenever you find trap 60903
periodically in the log file, you should contact platform team to investigate the bulk file creation failure
on the switch.
Step 6 To take CARD_01_CC.CF.10 as an example. This file is shelf generic file and is the first file to be
uploaded after Cisco MGM has received 60902 trap from the switch. The "10" in the example is the
node_id. If you find 60902 in the log file but no config file has been uploaded after a reasonable amount
of time, it is possible that the FTP has failed. By greping "to ftp file" and the config file name, or just
"FTP" from the log files, and by tracing the log messages in the log file, you should be able to tell
whether or not FTP failure has occurred. For more detail information of SNMP request failure and FTP
failure, inspect "snmpcomm" and "cwmftpd" log files Look into cwmftp.log and cwmftp.request_log.
Search for the file name at the time the error happened in both files. The cwmftp.request_log gives the
summary/final result of the FTP operation and any error is reported. The cwmftp.log shows the step by
step details about the FTP operation.
Cisco MGM will upload and parse a set of config files from the switch. The following lists the files
uploaded from MGX NE.It includes VISM, AXSM, VXSM, SRM, and RPM/RPM-PR cards:
1. CARD_01_CC.CF
2. SM_1_slot#.CF
3. SM_1_slot#.CS
4. SM_CARD_01_slot#.CF
5. SM_CONN_01_slot#.CF
6. SM_ALARM_01_slot#.CF
7. SM_CON_UPDATE_01_slot#.CF
8. SM_CARD_01_SRM.CF
9. SM_CARD_01_RPM.CF