The ROMMON upgrade process, while generally straightforward using the upgrade rom-monitor filename command, requires patience and potentially multiple reload cycles to complete successfully. When issues arise, the Cisco support community and bug search tools provide valuable troubleshooting resources for resolving upgrade failures and compatibility problems.
In some cases, the upgrade process appears to complete successfully, with the router displaying messages like "ROMMON upgrade complete" and verifying the CRC checksum. However, after performing a reload and multiple reboot cycles, the ROM monitor version remains at the older version despite appearing to have been upgraded.
Expected output: ROMMON Version: 173-1r
Before diving into procedures, let’s decode the filename. Cisco’s naming convention is deliberate and informative.
report the upgrade getting "stuck" or failing on older RP1 modules, suggesting that unless your target IOS XE version strictly requires it, sticking with a stable older version like 16.3(2r) might be safer for older hardware. Boot Order Requirement: It is universally recommended by experts to upgrade the ROMmon first asr1000-rommon.173-1r.spa.pkg
If you need help with the , or want to know the minimum required version before upgrading to 17.3 , I can also:
Note: The all keyword ensures both primary and secondary/backup ROMMON regions are updated on dual RP systems. However, after performing a reload and multiple reboot
An active console connection is required, as the upgrade will disrupt network management connectivity.
If you want, I can: