Troubleshooting guide

33
Special Procedures
Step 3 If there is a redundant NP in this chassis, verify that the other NP is functioning as backup.
Enter the following command:
bash# rsh other-np /bin/true
The following results are possible:
• No error message
bash# rsh other-np /bin/true
bash#
This result indicates success. The other NP is up and accessible. Return to the section
that referred you to this Special Procedure (“Procedure 3, Change the Running Software
Version”).
• Connection timed out (the timeout takes about 75 seconds)
bash# rsh other-np /bin/true
other-np: connection timed out
bash#
This result indicates that the backup NP is not up. Go to Step 4.
• Permission denied
bash# rsh other-np /bin/true
Permission denied.
bash#
This result indicates that the backup NP is up, but not accessible because of a
permissions mismatch. Go to Step 4.
Step 4 The following error message may be generated (after about 75 seconds):
other-np: connection timed out
If this message is displayed, reset the other NP:
• Return to the TCS by typing ‘. (backquote plus dot, that is, left single quote plus period).
• Reset the backup NP by typing the following (substituting the slot number of the backup
NP for backup ):
TCS HUB<<A>>reset backup
• Connect to the backup NP by typing the following (substituting the slot number of the
backup NP for backup ):
TCS HUB<<A>>connect backup
• Monitor the reboot, looking for the following two trap messages:
==> (OPER) NDD_2 at mm/dd/yy/ hh:mm:ss <time-zone> (mm/dd/yy hh:mm:ss GMT)
Network Processor <node_name:slot> becoming backup np
==> (GENERIC) at mm/dd/yy/ hh:mm:ss <time-zone> (mm/dd/yy hh:mm:ss GMT)
Cold Start Trap at mm/dd/yy hh:mm:ss <time-zone> (mm/dd/yy hh:mm:ss GMT)
Note You may have to wait about 5 minutes for these traps to appear.
• Reconnect to the primary NP. Repeat Step 3. If the same failure occurs, call Cisco
Customer Support at 1-800-553-NETS (6387) or 1-800-553-2447.