J-43
Cisco Transport Manager Release 6.0 User Guide
78-16845-01
Appendix J Troubleshooting
J.10.4 Equipmen t Management Problems
Note It should not take long to declare node resync failure because of the SNMP request failure. To
verify that there is an SNMP failure, check the ooemc and snmpcomm log files.
Note Using ooemc10.6568.log as an example of an ooemc log filename, 10 is the child ID, the 6568
is the ooemc process ID. The child ID is calculated from the following formula: Remainder
(NEDBACCSSID / number of ooemc child) + 1. To retrieve the process ID, use the CLI
command psg em.
Step 6 Grep RESYNC from the log file. The grep result should include the node ID and node mode. Review the
log messages in the log file to determine if an SNMP failure has occurred.
Step 7 Do the following:
a. Check the log file for trap 60903. If you find it, contact the platform team to investigate the bulk file
creation failure on the switch.
Very often, the node mode 2 problem is caused by a bulk file creation abort process on the switch.
If there are no SNMP request failures, 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 the ooemc receives a trap 60902, it will start to FTP the bulk file, which is a
shelf generic configuration file. This is also the first file to be uploaded in every resync mode
(coldstart, warmstart, or periodic resync.) The commonly seen mode 2 problem is that the switch
will abort the bulk file creation and send trap 60903 to CTM. CTM will reschedule the next SNMP
request unless it exceeds maximum retries.
b. Check the log file for trap 60902.
CARD_01_CC.CF.10. This file is a shelf generic file and is the first file to be uploaded after CTM
receives trap 60902 from the switch. The 10 is the node ID. If you find trap 60902 in the log file but
no config file has been uploaded after a reasonable amount of time, it is possible that the FTP failed.
To find out if FTP failure has occurred, do the following:
a. Grep “to ftp file" and the config filename, or just "FTP" from the log files.
b. Trace the log messages in the log file.
For a more detailed information on SNMP request failure and FTP failure, check the snmpcomm and
cwmftpd log files and the cwmftp.request_log. Search for the filename at the time the error
happened in both files. The cwmftp.request_log gives the summary or final result of the FTP
operation, and any error is reported. The cwmftp.log shows the FTP operation details.
CTM will upload and parse a set of config files from the switch. The following files are uploaded from
the MGX NE, which contains 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