Appendix J Troubleshooting
J.10.4 Equipment Management Problems
9.SM_CARD_01_RPM.CF
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
The following files are uploaded from the MGX NE. It includes VISM, AXSM, VXSM, SRM,
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 difference between the items in these lists is in the files uploaded for AXSM cards and
Step 8 In another scenario in which the node mode stays in 2 for a very long time, the parsing of one particular config upload file has taken a very long time and has not completed. To view the parsing process, enter the following command:
tail
Step 9 Collect the ooemc, nts, snmpcomm, and cwmftpd log files from the /opt/svplus/log directory.
Possible alternative
J.10.4.5 Node Resync Mode Is 5
Node mode 5 indicates that node resync has failed. This could be caused by the config upload or parsing failure of the shelf generic file (CARD_01_CC.CF.13, for example) or pnni file (PNNI_01_CC.CF.13, for example). In general, mode 5 signifies that a problem has happened in one or more stages of the entire resync process. The resync process is composed of the following stages and each stage alone can lead to mode 5 problems:
1.The ooemc triggers node resync.
2.The ooemc sends an SNMP request to the switch for bulk file creation.
Cisco Transport Manager Release 6.0 User Guide
|
| ||
|
|
