Caution 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 system is upgraded to Cisco IOS XR Software Release 3.9.0. For minimum ROM Monitor requirements, see
Software/Firmware Compatibility Matrix.
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 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:
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 CRS 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.
Normally, you only upgrade ROMMON B in most cases. ROMMON A is a backup from ROMMON B in case ROMMON B fails. Failures are most likely to occur during ROMMON upgrades or downgrades; they are very unlikely to fail during normal usage. A failure in ROMMON A results in an inactive card that must be returned to the authorized merchandiser.
By default, on an MSC/FP-140 and PRP ROMMON, there is a dedicated piece of hardware that chooses to boot ROMMON B. This resets the board and selects ROMMON A in the event of a boot timer expiry, which means that ROMMON A and ROMMON B are fully independent and identical images.
Note • ROMMON 1.x and ROMMON 2.x are not compatible with each other.
We recommend that you upgrade ROMMON A and ROMMON B to a minimum of ROMMON version 2.03 or a later version after the Cisco IOS XR software is upgraded to release 4.1.0 or a later release.
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 Cisco IOS XR software and the Cisco CRS 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 the 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.
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 system is upgraded to Cisco IOS XR Software Release 3.9.0. If the router is brought up with an incompatible version of the ROM Monitor software, the standby RP may fail to boot.
NoteROMMON version 2.01 (or 2.03) is the minimal version for Cisco IOS XR Software Release 4.0.x (or 4.1.x).
For minimum ROM Monitor version requirements for Cisco IOS XR Software Release 3.2 and later releases, see Software/Firmware Compatibility Matrix at the following URL:
In addition, Cisco CRS multishelf systems should be upgraded to ROMMON release 1.54 before being upgraded to Cisco IOS XR Software Release 3.9.0, to ensure that RPs are assigned the correct rack numbers during system boot.
After you upgrade to Cisco IOS XR Software Release 3.9.0, you should upgrade the ROM Monitor firmware to the recommended version for this release. See Software/Firmware Compatibility Matrix .
NoteIf the ROM Monitor firmware is not compatible with the Cisco IOS XR software currently running on the router, refer to the documentation for your currently running software release for instructions on upgrading the ROM Monitor firmware to a compatible version. After you upgrade to Cisco IOS XR Software Release 3.9.0, use the instructions in this module to upgrade your ROM Monitor firmware to a version compatible with Cisco IOS XR Software Release 3.9.0.
Overriding a Boot Block in the Standby RP
If a Cisco CRS system is upgraded to Cisco IOS XR Software Release 3.9.0 before the ROM Monitor firmware is upgraded to a compatible version, a boot block may occur in the standby RP.
If a boot block occurs in a multishelf system, contact your Cisco Systems support representative for assistance. See “$paratext>” section.
NoteIf you are running Cisco IOS XR Software Release 3.2.6, or an earlier release, RP/B is not supported in Cisco CRS systems (single-shelf or multishelf). RP/B was introduced in Cisco IOS XR Software Release 3.3.0 with a minimum supported ROMMON version of 1.38.
In split-boot feature, the minimal boot image (MBI) resides within bootflash memory and the rest of the packages reside on the PCMCIA cards. Split-boot applies only to the RP node, DRP nodes of the LC chassis, and SC node of the fabric chassis. ROM Monitor boots the MBI from bootflash memory. MBI boots other packages (Manageability, Security, MPLS, and Multicast) from flash disk (disk0/disk1) on all RP, DRP, and SC nodes within the Cisco CRS router. When the MBI is installed, it contains all the necessary file system drivers, which can then access the packages and files from the PCMCIA cards.
NoteThe flash disk drives, disk0 and disk1, are not accessible from ROM Monitor due to the FAT 32 file system. However, the flash disk drives are accessible from ROM Monitor in the FAT 16 file system. Both Cisco IOS XR software Release 3.9.0 and Cisco IOS XR software Release 3.8.0 support both FAT 16 and FAT 32 file systems. Earlier releases support only the FAT 16 filesystem.
The following are the prerequisites for implementing the split-boot feature on ROM Monitor:
New ROMMON with split-boot support: The minimum ROMMON version of 1.53 is required to support Split-boot. When the Cisco CRS router uses Cisco IOS XR software Release 3.9.0 or a later release, you must upgrade the ROM Monitor based on the instructions mentioned in the next section. For more information, see Upgrading or Downgrading ROM Monitor Using the FPD PIE.
Install code with split-boot support: All RP, DRP, and SC nodes must have a working bootflash; otherwise, the router fails to boot.
Safe Messages to Ignore
Safe messages do not indicate any error. They appear because the new ROM Monitor first searches for the MBI in bootflash memory in Release 3.7.0 and earlier releases of Cisco IOS XR software. However, these safe messages are not displayed if you are using Cisco IOS XR Software Release 3.9.0 and Cisco IOS XR software Release 3.8.0. releases.
When the flash disk is booting RP, DRP, and SC nodes that have the new ROM Monitor with a Cisco IOS XR software image earlier than Release 3.9.0, the safe messages are displayed under the following conditions:
When the BOOT variable is set to BOOT=disk0:<mbi_image_path>/<mbi.vm>:
Fail to open file name disk0/<mbi_image_path>/<mbi.vm>
When disk mirroring is enabled and when the BOOT_DEV_SEQ_OPER variable is set to BOOT_DEV_SEQ_OPER=disk0:,disk1:
Fail to open file name disk0/<mbi_image_path>/<mbi.vm>
Fail to open file name disk1/<mbi_image_path>/<mbi.vm>
A process called Turboboot is performed on the Cisco CRS routers to install Cisco IOS XR software into a persistent storage device for the first time. This persistent storage device subsequently diskboots the Cisco CRS router. When diskbooted, the router can be warm booted with a newer version of software, which might require a reload of the node.
The Turboboot errors appear when any one of the following conditions occurs:
If the bootflash is bad or missing on the active RP (at least in the Turboboot phase), the Turboboot operation fails with the following error messages:
TURBOBOOT: Failed to obtain turboboot parameters: 'Turboboot' detected the 'fatal' condition 'No devices that qualifies for boot device are found in the system'
TURBOBOOT: Resetting TURBOBOOT rommon variable to (TURBOBOOT=).
TURBOBOOT: Setting config-register to NOT autoboot the router and NOT disable send break.
TURBOBOOT: Failed reading/validating turboboot settings: 'Turboboot' detected the 'fatal' condition 'No devices that qualifies for boot device are found in the system'
If the bootflash on the standby RP is bad or missing, the installation encounters a fatal error condition and sends a message that ' bootflash is either corrupt or missing '.
NoteEnsure that all required bootflashes are present and working on all Cisco CRS routers before installing the new Cisco IOS XR software and the new ROM Monitor that supports split-boot.
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 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.
Use the following procedure to upgrade or downgrade 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.
NoteWe 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 command to determine if the ROM Monitor image on the card is compatible with the currently running Cisco IOS XR software release.
Before upgrading or downgrading ROM Monitor firmware, verify that the following prerequisites have been met:
FPD PIE is installed on your router. For more information on installing software PIEs, see the Upgrading and Managing Cisco IOS XR Software module of Cisco IOS XR System Management Configuration Guide for the Cisco CRS Router .
NoteIf the Cisco IOS XR software was upgraded to Release 3.9.0 or a later release before the ROMMON firmware was upgraded to a compatible version, and the standby RP fails to boot, clear the boot block with thehw-module boot override command in administration configuration mode. For more information, see Additional References.
b. (Optional) Repeat on each SDR impacted by the reload operation.
d. reload location all
12. show platform
Command or Action
show hw-module fpd location all
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.
Enters administration EXEC mode from EXEC mode.
show fpd package
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.
For ROMMON B:
upgrade hw-module fpd rommon location [ all | node-id ]
Upgrades the ROMMON B and ROMMON A images on the specified card ( node-id ) or all cards ( all ). You need to explicitly upgrade the ROMMON A using the hidden command, provided your ROMMON is earlier than Release 1.52.
Note Before you continue to reload the card, you should see a message indicating that the upgrade was completed successfully.
Warning Do not stop the upgrade or reload any cards while the upgrade process is in progress. It may corrupt the firmware making the card unbootable.
Exits administration EXEC mode and returns to EXEC mode.
If you are upgrading a single node on a router, including a standby DSDRSC, go to Step 9.
Continues to reload the node.
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.
If you are upgrading a router with a single RP, or want to perform a cold restart on all nodes, go to Step 11.
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. (Optional ) Use cfs check command to ensure the sanity of the configuration file system for the owner SDR.
b. ( Optional ) Repeat the cfs check command on the DSDRSC of each additional non-owner SDR in the system to verify the configuration file system for each non-owner SDR
c. Reloads the standby RP to activate the new ROMMON firmware.
Note The standby RP is the standby DSC for the system. The primary and standby DSCs are also the DSDRSCs for the owner SDR.
d. Use the show redundancy command to verify the redundancy status of the DSC nodes. Wait for the standby RP to return to “Ready” state.
e. Use the redundancy switchover command to cause the primary (active) RP to fail over to the redundant standby RP.
Note The standby RP must be ready to take over.
f. Use the show redundancy command to verify the status of the RP nodes. Wait for the standby RP to return to ready state.
g.Reload the original primary RP to activate the new ROMMON firmware.
h. (Optional) Repeat Step a. to Step g. on all DSDRSCs in the system to ensure a graceful restart for all SDRs.
i. Use the admin command to enter administration EXEC mode.
j. 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 such as fabric cards.
k.Use the hw-module location node-id reload command to reload each additional card where the ROMMON firmware was changed. Each node must be reloaded to activate the new ROMMON firmware.
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. Repeat Step k. to reload all upgraded nodes in the system.
m. 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.
Reload all nodes in the system (cold restart) :
a. cfs check
b. Repeat on each SDR impacted by the reload operation.
d. reload [ location all ]
RP/0/RP0/CPU0:router# cfs check
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 Reloading the primary RP (DSC) interrupts all service.
a. ( Optional ) Ensures the sanity of the configuration file system for the owner SDR.
b. ( Optional ) Ensures the sanity of the configuration file system for each non-owner SDR in the system.
c. Enters administration EXEC mode.
d. Reloads the DSDRSC with the upgraded ROM Monitor firmware. Use the reload location all command in administration EXEC mode to reload all nodes in the system.
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.
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: %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 both ROMMON 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.
Configuration Examples for ROM Monitor Upgrades
This section provides the following configuration examples:
SP/0/SM3/SP:Feb 20 15:58:25.656 : lc_fpd_upgrade: %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: Start Upgrade...
Cisco IOS XR Interface and Hardware Component Command Reference
System management commands
Cisco IOS XR System Management Command Reference
The Cisco Support website provides extensive online resources, including documentation and tools for troubleshooting and resolving technical issues with Cisco products and technologies.
To receive security and technical information about your products, you can subscribe to various services, such as the Product Alert Tool (accessed from Field Notices), the Cisco Technical Services Newsletter, and Really Simple Syndication (RSS) Feeds.
Access to most tools on the Cisco Support website requires a Cisco.com user ID and password.