Restore A Previously Halted Card; Verifying Network Connectivity - Cisco ASR 5500 Administration Manual
Asr 5500 system administration guide, staros release 19
Hide thumbs
Also See for ASR 5500:
- System administration manual (430 pages) ,
- Installation manual (192 pages) ,
- Installation procedure overview (6 pages)
Table of Contents
Advertisement
Troubleshooting
Follow the instructions below to manually initiate a card halt. These instructions assume you are at the root
prompt for the Exec mode.
Step 1
Initiate a manual card migration by entering the following command:
host_name
[local]
slot# is the chassis slot number in which the card to be halted is installed. It can be any integer from 1 through 4, and 7
through 18. You will receive the following prompt:
Are You Sure? [Yes|No]:
Step 2
Press Y to initiate the halt operation.
Step 3
Verify that the migration was successful by entering the show card table command at the Exec mode prompt.
Check the entry in the Oper State column next to the card that was just halted. Its state should be Offline. If the card was
in active mode prior to the execution of this command, the state of the redundant component associated with it should
now be Active.
Restore a Previously Halted Card
Follow the instructions below to restore a card that was previously halted. These instructions assume you are
at the root prompt for the Exec mode.
Step 1
Reboot the card to be restored by entering the following command.
host_name
[local]
You will receive the following prompt:
Are You Sure? [Yes|No]:
Step 2
Press Y to start the reboot of the card.
Step 3
Verify that the migration was successful by entering the show card table command at the prompt.
Check the entry in the Oper State column next to the card that was just restored. Its state should be the state of that it
was in before it was halted.
Verifying Network Connectivity
There are multiple commands supported by the system to verify and/or troubleshoot network connectivity.
Note that network connectivity can only be tested once system interfaces and ports have been configured and
bound.
The commands specified in this section should be issued on a context-by-context basis. Contexts act like
virtual private networks (VPNs) that operate independently of other contexts. Ports, interfaces, and routes
configured in one context cannot be tested from another context without additional configuration.
card halt slot#
#
card reboot slot# -force
#
ASR 5500 System Administration Guide, StarOS Release 19
Verifying Network Connectivity
171
Advertisement
Table of Contents
Troubleshooting
