The router will extract the package file and program the field-programmable gate array (FPGA) / ROMMON flash block. A successful write will return a confirmation message indicating that the new ROMMON will take effect upon the next reload. Step 4: Reload the Router To execute the microcode change, reload the chassis: Router# reload Use code with caution. 5. Post-Upgrade Verification
Modifying system firmware carries inherent risks. Follow these steps meticulously to ensure a successful upgrade. Step 1: Download and Verify the Package
Router# copy tftp: bootflash: Address or name of remote host []? 192.168.1.5 Source filename []? asr1000-rommon.173-1r.spa.pkg Destination filename [asr1000-rommon.173-1r.spa.pkg]? Use code with caution. Copied to clipboard Step 2: Run the Upgrade Command
A specific bug (CSCvz87460) affects ASR 1002 routers with RP2 processors (specifically those with a Version Identifier of V07 or higher). Users often see a "FAILURE: MD5 signature does not match!" asr1000-rommon.173-1r.spa.pkg
Before initiating the upgrade, gather system data to ensure a smooth deployment. Run these commands from the Cisco IOS XE Exec prompt: 1. Check Current ROMMON Version Router# show platform | include ROMMON Use code with caution.
Before proceeding with the upgrade, engineers should verify compatibility by consulting the official documentation:
Let's break down the specific filename: asr1000-rommon.173-1r.spa.pkg . The router will extract the package file and
Use TFTP, FTP, or SCP to move the .pkg file to the bootflash: of your ASR 1000 router.
As with all firmware updates, the 173-1r package fixes potential boot-time security vulnerabilities and improves the reliability of the hardware initialization process, ensuring that the router starts up consistently in high-availability scenarios. Preparation: Pre-Upgrade Checklist
ROMMON 17.3(1r) serves as a foundational requirement for newer IOS-XE releases. For example: Step 1: Download and Verify the Package Router#
If a chassis with redundant RPs experiences sync issues post-upgrade, ensure both R0 and R1 were successfully targeted with the upgrade command. You can check the secondary RP status via show platform diag .
Before upgrading, check your current ROMMON version: