-
Cisco IOS XR ROM Monitor Guide, Release 3.6
-
Preface
-
ROM Monitor Overview and Basic Procedures
-
Router Recovery with ROM Monitor
-
Managing Configuration Files in ROM Monitor
-
Password Recover in ROM Monitor Mode
-
Upgrading and Downgrading ROM Monitor Firmware on Cisco CRS-1 Routers
-
Upgrading and Downgrading Boothelper and ROM Monitor on Cisco XR 12000 Series Routers
-
Index
-
Feedback
Table Of Contents
Upgrading and Downgrading ROM Monitor Firmware on Cisco CRS-1 Routers
Information About ROM Monitor Firmware
Upgrading or Downgrading a Single Node or All Nodes
Reloading Nodes After a ROMMON Firmware Change
ROM Monitor Compatibility with Cisco IOS XR Software
Upgrading or Downgrading ROM Monitor Using the FPD PIE
Configuration Examples for ROM Monitor Upgrades
Graceful Reload of a Cisco CRS-1 Router: Example
Overriding a ROM Monitor Boot Block in a Single-chassis System
Upgrading and Downgrading ROM Monitor Firmware on Cisco CRS-1 Routers
This chapter describes how to upgrade or downgrade the ROM Monitor firmware on a Cisco CRS-1. It includes the following sections:
•
Information About ROM Monitor Firmware
–
–
–
•
•
•
Caution
If the router is brought up with an incompatible version of the ROM Monitor software, then the standby RP may fail to boot. For instructions to overcome a boot block in the standby RP in a single-chassis system, see Overriding a ROM Monitor Boot Block in a Single-chassis System. If a boot block occurs in a multishelf system, contact your Cisco Technical Support representative for assistance. See Obtaining Documentation and Submitting a Service Request.
Cisco CRS-1 multishelf systems should be upgraded to ROMMON release 1.40 before being upgraded to Cisco IOS XR Release 3.6.0 to ensure that RPs are assigned the correct rack numbers during system boot.
Note
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 CRS-1. 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:
•
•
Tip
About ROMMON A and ROMMON B
Each node in a Cisco CRS-1 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 ROMMON 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 router. During an upgrade or downgrade, the ROMMON firmware is copied into hardware EEPROMs in the router. For more information on ROMMON firmware compatibility with the Cisco IOS XR software and Cisco CRS-1 router, see ROM Monitor Compatibility with Cisco IOS XR Software.
For most upgrades, we recommend upgrading or downgrading the ROMMON firmware on all nodes. You can also upgrade or downgrade a single node which is useful when moving a card between two routers or adding a card that is not running the correct ROM Monitor version. When you upgrade a single node that uses ROM Monitor in both the CPU0 and SP modules, such as a line card node, we recommend that you upgrade both modules to the same ROM Monitor version.
Reloading Nodes After a ROMMON Firmware Change
The new ROMMON 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 ROMMON version.
To gracefully reload all nodes, reload the standby RP, perform a redundancy switchover, reload the second RP, and then reload all other nodes in the system.
If the router does not contain a redundant standby RP, or if you wish to perform a cold restart, you can also reload all nodes at the same time, including the primary RP (DSC). Remember that a cold restart results in router downtime while the cards reboot.
Instructions to reload the nodes are included in Upgrading or Downgrading ROM Monitor Using the FPD PIE.
ROM Monitor Compatibility with Cisco IOS XR Software
The ROM Monitor firmware on all RPs must be compatible with the Cisco IOS XR software release currently running on the router before a Cisco CRS-1 system is upgraded to Cisco IOS XR Software Release 3.6.0. If the router is brought up with an incompatible version of the ROM Monitor software, then the standby RP may fail to boot.
For minimum ROM Monitor version requirements for Cisco IOS XR Software Releases 3.01 and later releases, refer to Software/Firmware Compatibility Matrix at the following URL:
http://www.cisco.com/web/Cisco_IOS_XR_Software/index.html
In addition, Cisco CRS-1 multishelf systems should be upgraded to ROMMON release 1.40 before being upgraded to Cisco IOS XR Release 3.6.0, to ensure that RPs are assigned the correct rack numbers during system boot.
After you upgrade to Cisco IOS XR Software Release 3.6.0, you should upgrade the ROM Monitor firmware to the recommended version for this release. See Software/Firmware Compatibility Matrix.
Note
Overriding a Boot Block in the Standby RP
If a Cisco CRS-1 system is upgraded to Cisco IOS XR Software Release 3.6.0 before the ROM Monitor firmware is upgraded to a compatible version, a boot block may occur in the standby RP.
•
•
Note
Upgrading or Downgrading ROM Monitor Using the FPD PIE
The following procedure upgrades or downgrades the ROM Monitor firmware using the ROM Monitor image contained in the field-programmable device (FPD) software 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
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 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 following prerequisites have been met:
•
•
Note
SUMMARY STEPS
1.
2.
3.
4.
5.
6.
7.
8.
9.
a.
b.
10.
a.
b.
c.
d.
e.
f.
g.
h.
i.
j.
k.
l.
m.
n.
11.
a.
b.
c.
d.
12.
DETAILED STEPS
Step 1
show hw-module fpd location all
Example:RP/0/RP0/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/RP0/CPU0:Router# admin
Enters administration EXEC mode from EXEC mode.
Step 3
show fpd package
Example:RP/0/RP0/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/RP0/CPU0:Router(admin)# upgrade hw-module fpd rommon location 0/SM3/SP
Upgrades the ROMMON B images on the specified card (node-id) or all cards (all).
Note
Step 5
exit
Example:RP/0/RP0/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 DSDRSC, go to Step 9.
Continues to reload the node.
Step 7
If you are upgrading a router with redundant DSCs, 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 RP, 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:
a.
b.
Example:
RP/0/RP0/CPU0:router# hw-module location 0/RP1/CPU0 reload
a.
–
–
b.
Step 10
Gracefully reload all nodes on a system that includes redundant RPs (DSCs):
a.
b.
c.
d.
e.
f.
g.
h.
i.
j.
k.
l.
m.
n.
Gracefully reloads all nodes on a system that includes redundant RPs. The new ROMMON firmware is not active on a node until the card is reloaded.
a.
b.
c.
Note
d.
e.
Note
f.
g.
h.
i.
j.
Example:
RP/0/RP0/CPU0:router# cfs check
RP/0/RP0/CPU0:router# hw-module location 0/RP1/CPU0 reload
RP/0/RP0/CPU0:router# show redundancy
RP/0/RP0/CPU0:router# redundancy switchover
RP/0/RP0/CPU0:router# show redundancy
RP/0/RP0/CPU0:router# hw-module location 0/RP0/CPU0 reload
RP/0/RP0/CPU0:router# admin
RP/0/RP0/CPU0:router(admin)# show platform
RP/0/RP0/CPU0:router(admin)# hw-module location
0/1/CPU0 reload
RP/0/RP0/CPU0:router(admin)# hw-module location 0/2/CPU0 reload
RP/0/RP0/CPU0:router(admin)# hw-module location 0/SM0/SP reload
RP/0/RP0/CPU0:router(admin)# hw-module location 0/SM1/SP reload
RP/0/RP0/CPU0:router(admin)# hw-module location 0/SM2/SP reload
RP/0/RP0/CPU0:router(admin)# hw-module location 0/SM3/SP reload
RP/0/RP0/CPU0:router(admin)# show platform
k.
Replace node-id with the node ID you specified when upgrading ROM Monitor.
When reloading cards that contain both a CPU and an SP (such as an MSC card), it is only necessary to reload the CPU node. When the CPU is reloaded, the SP will also reload.
l.
m.
Step 11
Reload all nodes in the system (cold restart):
a.
b.
c.
d.
Example:
RP/0/RP0/CPU0:router# cfs check
RP/0/RP0/CPU0:router# admin
RP/0/RP0/CPU0:router(admin)# reload location all
Reloads all nodes, including the DSC. Use these commands if you are upgrading a router with a single RP, or wish to perform a cold restart of all nodes. The new ROMMON firmware is not active on a node until the card is reloaded.
Caution
a.
b.
c.
d.
Step 12
show platform
Example:RP/0/RP0/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
•
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•
•
Configuration Examples for ROM Monitor Upgrades
This section provides the following configuration examples:
•
ROM Monitor Upgrade: Example
The following example illustrates how to display ROM monitor image information for all cards in the router. ROMMON B is referred to as rommon in the display.
RP/0/RP0/CPU0:Router(admin)# show hw-module fpd location all===================================== ==========================================Existing Field Programmable Devices==========================================HW Current SW Upg/Location Card Type Version Type Subtype Inst Version Dng?============ ======================== ======= ==== ======= ==== =========== ====0/1/SP YYY-XXXIface 0.2 lc rommonA 0 1.43 Nolc rommon 0 1.43 No--------------------------------------------------------------------------------0/1/CPU0 CRS1-SIP-800 0.96 lc fpga 0 2.0 Nolc rommonA 0 1.43 Nolc rommon 0 1.43 No--------------------------------------------------------------------------------0/1/0 SPA-4XOC3-POS 1.0 spa fpga 0 3.4 No--------------------------------------------------------------------------------0/1/4 SPA-4XOC48POS/RPR 1.0 spa fpga 4 1.0 No--------------------------------------------------------------------------------0/1/5 SPA-8X1GE 2.2 spa fpga 5 1.8 No--------------------------------------------------------------------------------0/4/SP DRP 0.3 lc rommonA 0 1.43 Nolc rommon 0 1.43 No--------------------------------------------------------------------------------0/4/CPU0 DRP 0.3 lc rommonA 0 1.43 Nolc rommon 0 1.43 No--------------------------------------------------------------------------------0/4/CPU1 DRP 0.3 lc rommonA 0 1.43 Nolc rommon 0 1.43 No--------------------------------------------------------------------------------0/6/SP YYY-XXXIface 0.3 lc rommonA 0 1.43 Nolc rommon 0 1.43 No--------------------------------------------------------------------------------0/6/CPU0 CRS1-SIP-800 0.96 lc fpga 0 2.0 Nolc rommonA 0 1.43 Nolc rommon 0 1.43 No--------------------------------------------------------------------------------0/6/0 SPA-4XOC3-POS 1.0 spa fpga 0 3.4 No--------------------------------------------------------------------------------0/6/4 SPA-8XOC12-POS 1.1 spa fpga 4 1.0 No--------------------------------------------------------------------------------0/6/5 SPA-8X1GE 2.2 spa fpga 5 1.8 No--------------------------------------------------------------------------------0/RP0/CPU0 HQ Route Processor 0.1 lc rommonA 0 1.43 Nolc rommon 0 1.43 No--------------------------------------------------------------------------------0/RP1/CPU0 HQ Route Processor 0.1 lc rommonA 0 1.43 Nolc rommon 0 1.43 No--------------------------------------------------------------------------------0/SM0/SP Fabric HS123 0.1 lc rommonA 0 1.43 Nolc rommon 0 1.43 No--------------------------------------------------------------------------------0/SM1/SP Fabric HS123 0.1 lc rommonA 0 1.43 Nolc rommon 0 1.43 No--------------------------------------------------------------------------------0/SM2/SP Fabric HS123 0.1 lc rommonA 0 1.43 Nolc rommon 0 1.43 No--------------------------------------------------------------------------------0/SM3/SP Fabric HS123 0.1 lc rommonA 0 1.43 Nolc rommon 0 1.43 No--------------------------------------------------------------------------------The following example shows how to determine what FPD images are available for each card in the router:
RP/0/RP0/CPU0:Router(admin)# show fpd package=============================== ================================================Field Programmable Device Package================================================SW Min ReqCard Type FPD Description Type Subtype Version HW Vers==================== ========================== ==== ======= =========== =======CRS1-SIP-800 JACKET FPGA swv2.0 lc fpga 2.0 0.0FPGA swv2.0 hwv80 lc fpga 2.0 0.80--------------------------------------------------------------------------------8-10GBE FPGA swvA.0 lc fpga 10.0 0.0--------------------------------------------------------------------------------Route Processor ROMMONA swv1.43 asmp lc rommonA 1.32 0.0ROMMONA swv1.43 dsmp lc rommonA 1.32 0.0ROMMONB swv1.43 asmp lc rommon 1.43 0.0ROMMONB swv1.43 dsmp lc rommon 1.43 0.0--------------------------------------------------------------------------------SC ROMMONA swv1.43 asmp lc rommonA 1.32 0.0ROMMONA swv1.43 dsmp lc rommonA 1.32 0.0ROMMONB swv1.43 asmp lc rommon 1.43 0.0ROMMONB swv1.43 dsmp lc rommon 1.43 0.0--------------------------------------------------------------------------------HQ Route Processor ROMMONA swv1.43 asmp lc rommonA 1.32 0.0ROMMONA swv1.43 dsmp lc rommonA 1.32 0.0ROMMONB swv1.43 asmp lc rommon 1.43 0.0ROMMONB swv1.43 dsmp lc rommon 1.43 0.0--------------------------------------------------------------------------------Shelf Controller GE ROMMONA swv1.43 asmp lc rommonA 1.32 0.0ROMMONA swv1.43 dsmp lc rommonA 1.32 0.0ROMMONB swv1.43 asmp lc rommon 1.43 0.0ROMMONB swv1.43 dsmp lc rommon 1.43 0.0--------------------------------------------------------------------------------Route Processor B ROMMONA swv1.43 asmp lc rommonA 1.32 0.0ROMMONA swv1.43 dsmp lc rommonA 1.32 0.0ROMMONB swv1.43 asmp lc rommon 1.43 0.0ROMMONB swv1.43 dsmp lc rommon 1.43 0.0--------------------------------------------------------------------------------Shelf Controller GE2 ROMMONA swv1.43 asmp lc rommonA 1.32 0.0ROMMONA swv1.43 dsmp lc rommonA 1.32 0.0ROMMONB swv1.43 asmp lc rommon 1.43 0.0ROMMONB swv1.43 dsmp lc rommon 1.43 0.0--------------------------------------------------------------------------------DRP ROMMONA swv1.43 asmp lc rommonA 1.32 0.0ROMMONA swv1.43 dsmp lc rommonA 1.32 0.0ROMMONA swv1.43 sp lc rommonA 1.32 0.0ROMMONB swv1.43 asmp lc rommon 1.43 0.0ROMMONB swv1.43 dsmp lc rommon 1.43 0.0ROMMONB swv1.43 sp lc rommon 1.43 0.0--------------------------------------------------------------------------------DRP_B ROMMONA swv1.43 asmp lc rommonA 1.32 0.0ROMMONA swv1.43 dsmp lc rommonA 1.43 0.0ROMMONA swv1.43 sp lc rommonA 1.43 0.0ROMMONB swv1.43 asmp lc rommon 1.43 0.0ROMMONB swv1.43 dsmp lc rommon 1.43 0.0ROMMONB swv1.43 sp lc rommon 1.43 0.0--------------------------------------------------------------------------------S1S2S3 ROMMONA swv1.43 sp lc rommonA 1.32 0.0ROMMONB swv1.43 sp lc rommon 1.43 0.0--------------------------------------------------------------------------------S1S3 ROMMONA swv1.43 sp lc rommonA 1.32 0.0ROMMONB swv1.43 sp lc rommon 1.43 0.0--------------------------------------------------------------------------------S2 ROMMONA swv1.43 sp lc rommonA 1.32 0.0ROMMONB swv1.43 sp lc rommon 1.43 0.0--------------------------------------------------------------------------------Fabric HS123 ROMMONA swv1.43 sp lc rommonA 1.32 0.0ROMMONB swv1.43 sp lc rommon 1.43 0.0--------------------------------------------------------------------------------Fabric HS123 Star ROMMONA swv1.43 sp lc rommonA 1.32 0.0ROMMONB swv1.43 sp lc rommon 1.43 0.0--------------------------------------------------------------------------------Fabric HS13 Star ROMMONA swv1.43 sp lc rommonA 1.32 0.0ROMMONB swv1.43 sp lc rommon 1.43 0.0--------------------------------------------------------------------------------Fabric QQS123 ROMMONA swv1.43 sp lc rommonA 1.32 0.0ROMMONB swv1.43 sp lc rommon 1.43 0.0--------------------------------------------------------------------------------LED ROMMONA swv1.43 sp lc rommonA 1.32 0.0ROMMONB swv1.43 sp lc rommon 1.43 0.0--------------------------------------------------------------------------------YYY-XXXIface ROMMONA swv1.43 asmp lc rommonA 1.32 0.0ROMMONA swv1.43 dsmp lc rommonA 1.32 0.0ROMMONA swv1.43 sp lc rommonA 1.32 0.0ROMMONB swv1.43 asmp lc rommon 1.43 0.0ROMMONB swv1.43 dsmp lc rommon 1.43 0.0ROMMONB swv1.43 sp lc rommon 1.43 0.0--------------------------------------------------------------------------------PSAL ROMMONA swv1.43 sp lc rommonA 1.32 0.0ROMMONB swv1.43 sp lc rommon 1.43 0.0--------------------------------------------------------------------------------FAN ROMMONA swv1.43 sp lc rommonA 1.32 0.0ROMMONB swv1.43 sp lc rommon 1.43 0.0--------------------------------------------------------------------------------FC Fan Controller ROMMONA swv1.43 sp lc rommonA 1.32 0.0ROMMONB swv1.43 sp lc rommon 1.43 0.0--------------------------------------------------------------------------------LED ROMMONA swv1.43 sp lc rommonA 1.32 0.0ROMMONB swv1.43 sp lc rommon 1.43 0.0--------------------------------------------------------------------------------SPA-4XT3/E3 SPA E3 Subrate FPGA spa fpga2 1.4 0.0SPA T3 Subrate FPGA spa fpga3 1.4 0.0SPA I/O FPGA spa fpga 1.0 0.0SPA ROMMON spa rommon 2.12 0.0--------------------------------------------------------------------------------SPA-2XT3/E3 SPA E3 Subrate FPGA spa fpga2 1.4 0.0SPA T3 Subrate FPGA spa fpga3 1.4 0.0SPA I/O FPGA spa fpga 1.0 0.0SPA ROMMON spa rommon 2.12 0.0--------------------------------------------------------------------------------SPA-OC192POS SPA FPGA swv1.3 spa fpga 1.3 0.0--------------------------------------------------------------------------------SPA-8XOC12-POS SPA FPGA swv1.0 spa fpga 1.0 0.5--------------------------------------------------------------------------------SPA-4XOC3-POS SPA FPGA swv3.4 spa fpga 3.4 0.0--------------------------------------------------------------------------------SPA-OC192POS-XFP SPA FPGA swv1.2 spa fpga 1.2 0.0--------------------------------------------------------------------------------SPA-8X1GE SPA FPGA swv1.8 spa fpga 1.8 0.0--------------------------------------------------------------------------------SPA-2XOC48POS/RPR SPA FPGA swv1.0 spa fpga 1.0 0.0--------------------------------------------------------------------------------SPA-4XOC48POS/RPR SPA FPGA swv1.0 spa fpga 1.0 0.0--------------------------------------------------------------------------------SPA-10X1GE-V2 SPA FPGA swv1.10 spa fpga 1.10 0.0--------------------------------------------------------------------------------SPA-8X1GE-V2 SPA FPGA swv1.10 spa fpga 1.10 0.0--------------------------------------------------------------------------------SPA-5X1GE-V2 SPA FPGA swv1.10 spa fpga 1.10 0.0--------------------------------------------------------------------------------SPA-1X10GE-L-V2 SPA FPGA swv1.9 spa fpga 1.9 0.0--------------------------------------------------------------------------------SPA-1X10GE-WL-V2 SPA FPGA swv1.11 spa fpga 1.11 0.0--------------------------------------------------------------------------------The following example shows how to upgrade ROMMON B:
RP/0/RP0/CPU0:Router(admin)# upgrade hw-module fpd rommon force location 0/SM3/SP% RELOAD REMINDER:- The upgrade operation of the target module will not interrupt its normaloperation. However, for the changes to take effect, the target modulewill need to be manually reloaded after the upgrade operation. This canbe accomplished with the use of "hw-module <target> reload" command.- If automatic reload operation is desired after the upgrade, please usethe "reload" option at the end of the upgrade command.- The output of "show hw-module fpd location" command will not displaycorrect version information after the upgrade if the target module isnot reloaded.Continue? [confirm]Starting the upgrade/download of following FPD:=========== ==== ======= ======= =========== =========Current Upg/DngLocation Type Subtype Upg/Dng Version Version=========== ==== ======= ======= =========== =========0/SM3/SP lc rommon upg 1.43 1.43------------------------------------------------------SP/0/SM3/SP:Feb 20 15:58:25.656 : lc_fpd_upgrade[112]: %PLATFORM-UPGRADE_FPD-6-START : Starting to upgrade rommon subtype image from 1.43 to 1.43 for for this card on location 0/SM3/SP SP/0/SM3/SP:Feb 20 15:58:25.692 : upgrade_daemon[128]: Start Upgrade...SP/0/SM3/SP:Feb 20 15:58:25.696 : upgrade_daemon[128]: programming...with file /net/node0_RP0_CPU0/dev/shmem/hfr-fpd-3.5.0.0I/fpd/ucode/rommon-hfr-ppc8255-sp-B.binSP/0/SM3/SP:Feb 20 15:58:25.719 : upgrade_daemon[128]: Verifying /net/node0_RP0_CPU0/dev/shmem/hfr-fpd-3.5.0.0I/fpd/ucode/rommon-hfr-ppc8255-sp-B.bin:SP/0/SM3/SP:Feb 20 15:58:25.920 : upgrade_daemon[128]: Passed.SP/0/SM3/SP:Feb 20 15:58:31.257 : upgrade_daemon[128]: Verifying ROMMON B:SP/0/SM3/SP:Feb 20 15:58:31.297 : upgrade_daemon[128]: Passed.SP/0/SM3/SP:Feb 20 15:58:31.301 : upgrade_daemon[128]: OK, ROMMON B is programmed successfully.SP/0/SM3/SP:Feb 20 15:58:31.310 : lc_fpd_upgrade[112]: %PLATFORM-UPGRADE_FPD-6-PASSED : Successfully upgrade rommon subtype image for for this card on location 0/SM3/SP% Successfully upgraded 1 FPD for Fabric HS123 on location 0/SM3/SPGraceful Reload of a Cisco CRS-1 Router: Example
In the following example, a Cisco CRS-1 router is gracefully reloaded following a ROMMON upgrade or downgrade:
RP/0/RP0/CPU0:router# cfs checkCreating any missing directories in Configuration File system...OKInitializing Configuration Version Manager...OKSyncing commit database with running configuration...OKRe-initializing cache files...OKUpdating Commit Database. Please wait...[OK]RP/0/RP0/CPU0:router# hw-module location 0/RP1/CPU0 reloadWARNING: This will take the requested node out of service.Do you wish to continue?[confirm(y/n)]yRP/0/RP0/CPU0:router# show redundancyRedundancy information for node 0/RP0/CPU0:==========================================Node 0/RP0/CPU0 is in ACTIVE rolePartner node (0/RP1/CPU0) is in STANDBY roleStandby node in 0/RP1/CPU0 is readyReload and boot info----------------------RP reloaded Sun Jun 11 17:46:26 2006: 1 hour, 10 minutes agoActive node booted Sun Jun 11 17:46:26 2006: 1 hour, 10 minutes agoStandby node boot Sun Jun 11 18:50:39 2006: 6 minutes agoStandby node last went not ready Sun Jun 11 18:51:18 2006: 6 minutes agoStandby node last went ready Sun Jun 11 18:53:21 2006: 4 minutes agoThere have been 0 switch-overs since reloadRP/0/RP0/CPU0:router# redundancy switchoverUpdating Commit Database. Please wait...[OK]Proceed with switchover 0/RP0/CPU0 -> 0/RP1/CPU0? [confirm]Initiating switch-over.RP/0/RP0/CPU0:Router#<Your 'TELNET' connection has terminated>User Access VerificationUsername: usernamePassword: <secret>Last switch-over Tue Jun 13 12:07:34 2006: 1 minute agoRP/0/RP1/CPU0:router# show redundancyRedundancy information for node 0/RP1/CPU0:==========================================Node 0/RP1/CPU0 is in ACTIVE rolePartner node (0/RP0/CPU0) is in STANDBY roleStandby node in 0/RP0/CPU0 is readyReload and boot info----------------------RP reloaded Sun Jun 11 19:47:43 2006: 1 day, 16 hours, 24 minutes agoActive node booted Sun Jun 11 19:48:25 2006: 1 day, 16 hours, 24 minutes agoLast switch-over Tue Jun 13 12:07:34 2006: 5 minutes agoStandby node boot Tue Jun 13 12:08:50 2006: 3 minutes agoStandby node last went not ready Tue Jun 13 12:09:21 2006: 3 minutes agoStandby node last went ready Tue Jun 13 12:11:21 2006: 1 minute agoThere has been 1 switch-over since reloadRP/0/RP1/CPU0:router# hw-module location 0/rp0/cpu0 reloadWARNING: This will take the requested node out of service.Do you wish to continue?[confirm(y/n)]yRP/0/RP1/CPU0:router# show redundancyRedundancy information for node 0/RP1/CPU0:==========================================Node 0/RP1/CPU0 is in ACTIVE rolePartner node (0/RP0/CPU0) is in STANDBY roleStandby node in 0/RP0/CPU0 is readyReload and boot info----------------------RP reloaded Sun Jun 11 19:47:43 2006: 1 day, 16 hours, 30 minutes agoActive node booted Sun Jun 11 19:48:25 2006: 1 day, 16 hours, 30 minutes agoLast switch-over Tue Jun 13 12:07:34 2006: 11 minutes agoStandby node boot Tue Jun 13 12:15:24 2006: 3 minutes agoStandby node last went not ready Tue Jun 13 12:18:26 2006: 11 seconds agoStandby node last went ready Tue Jun 13 12:18:26 2006: 11 seconds agoThere has been 1 switch-over since reloadRP/0/RP1/CPU0:router# adminRP/0/RP1/CPU0:router(admin)# show platformNode Type PLIM State Config State-----------------------------------------------------------------------------0/1/SP MSC(SP) N/A IOS XR RUN PWR,NSHUT,MON0/1/CPU0 MSC Jacket Card IOS XR RUN PWR,NSHUT,MON0/1/0 MSC(SPA) 4XOC3-POS OK PWR,NSHUT,MON0/1/5 MSC(SPA) 8X1GE OK PWR,NSHUT,MON0/6/SP MSC(SP) N/A IOS XR RUN PWR,NSHUT,MON0/6/CPU0 MSC Jacket Card IOS XR RUN PWR,NSHUT,MON0/6/0 MSC(SPA) 4XOC3-POS OK PWR,NSHUT,MON0/6/4 MSC(SPA) 8XOC3/OC12-POS OK PWR,NSHUT,MON0/6/5 MSC(SPA) 8X1GE OK PWR,NSHUT,MON0/RP0/CPU0 RP(Standby) N/A IOS XR RUN PWR,NSHUT,MON0/RP1/CPU0 RP(Active) N/A IOS XR RUN PWR,NSHUT,MON0/SM0/SP FC/S(SP) N/A IOS XR RUN PWR,NSHUT,MON0/SM1/SP FC/S(SP) N/A IOS XR RUN PWR,NSHUT,MON0/SM2/SP FC/S(SP) N/A IOS XR RUN PWR,NSHUT,MON0/SM3/SP FC/S(SP) N/A IOS XR RUN PWR,NSHUT,MONRP/0/RP1/CPU0:router(admin)# hw-module location 0/1/cpu0 reload warmWARNING: This will warm reload the requested node.Do you wish to continue?[confirm(y/n)]yRP/0/RP1/CPU0:router(admin)# hw-module location 0/6/cpu0 reload warmWARNING: This will warm reload the requested node.Do you wish to continue?[confirm(y/n)]yRP/0/RP1/CPU0:router(admin)# hw-module location 0/sm0/sp reloadWARNING: This will take the requested node out of service.Do you wish to continue?[confirm(y/n)]yRP/0/RP1/CPU0:router(admin)# hw-module location 0/sm1/SP reloadWARNING: This will take the requested node out of service.Do you wish to continue?[confirm(y/n)]yRP/0/RP1/CPU0:router(admin)# hw-module location 0/sm2/SP reloadWARNING: This will take the requested node out of service.Do you wish to continue?[confirm(y/n)]yRP/0/RP1/CPU0:router(admin)# hw-module location 0/sm3/SP reloadWARNING: This will take the requested node out of service.Do you wish to continue?[confirm(y/n)]yRP/0/RP1/CPU0:router(admin)# show platformNode Type PLIM State Config State-----------------------------------------------------------------------------0/1/SP MSC(SP) N/A IOS XR RUN PWR,NSHUT,MON0/1/CPU0 MSC Jacket Card IOS XR RUN PWR,NSHUT,MON0/1/0 MSC(SPA) 4XOC3-POS OK PWR,NSHUT,MON0/1/5 MSC(SPA) 8X1GE OK PWR,NSHUT,MON0/6/SP MSC(SP) N/A IOS XR RUN PWR,NSHUT,MON0/6/CPU0 MSC Jacket Card IOS XR RUN PWR,NSHUT,MON0/6/0 MSC(SPA) 4XOC3-POS OK PWR,NSHUT,MON0/6/4 MSC(SPA) 8XOC3/OC12-POS OK PWR,NSHUT,MON0/6/5 MSC(SPA) 8X1GE OK PWR,NSHUT,MON0/RP0/CPU0 RP(Standby) N/A IOS XR RUN PWR,NSHUT,MON0/RP1/CPU0 RP(Active) N/A IOS XR RUN PWR,NSHUT,MON0/SM0/SP FC/S(SP) N/A IOS XR RUN PWR,NSHUT,MON0/SM1/SP FC/S(SP) N/A IOS XR RUN PWR,NSHUT,MON0/SM2/SP FC/S(SP) N/A IOS XR RUN PWR,NSHUT,MON0/SM3/SP FC/S(SP) N/A IOS XR RUN PWR,NSHUT,MONRP/0/RP1/CPU0:router(admin)# show diag | inc ROM|NODE|PLIMNODE 0/1/SP : MSC(SP)ROMMON: Version 1.40(20060207:032848) [CRS-1 ROMMON]PLIM 0/1/CPU0 : JACKET CARDROMMON: Version 1.40(20060207:032757) [CRS-1 ROMMON]NODE 0/1/0 : 4xOC3 POS SPANODE 0/1/5 : 8xGE SPANODE 0/6/SP : MSC(SP)ROMMON: Version 1.40(20060207:032848) [CRS-1 ROMMON]PLIM 0/6/CPU0 : JACKET CARDROMMON: Version 1.40(20060207:032743) [CRS-1 ROMMON]NODE 0/6/0 : 4xOC3 POS SPANODE 0/6/4 : 8xOC3/OC12 POS SPANODE 0/6/5 : 8xGE SPANODE 0/RP0/CPU0 : RPROMMON: Version 1.40(20060207:032757) [CRS-1 ROMMON]NODE 0/RP1/CPU0 : RPROMMON: Version 1.40(20060207:032757) [CRS-1 ROMMON]NODE 0/SM0/SP : FC/SROMMON: Version 1.40(20060207:032848) [CRS-1 ROMMON]NODE 0/SM1/SP : FC/SROMMON: Version 1.40(20060207:032848) [CRS-1 ROMMON]NODE 0/SM2/SP : FC/SROMMON: Version 1.40(20060207:032848) [CRS-1 ROMMON]NODE 0/SM3/SP : FC/SROMMON: Version 1.40(20060207:032848) [CRS-1 ROMMON]Overriding a ROM Monitor Boot Block in a Single-chassis System
When a single chassis Cisco CRS-1 system is upgraded to Cisco IOS XR software Release 3.4.0 or higher, the ROM Monitor firmware must be upgraded to release 1.42 or higher before the Cisco IOS XR software is installed or upgraded.
If a single chassis Cisco CRS-1 system is brought up with the incorrect ROM Monitor firmware, the standby RP will fail to boot, and the following console message is displayed:
Received boot request from an RP with an empty rack serial number, which indicates an attempt to boot a RP with ROMMON v1.19x as the standby. Boot request is being failed ! Refer to customer documentation for configuring a boot override.To correct this error, you must override the boot block as described in the following instructions. When the RP is running, immediately upgrade the ROM Monitor firmware.
Caution
Restrictions
These instructions are for an RP in a single chassis system only.
Note
SUMMARY STEPS
1.
2.
3.
4.
DETAILED STEPS
Step 1
admin
Example:
RP/0/RP0/CPU0:Router# admin
Places the router in administration EXEC mode.
Step 2
configure
Example:
RP/0/RP0/CPU0:Router(admin)# configure
Enters administration configuration mode.
Step 3
hw-module boot override
Example:
RP/0/RP0/CPU0:Router(admin-config)# hw-module boot override
Allows the RP to boot so the ROM Monitor firmware can be upgraded to the proper version. A message will appear
Step 4
Complete the instructions in Upgrading or Downgrading ROM Monitor Using the FPD PIE.
Upgrades the ROM Monitor firmware on the RP, which allows the RP to boot normally.
Examples
In the following example, an error message is displayed on the console. The boot block is then cleared to allow the user to upgrade the ROM Monitor firmware.
Received boot request from an RP with an empty rack serial number, which indicates an attempt to boot a RP with ROMMON v1.19x as the standby. Boot request is being failed ! Refer to customer documentation for configuring a boot override.RP/0/RP0/CPU0:Router# adminRP/0/RP0/CPU0:Router(admin)# configureRP/0/RP0/CPU0:Router(admin-config)# hw-module boot overrideWARNING !!! WARNING !!! Received boot request from an RP with an empty rack serial number. Permitting RP to boot due to config override. Please upgrade RP ROMMON to latest recommended versionWhat to Do Next
Complete the instructions in Upgrading or Downgrading ROM Monitor Using the FPD PIE.
Additional References
Related Documents
Hardware component commands
Cisco IOS XR Interface and Hardware Component Command Reference
System management commands
Cisco IOS XR System Management Command Reference
Technical Assistance
