B-6
Cisco CRS-1 Series Carrier Routing System Getting Started Guide
Appendix B Upgrading and Downgrading ROM Monitor Software
Configuration Examples for ROM Monitor Upgrades
Troubleshooting Tips
• If any node cannot be upgraded successfully or if you see error messages similar to the following
message, try reformatting the bootflash (format bootflash: [location all | nodeID]) 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 only ROMMONB and the version does not change to the expected version after
the upgrade, the upgrade might have failed. When the router cannot load ROMMONB, it will load
ROMMONA.
• If both ROMMANB and ROMMONA are damaged due to unexpected node reset or 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:
• ROM Monitor Upgrade: Example, page B-7
Step 16
reload
Reloads the RP in a single RP router with the upgraded
ROM monitor software.
Note Reloading a single RP router will interrupt all
service.
Step 17
Go to Step 19.—
Step 18
hw-module node nodeID reload
Example:
RP/0/RP0/CPU0:Router# hw-module node 0/RP0/CPU0
reload
Reloads a single node within a router with the upgraded
ROM monitor software.
• Replace nodeID with the node ID you specified when
upgrading ROM monitor.
Step 19
show diag
Example:
RP/0/RP0/CPU0:Router# show diag
Displays hardware information and ROM monitor
information for each node in the router.
• Review the command display and verify that the
appropriate nodes are using the upgraded version of
ROM monitor.
Command or Action Purpose
To Next Page
Loading...
Need help?
General
