User guide

C-24
Cisco Media Gateway Manager 5.0 User Guide
OL-5461-02
Appendix C Troubleshooting
Equipment Management Problems
10. PNNI_01_CC.CF
Files 1 and 2 are uploaded for each NBSM. Files 4 to 7 are uploaded for each AXSM. File 9 is uploaded
for all RPM/RPM-PR cards on the switch.
The following list the files uploaded from MGX NE for VISM, AXSM, VXSM, SRM, RPM/RPM-PR,
and RPM-XF 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_SC_slot#_transactionID_date.CF
9. SM_IC_slot#_transactionID_date.CF
10. SM_CARD_01_SRM.CF
11. SM_CARD_01_RPM.CF
12. PNNI_01_CC.CF
The different between these two lists is on the files uploaded for AXSM cards and RPM-XF card. For
switch running 4.0 or above switch software, static file (SM_SC_slot#_transactionID_date.CF) and
incremental file (SM_IC_slot#_transactionID_date.CF) are uploaded, but for switch running 3.0 or
lower switch software, conn, alarm and conn update files are uploaded for each AXSM. Files 4 to 7 in
the second list are uploaded for each RPM-XF card, and file 11 is uploaded for all RPM/RPM-PR cards
on the switch.
Step 7 Another scenario that the node mode stays in 2 for very long time is because the parsing of one particular
config upload file has taken very long time and has not completed yet. You can "tail" the ooemc log file
by doing "tail -f ooemc_log_file" and get a feeling on what is going on with the parsing.
Defect Information—Collect ooemc log files, nts log files, snmpcomm log files, and cwmftpd log files
under /opt/svplus/log.
Possible alternative workaround—None
C.5.1.5 Node Resync Mode is 5
Node syncup failure with mode 5
Step 1 Node mode 5 indicates that node resync fails. This could be caused by the config upload or parsing
failure of shelf generic file (CARD_01_CC.CF.13 for example) or pnni file (PNNI_01_CC.CF.13 for
example). For the upload issue, in ISS: Node Mode Remains in 2 we have touched on the "mode 5" issue.
Refer to that section for more debugging information. In general, mode 5 signifies that problem has
happened on one or more stages of the whole resync process. You can think of the resync process being
composed of the following stages and each stage alone can lead to mode 5 problem:
1. OOEMC will trigger node resync.
2. OOEMC will send SNMP request to switch for bulk file creation