Table Of Contents
Upgrading and Downgrading ROM Monitor Firmware on the Cisco ASR 9000 Series Aggregation Services Routers
Information About ROM Monitor Firmware
About ROMMON A and ROMMON B
Upgrading or Downgrading a Single Node or All Nodes
Reloading Nodes After a ROM Monitor Firmware Change
Upgrading or Downgrading ROM Monitor Using the FPD PIE
Prerequisites
Troubleshooting Tips
Configuration Examples for ROM Monitor Upgrades
ROM Monitor Upgrade: Example
Graceful Reload of a Cisco ASR 9000 Series Router: Example
Additional References
Related Documents
Technical Assistance
Upgrading and Downgrading ROM Monitor Firmware on the Cisco ASR 9000 Series Aggregation Services Routers
This module describes how to upgrade or downgrade the ROM Monitor firmware on a Cisco ASR 9000 Series Aggregation Services Router.
This chapter contains the following sections:
•
Information About ROM Monitor Firmware
•
Upgrading or Downgrading ROM Monitor Using the FPD PIE
•
Configuration Examples for ROM Monitor Upgrades
•
Additional References
Information About ROM Monitor Firmware
The ROM Monitor, which is also known as ROMMON, is a bootstrap program that initializes the hardware and boots the Cisco IOS XR firmware when you power on or restart a Cisco ASR 9000 Series Router. ROM Monitor upgrades can be required to resolve firmware defects or support new features. Typically, ROM Monitor upgrades are infrequent and not required for every Cisco IOS XR software upgrade.
Before upgrading or downgrading ROM Monitor firmware, you should understand the following concepts:
•
About ROMMON A and ROMMON B
•
Upgrading or Downgrading a Single Node or All Nodes
•
Upgrading or Downgrading ROM Monitor Using the FPD PIE
Tip
Information on operating the router in ROM Monitor mode is provided in the "ROM Monitor Overview".
About ROMMON A and ROMMON B
Each node in a Cisco ASR 9000 Series Router includes two copies of ROM Monitor: ROMMON A and ROMMON B. During power on, ROMMON A loads first. If ROMMON A detects the presence of ROMMON B, it checks the compatibility and integrity of the ROMMON B code. If ROMMON B passes these tests, ROMMON A passes control of the router to ROMMON B.
You can only upgrade ROMMON B. When you upgrade ROMMON B, the router uses the unmodified ROMMON A if the ROM Monitor upgrade is interrupted or fails for any reason.
Upgrading or Downgrading a Single Node or All Nodes
The upgrade and downgrade procedures for ROM Monitor firmware are the same. Install a higher version to upgrade the firmware, or a lower version to downgrade the firmware.
ROM Monitor operates on every node within the Cisco ASR 9000 Series Router. During an upgrade or downgrade, the ROM Monitor firmware is copied into hardware EEPROMs in the router.
For most upgrades, we recommend upgrading or downgrading the ROM Monitor firmware on all nodes. You can also upgrade or downgrade a single node, which is useful when moving a card between two routers, adding a card that is not running the correct ROM Monitor version, inserting a new card in the chassis, or migrating to a later Cisco IOS XR software release.
Reloading Nodes After a ROM Monitor Firmware Change
The new ROM Monitor firmware is not active on a node until the card is reloaded. For example, if you upgrade a single node, you must reload that node only after the upgrade. If you upgrade or downgrade all nodes, you must also reload all nodes to activate the new ROM Monitor version.
To gracefully reload all nodes, reload the standby RSP, perform a redundancy switchover, reload the second RSP, and then reload all other nodes in the system.
If the router does not contain a redundant standby RSP, or if you wish to perform a cold restart, you can also reload all nodes at the same time. Remember that a cold restart results in router downtime while the cards reboot.
Instructions to reload the nodes are included in the "Upgrading or Downgrading ROM Monitor Using the FPD PIE" section.
Upgrading or Downgrading ROM Monitor Using the FPD PIE
The field-programmable devices (FPDs) are hardware devices implemented on router cards that support separate software upgrades. A field-programmable gate array (FPGA) is a type of programmable memory device that exists on most hardware components of a router. The term FPD describes any type of programmable hardware device on Serial Interface Processors (SIPs) and shared port adapters (SPAs), including FPGAs. Cisco IOS XR software provides the Cisco FPD upgrade feature to manage the upgrade of FPD images on SIPs and SPAs. Refer to the Upgrading FPD on Cisco IOS XR Software module in the Cisco ASR 9000 Series Aggregation Services Router System Management Configuration Guide for more information on upgrading FPDs.
The following procedure upgrades or downgrades the ROM Monitor firmware using the ROM Monitor image contained in the FPD software package installation envelope (PIE). This section also includes instructions to reload a node, gracefully reload all nodes in the system, or perform a cold restart for all nodes in the system.
Note
We recommend upgrading one card at a time. After each upgrade, you should see a message indicating that the upgrade was performed successfully. Reload the card only after the upgrade finishes successfully.
If you are not sure if a card requires a ROM monitor upgrade, you can install the card and use the show hw-module fpd location <node-id> command to determine if the ROM monitor image on the card is compatible with the currently running Cisco IOS XR software release.
Prerequisites
Before upgrading or downgrading ROM Monitor firmware, verify that the FPD PIE is installed on your router. See the Upgrading and Managing Cisco IOS XR Software module in Cisco ASR 9000 Series Aggregation Services Router System Management Configuration Guide for more information on installing software PIEs.
SUMMARY STEPS
1.
show hw-module fpd location all
2.
admin
3.
show fpd package
4.
upgrade hw-module fpd rommon location [all | node-id]
5.
exit
6.
If you are upgrading a single node on a router, including a standby RSP, go to Step 9.
7.
If you are upgrading a router with redundant RSPs, and want to perform a graceful reload, go to Step 10.
8.
If you are upgrading a router with a single RSP, or want to perform a cold restart on all nodes, go to Step 11.
9.
Reload a single node:
a.
hw-module location node-id reload
b.
Go to Step 12.
10.
Gracefully reloads the redundant RSPs followed with all nodes on a system:
a.
cfs check
b.
hw-module location node-id reload
c.
show redundancy
d.
redundancy switchover
e.
show redundancy
f.
admin
g.
show platform
h.
hw-module location node-id reload
i.
Repeat Step h. to reload all upgraded nodes in the system.
j.
show platform
11.
Reload all nodes in a system (cold restart):
a.
cfs check
b.
admin
c.
reload location all
12.
show platform
DETAILED STEPS
| |
Command or Action
|
Purpose
|
Step 1
|
show hw-module fpd location all
Example:
RP/0/RSP0/CPU0:Router# show hw-module fpd
location all
|
Displays the current FPD image versions for all cards installed in the router. Use this command to determine if you must upgrade the ROM monitor image on your cards.
|
Step 2
|
admin
Example:
RP/0/RSP0/CPU0:Router# admin
|
Enters administration EXEC mode from EXEC mode.
|
Step 3
|
show fpd package
Example:
RP/0/RSP0/CPU0:Router(admin)# show fpd
package
|
(Optional) Displays which cards are supported with your current Cisco IOS XR software release, which FPD or ROM monitor image you need for each card, and what the minimum hardware requirements are for the cards. If there are multiple FPD images for your card, use this command to determine which FPD image to use if you want to upgrade only a specific FPD type.
|
Step 4
|
upgrade hw-module fpd rommon location
[all | node-id]
Example:
RP/0/RSP0/CPU0:Router(admin)# upgrade
hw-module fpd rommon location 0/RSP1/CPU0
|
Upgrades the ROMMON B images on the specified card (node-id) or all cards (all).
Note Before you continue to reload the card, you should see a message indicating that the upgrade was completed successfully.
|
Step 5
|
exit
Example:
RP/0/RSP0/CPU0:Router(admin)# exit
|
Exits administration EXEC mode and returns to EXEC mode.
|
Step 6
|
If you are upgrading a single node on a router, including a standby RSP, go to Step 9.
|
Continues to reload the node.
|
Step 7
|
If you are upgrading a router with redundant RSPs, and want to perform a graceful reload, go to Step 10.
|
Continues to gracefully reload all nodes.
|
Step 8
|
If you are upgrading a router with a single RSP, or want to perform a cold restart on all nodes, go to Step 11.
|
Continues to perform a cold restart of all nodes.
|
Step 9
|
Reload a single node:
hw-module location node-id reload
Go to Step 12.
Example:
RP/0/RSP0/CPU0:router#
hw-module location 0/RP1/CPU0 reload
|
Reloads a single node within a router, such as a standby RSP. The new ROM Monitor firmware is not active on a node until the card is reloaded.
Replace node-id with the node ID you specified when upgrading ROM Monitor.
Go to Step 12 to verify that the correct ROM Monitor firmware is active on each node.
|
Step 10
|
a. cfs check
b. hw-module location node-id reload
c. show redundancy
d. redundancy switchover
e. show redundancy
f. admin
g. show platform
h. hw-module location node-id reload
i. Repeat step h. to reload all upgraded nodes in the system.
j. show platform
|
Gracefully reloads the redundant RSPs followed with all nodes on a system. The new ROM Monitor firmware is not active on a node until the card is reloaded.
a. (Optional) Use cfs check command to ensure the sanity of the configuration file system for the default-SDR.
b. Reload the standby RSP to activate the new ROM Monitor firmware. Specify the node-id of the standby RSP .
Wait till the standby RSP fully boots.
c. Use the show redundancy command to verify the redundancy status of the RSPs. Wait for the standby RSP to return to "Ready" state.
d. Use the redundancy switchover command to cause the primary (active) RSP to fail over to the redundant standby RSP. The control switches over to the standby RSP.
Note The standby RSP must be ready to take over.
e. Use the show redundancy command to verify the status of the RSPs. Wait for the standby RSP to return to ready state.
|
| |
Example:
RP/0/RSP0/CPU0:router# cfs check
RP/0/RSP0/CPU0:router#
hw-module location 0/RSP1/CPU0 reload
RP/0/RSP0/CPU0:router# show redundancy
RP/0/RSP0/CPU0:router# redundancy
switchover
RP/0/RSP0/CPU0:router# show redundancy
RP/0/RSP0/CPU0:router# admin
RP/0/RSP0/CPU0:router(admin)# show
platform
RP/0/RSP0/CPU0:router(admin)# hw-module
location 0/1/CPU0 reload
RP/0/RSP0/CPU0:router(admin)# hw-module
location 0/2/CPU0 reload
RP/0/RSP0/CPU0:router(admin)# hw-module
location 0/SM0/SP reload
RP/0/RSP0/CPU0:router(admin)# hw-module
location 0/SM1/SP reload
RP/0/RSP0/CPU0:router(admin)# hw-module
location 0/SM2/SP reload
RP/0/RSP0/CPU0:router(admin)# hw-module
location 0/SM3/SP reload
RP/0/RSP0/CPU0:router(admin)# show
platform
|
f. Use the admin command to enter administration EXEC mode.
g. Use the show platform command to view all the nodes in the system. Enter this command in administration EXEC mode to display information for all nodes in the system, including admin plane resources.
h. Use the hw-module location node-id reload command to reload each additional card where the ROM Monitor firmware was changed. Each node must be reloaded to activate the new ROM Monitor firmware.
Replace node-id with the node ID you specified when upgrading ROM Monitor.
i. Use the hw-module location node-id reload command to reload all upgraded nodes in the system.
j. Use the show platform command to view all the nodes in the system. Verify that all the reloaded nodes are in the "IOS XR RUN" state.
|
Step 11
|
Reload all nodes in the system (cold restart):
a. cfs check
b. admin
c. reload [location all]
Example:
RP/0/RSP0/CPU0:router# cfs check
RP/0/RSP0/CPU0:router# admin
RP/0/RSP0/CPU0:router(admin)# reload
location all
|
Reloads all nodes, including the RSP. Use these commands if you are upgrading a router with a single RSP, or wish to perform a cold restart of all nodes. The new ROM Monitor firmware is not active on a node until the card is reloaded.
Caution  Reloading the primary RSP interrupts all service.
a. (Optional) Use the cfs check command to ensure the sanity of the configuration file system for the default-SDR.
b. Enters administration EXEC mode.
c. Use the reload location all command in administration EXEC mode to reload all nodes in the system.
|
Step 12
|
show platform
Example:
RP/0/RSP0/CPU0:Router# show platform
|
Verifies that the ROM monitor image on the card has been successfully upgraded by displaying the status of all cards in the system.
|
Troubleshooting Tips
This section provides the troubleshooting tips for the upgrade procedure:
•
If any node cannot be upgraded successfully, if you do not receive a message indicating a successful upgrade, or if you see error messages similar to the following message, try reformatting the bootflash (format bootflash: [location all | node-id]) and then repeat this upgrade procedure:
LC/0/3/CPU0:rommon_burner[65635]: %ROMMON_BURNER-3-FILE_OP_ERR : Opening ROMMON flash
partition failed: No such file or directory in function main at line 952
•
If you are upgrading ROMMON B and the version does not change to the expected version after the upgrade, the upgrade might have failed. When the router cannot load ROMMON B, it loads ROMMON A.
If ROMMON A is used for any card in the router, following SYSLOG message is displayed during system boot up:
LC/0/5/CPU0:Nov 5 12:29:12.311 : rommon_fpd_agent[202]: rommon instance 0 has image A
programmed. Upgrade the possibly corrupt image B using "upgrade hw-module fpd" CLI in
admin mode.
•
If both ROMMAN B and ROMMON A are damaged due to an unexpected node reset or a power interruption during the upgrade, the affected route processors must be returned to Cisco for repair.
•
If a lower version of the ROM Monitor is detected based on the version check performed during system boot, following error message is displayed:
RP/0/RSP1/CPU0:Nov 19 07:19:02.628 : rommon_fpd_agent[308]:
%PLATFORM-UPGRADE_FPD-4-DOWN_REV : lc rommon instance 0 is down-rev (V0.63), upgrade
to (V0.64). Use the "upgrade hw-module fpd" CLI in admin mode.
Configuration Examples for ROM Monitor Upgrades
This section provides the following configuration examples:
•
ROM Monitor Upgrade: Example
•
Graceful Reload of a Cisco ASR 9000 Series Router: Example
ROM Monitor Upgrade: Example
The following example shows how to display ROM monitor image information for all cards in the router:
RP/0/RSP1/CPU0:router(admin)# show hw-module fpd location all
================================================================================
Existing Field Programmable Devices
==========================================
Location Card Type Version Type Subtype Inst Version Dng?
============ ======================== ======= ==== ======= ==== =========== ====
0/RSP0/CPU0 A9K-RSP-4G 4.8 lc fpga3 0 1.18 No
--------------------------------------------------------------------------------
0/RSP0/CPU0 ASR-9010-FAN 1.0 lc cbc 1 4.00 No
--------------------------------------------------------------------------------
0/RSP0/CPU0 ASR-9010-FAN 1.0 lc cbc 2 4.00 No
--------------------------------------------------------------------------------
0/RSP0/CPU0 A9K-BPID2-10-SLOT 1.0 lc cbc 3 7.00 No
--------------------------------------------------------------------------------
0/RSP1/CPU0 A9K-RSP-4G 4.8 lc fpga3 0 1.18 No
--------------------------------------------------------------------------------
0/1/CPU0 A9K-4T-L 1.0 lc fpga1 0 0.42 No
--------------------------------------------------------------------------------
0/1/CPU0 A9K-4T-L 1.0 lc fpga1 1 0.42 No
--------------------------------------------------------------------------------
0/2/CPU0 A9K-2T20GE-B 1.0 lc fpga1 0 0.42 No
--------------------------------------------------------------------------------
0/2/CPU0 A9K-2T20GE-B 1.0 lc fpga1 1 0.42 No
--------------------------------------------------------------------------------
0/3/CPU0 A9K-SIP-700 0.31 lc fpga1 0 0.22 No
--------------------------------------------------------------------------------
0/3/0 SPA-5X1GE-V2 4.255 spa fpga1 0 1.10 No
--------------------------------------------------------------------------------
0/3/1 SPA-2XCHOC12/DS0 1.0 spa rommon 1 2.02 No
--------------------------------------------------------------------------------
0/4/CPU0 A9K-8T/4-L 1.0 lc fpga1 0 0.42 No
--------------------------------------------------------------------------------
0/4/CPU0 A9K-8T/4-L 1.0 lc fpga1 1 0.42 No
--------------------------------------------------------------------------------
0/6/CPU0 A9K-40GE-L 1.0 lc fpga1 0 0.42 No
--------------------------------------------------------------------------------
0/6/CPU0 A9K-40GE-L 1.0 lc fpga1 1 0.42 No
--------------------------------------------------------------------------------
The following example shows how to upgrade the ROM Monitor image when a lower version of ROM Monitor firmware is detected. In the example, the ROM Monitor image for the 0/RSP1/CPU0 node ID is updated:
RP/0/RSP0/CPU0:router(admin)# upgrade hw-module fpd rommon location 0/RSP1/CPU0
- The upgrade operation of the target module will not interrupt its normal
operation. However, for the changes to take effect, the target module
will need to be manually reloaded after the upgrade operation. This can
be accomplished with the use of "hw-module <target> reload" command.
- If automatic reload operation is desired after the upgrade, please use
the "reload" option at the end of the upgrade command.
- The output of "show hw-module fpd location" command will not display
correct version information after the upgrade if the target module is
Starting the upgrade/download of following FPD:
=========== ==== ======= ======= =========== =========
Location Type Subtype Upg/Dng Version Version
=========== ==== ======= ======= =========== =========
0/RSP1/CPU0 lc rommon upg 0.63 0.64
------------------------------------------------------
RP/0/RSP1/CPU0:Nov 19 07:24:11.553 : lc_fpd_upgrade[243]: %PLATFORM-UPGRADE_FPD-6-START :
Starting to upgrade rommon subtype image from 0.63 to 0.64 for this card on location
0/RSP1/CPU0
RP/0/RSP1/CPU0:Nov 19 07:24:11.561 : rommon_fpd_agent[308]: Start Upgrade...
RP/0/RSP1/CPU0:Nov 19 07:24:11.561 : rommon_fpd_agent[308]: Programming fpd instance
0...with file
/net/node0_RSP0_CPU0/dev/shmem/asr9k-fpd-3.7.2.10I/fpd/ucode/rommon-viking-8641d-rsp2-B.bi
n
RP/0/RSP1/CPU0:Nov 19 07:24:21.098 : lc_fpd_upgrade[243]: %PLATFORM-UPGRADE_FPD-6-PASSED :
Successfully upgrade rommon subtype image for this card on location 0/RSP1/CPU0
% Successfully upgraded 1 FPD for A9K-RSP-4G-HDD on location 0/RSP1/CPU0
The following example shows reload of the 0/RSP1/CPU0 node:
RP/0/RSP0/CPU0:router(admin)# hw-module location 0/RSP1/CPU0 reload
WARNING: This will take the requested node out of service.
Do you wish to continue?[confirm(y/n)] y
RP/0/RSP0/CPU0:Nov 19 07:26:45.060 : shelfmgr[323]: %PLATFORM-SHELFMGR-6-USER_RESET : Node
0/RSP1/CPU0 is reset due to user reload request
RP/0/RSP0/CPU0:Nov 19 07:26:51.866 : shelfmgr[323]: %PLATFORM-SHELFMGR-6-NODE_STATE_CHANGE
: 0/RSP1/CPU0 card type:1049346 nstate:ROMMON
RP/0/RSP0/CPU0:Nov 19 07:27:11.153 : shelfmgr[323]:
%PLATFORM-SHELFMGR_HAL-6-BOOT_REQ_RECEIVED : Boot Request from 0/RSP1/CPU0, Rommon
Version: 0.64
RP/0/RSP0/CPU0:Nov 19 07:27:11.155 : shelfmgr[323]: %PLATFORM-SHELFMGR-6-NODE_STATE_CHANGE
: 0/RSP1/CPU0 card type:1049346 nstate:MBI-BOOTING
RP/0/RSP0/CPU0:Nov 19 07:29:26.661 : shelfmgr[323]: %PLATFORM-SHELFMGR-6-NODE_STATE_CHANGE
: 0/RSP1/CPU0 card type:1049346 nstate:IOS XR RUN
RP/0/RSP0/CPU0:Nov 19 07:29:52.066 : redcon[303]: %HA-REDCON-1-STANDBY_READY : standby
card is ready
Verify the upgrade using the show hw-module fpd location all command, as shown in the following command:
RP/0/RSP0/CPU0:router(admin)# show hw-module fpd location all
===================================== ==========================================
Existing Field Programmable Devices
==========================================
Location Card Type Version Type Subtype Inst Version Dng?
============ ======================== ======= ==== ======= ==== =========== ====
0/RSP0/CPU0 A9K-RSP-4G 4.8 lc fpga3 0 1.18 No
--------------------------------------------------------------------------------
0/RSP0/CPU0 ASR-9010-FAN 1.0 lc cbc 1 4.00 No
--------------------------------------------------------------------------------
0/RSP0/CPU0 ASR-9010-FAN 1.0 lc cbc 2 4.00 No
--------------------------------------------------------------------------------
0/RSP0/CPU0 A9K-BPID2-10-SLOT 1.0 lc cbc 3 7.00 No
--------------------------------------------------------------------------------
0/RSP1/CPU0 A9K-RSP-4G 4.8 lc fpga3 0 1.18 No
--------------------------------------------------------------------------------
0/1/CPU0 A9K-4T-L 1.0 lc fpga1 0 0.42 No
--------------------------------------------------------------------------------
0/1/CPU0 A9K-4T-L 1.0 lc fpga1 1 0.42 No
--------------------------------------------------------------------------------
0/2/CPU0 A9K-2T20GE-B 1.0 lc fpga1 0 0.42 No
--------------------------------------------------------------------------------
0/2/CPU0 A9K-2T20GE-B 1.0 lc fpga1 1 0.42 No
--------------------------------------------------------------------------------
0/3/CPU0 A9K-SIP-700 0.31 lc fpga1 0 0.22 No
--------------------------------------------------------------------------------
0/3/0 SPA-5X1GE-V2 4.255 spa fpga1 0 1.10 No
--------------------------------------------------------------------------------
0/3/1 SPA-2XCHOC12/DS0 1.0 spa rommon 1 2.02 No
--------------------------------------------------------------------------------
0/4/CPU0 A9K-8T/4-L 1.0 lc fpga1 0 0.42 No
--------------------------------------------------------------------------------
0/4/CPU0 A9K-8T/4-L 1.0 lc fpga1 1 0.42 No
--------------------------------------------------------------------------------
0/6/CPU0 A9K-40GE-L 1.0 lc fpga1 0 0.42 No
--------------------------------------------------------------------------------
0/6/CPU0 A9K-40GE-L 1.0 lc fpga1 1 0.42 No
--------------------------------------------------------------------------------
1. One or more FPD needs an upgrade or a downgrade. This can be accomplished
using the "admin upgrade hw-module fpd" CLI.
The following example shows how to upgrade ROMMON B:
RP/0/RSP0/CPU0:router(admin)# upgrade hw-module fpd rommon force location 0/RSP1/CPU0
- The upgrade operation of the target module will not interrupt its normal
operation. However, for the changes to take effect, the target module
will need to be manually reloaded after the upgrade operation. This can
be accomplished with the use of "hw-module <target> reload" command.
- If automatic reload operation is desired after the upgrade, please use
the "reload" option at the end of the upgrade command.
- The output of "show hw-module fpd location" command will not display
correct version information after the upgrade if the target module is
Starting the upgrade/download of following FPD:
=========== ==== ======= ======= =========== =========
Location Type Subtype Upg/Dng Version Version
=========== ==== ======= ======= =========== =========
0/RSP1/CPU0 lc rommon upg 0.64 1.0
------------------------------------------------------
RP/0/RSP1/CPU0:Dec 11 16:18:01.982 : lc_fpd_upgrade[240]: %PLATFORM-UPGRADE_FPD-6-START :
Starting to upgrade rommon subtype image from 0.64 to 1.0 for this card on location
0/RSP1/CPU0
RP/0/RSP1/CPU0:Dec 11 16:18:01.989 : rommon_fpd_agent[303]: Start Upgrade...
RP/0/RSP1/CPU0:Dec 11 16:18:01.990 : rommon_fpd_agent[303]: Programming fpd instance
0...with file
/net/node0_RSP0_CPU0/dev/shmem/asr9k-fpd-3.7.1.23I/fpd/ucode/rommon-viking-8641d-rsp2-B.bi
n
RP/0/RSP1/CPU0:Dec 11 16:18:11.604 : lc_fpd_upgrade[240]: %PLATFORM-UPGRADE_FPD-6-PASSED :
Successfully upgrade rommon subtype image for this card on location 0/RSP1/CPU0
% Successfully upgraded 1 FPD for A9K-RSP-4G-HDD on location 0/RSP1/CPU0
RP/0/RSP0/CPU0:ios(admin)# hw-module location 0/RSP1/CPU0 reload
Graceful Reload of a Cisco ASR 9000 Series Router: Example
In the following example, a Cisco ASR 9000 Series Router is gracefully reloaded following a ROM Monitor firmware upgrade or downgrade:
RP/0/RSP0/CPU0:router# cfs check
Creating any missing directories in Configuration File system...OK
Initializing Configuration Version Manager...OK
Syncing commit database with running configuration...OK
RP/0/RSP0/CPU0:router#hw-module location 0/RSP1/CPU0 reload
WARNING: This will take the requested node out of service.
Do you wish to continue?[confirm(y/n)]y
RP/0/RSP0/CPU0:router# show redundancy
Redundancy information for node 0/RSP0/CPU0:
==========================================
Node 0/RSP0/CPU0 is in ACTIVE role
Partner node (0/RSP1/CPU0) is in STANDBY role
Standby node in 0/RSP1/CPU0 is ready
Standby node in 0/RSP1/CPU0 is NSR-ready
A9K-RSP-4G-HDD reloaded Thu Dec 11 14:50:47 2008: 2 hours, 27 minutes ago
Active node booted Thu Dec 11 14:50:47 2008: 2 hours, 27 minutes ago
Standby node boot Thu Dec 11 17:15:16 2008: 2 minutes ago
Standby node last went not ready Thu Dec 11 17:16:27 2008: 1 minute ago
Standby node last went ready Thu Dec 11 17:17:27 2008: 39 seconds ago
There have been 0 switch-overs since reload
RP/0/RSP0/CPU0:router# redundancy switchover
Proceed with switchover 0/RSP0/CPU0 -> 0/RSP1/CPU0? [confirm]
<Move to node 0/RSP1/CPU0>
RP/0/RSP1/CPU0:router# show redundancy
Redundancy information for node 0/RSP1/CPU0:
==========================================
Node 0/RSP1/CPU0 is in ACTIVE role
Partner node (0/RSP0/CPU0) is in STANDBY role
Standby node in 0/RSP0/CPU0 is ready
Standby node in 0/RSP0/CPU0 is NSR-ready
A9K-RSP-4G-HDD reloaded Thu Dec 11 14:50:47 2008: 2 hours, 35 minutes ago
Active node booted Thu Dec 11 17:15:15 2008: 11 minutes ago
Last switch-over Thu Dec 11 17:19:29 2008: 7 minutes ago
Standby node boot Thu Dec 11 17:22:57 2008: 3 minutes ago
Standby node last went not ready Thu Dec 11 17:24:06 2008: 2 minutes ago
Standby node last went ready Thu Dec 11 17:25:06 2008: 1 minute ago
There has been 1 switch-over since reload
RP/0/RSP1/CPU0:router# hw-module location 0/RSP0/CPU0 reload
WARNING: This will take the requested node out of service.
Do you wish to continue?[confirm(y/n)] y
RP/0/RSP1/CPU0:router# show redundancy
Redundancy information for node 0/RSP1/CPU0:
==========================================
Node 0/RSP1/CPU0 is in ACTIVE role
Partner node (0/RSP0/CPU0) is in STANDBY role
Standby node in 0/RSP0/CPU0 is ready
Standby node in 0/RSP0/CPU0 is NSR-ready
A9K-RSP-4G-HDD reloaded Thu Dec 11 14:50:47 2008: 2 hours, 41 minutes ago
Active node booted Thu Dec 11 17:15:15 2008: 16 minutes ago
Last switch-over Thu Dec 11 17:19:29 2008: 12 minutes ago
Standby node boot Thu Dec 11 17:28:56 2008: 3 minutes ago
Standby node last went not ready Thu Dec 11 17:30:02 2008: 2 minutes ago
Standby node last went ready Thu Dec 11 17:31:02 2008: 1 minute ago
There has been 1 switch-over since reload
RP/0/RSP1/CPU0:router# admin
RP/0/RSP1/CPU0:router(admin)# show platform
Node Type State Config State
-----------------------------------------------------------------------------
0/RSP0/CPU0 A9K-RSP-4G-HDD(Standby) IOS XR RUN PWR,NSHUT,MON
0/RSP1/CPU0 A9K-RSP-4G-HDD(Active) IOS XR RUN PWR,NSHUT,MON
0/0/CPU0 A9K-4T-B IOS XR RUN PWR,NSHUT,MON
0/2/CPU0 A9K-40GE-E IOS XR RUN PWR,NSHUT,MON
0/6/CPU0 A9K-8T/4-E IOS XR RUN PWR,NSHUT,MON
RP/0/RSP1/CPU0:router(admin)# hw-module location 0/0/CPU0 reload
WARNING: This will take the requested node out of service.
Do you wish to continue?[confirm(y/n)] y
RP/0/RSP1/CPU0:router(admin)# hw-module location 0/2/CPU0 reload
WARNING: This will take the requested node out of service.
Do you wish to continue?[confirm(y/n)] y
RP/0/RSP1/CPU0:router(admin)# hw-module location 0/6/CPU0 reload
WARNING: This will take the requested node out of service.
Do you wish to continue?[confirm(y/n)] y
RP/0/RSP1/CPU0:router(admin)# show platform
Node Type State Config State
-----------------------------------------------------------------------------
0/RSP0/CPU0 A9K-RSP-4G-HDD(Standby) IOS XR RUN PWR,NSHUT,MON
0/RSP1/CPU0 A9K-RSP-4G-HDD(Active) IOS XR RUN PWR,NSHUT,MON
0/0/CPU0 A9K-4T-B IOS XR RUN PWR,NSHUT,MON
0/2/CPU0 A9K-40GE-E IOS XR RUN PWR,NSHUT,MON
0/6/CPU0 A9K-8T/4-E IOS XR RUN PWR,NSHUT,MON
RP/0/RSP1/CPU0:router(admin)# show hw-module fpd location all
===================================== ==========================================
Existing Field Programmable Devices
==========================================
Location Card Type Version Type Subtype Inst Version Dng?
============ ======================== ======= ==== ======= ==== =========== ====
0/RSP0/CPU0 A9K-RSP-4G 4.8 lc fpga3 0 1.18 No
--------------------------------------------------------------------------------
0/RSP0/CPU0 ASR-9010-FAN 1.0 lc cbc 1 4.00 No
--------------------------------------------------------------------------------
0/RSP0/CPU0 ASR-9010-FAN 1.0 lc cbc 2 4.00 No
--------------------------------------------------------------------------------
0/RSP0/CPU0 A9K-BPID2-10-SLOT 1.0 lc cbc 3 7.00 No
--------------------------------------------------------------------------------
0/RSP1/CPU0 A9K-RSP-4G 4.8 lc fpga3 0 1.18 No
--------------------------------------------------------------------------------
0/1/CPU0 A9K-4T-L 1.0 lc fpga1 0 0.42 No
--------------------------------------------------------------------------------
0/1/CPU0 A9K-4T-L 1.0 lc fpga1 1 0.42 No
--------------------------------------------------------------------------------
0/2/CPU0 A9K-2T20GE-B 1.0 lc fpga1 0 0.42 No
--------------------------------------------------------------------------------
0/2/CPU0 A9K-2T20GE-B 1.0 lc fpga1 1 0.42 No
--------------------------------------------------------------------------------
0/3/CPU0 A9K-SIP-700 0.31 lc fpga1 0 0.22 No
--------------------------------------------------------------------------------
0/3/0 SPA-5X1GE-V2 4.255 spa fpga1 0 1.10 No
--------------------------------------------------------------------------------
0/3/1 SPA-2XCHOC12/DS0 1.0 spa rommon 1 2.02 No
--------------------------------------------------------------------------------
0/4/CPU0 A9K-8T/4-L 1.0 lc fpga1 0 0.42 No
--------------------------------------------------------------------------------
0/4/CPU0 A9K-8T/4-L 1.0 lc fpga1 1 0.42 No
--------------------------------------------------------------------------------
0/6/CPU0 A9K-40GE-L 1.0 lc fpga1 0 0.42 No
--------------------------------------------------------------------------------
0/6/CPU0 A9K-40GE-L 1.0 lc fpga1 1 0.42 No
--------------------------------------------------------------------------------
1. One or more FPD needs an upgrade or a downgrade. This can be accomplished
using the "admin upgrade hw-module fpd" CLI.
Additional References
Related Documents
Related Topic
|
Document Title
|
Hardware component commands
|
Cisco ASR 9000 Series Aggregation Services Router Interface and Hardware Component Command Reference
|
System management commands
|
Cisco ASR 9000 Series Aggregation Services Router System Management Command Reference
|
Technical Assistance
Description
|
Link
|
The Cisco Technical Support website contains thousands of pages of searchable technical content, including links to products, technologies, solutions, technical tips, and tools. Registered Cisco.com users can log in from this page to access even more content.
|
http://www.cisco.com/techsupport
|