IOS upgrade on asr9xx mandates rommon upgrades sometimes while they can be optional at other times. You may land up in unwanted situation if proper procedure is not followed during upgrades.
This article will include complete details about rommon upgrades on asr9xx platforms b/w different IOS-XE releases
Old method of upgrading rommon (Before 17.3.x) -
1. Check the RSP bootup ROMMON region (ROM0 or ROM1). The example, shows the RSP boots up from ROM0 region
System Bootstrap, Version 15.2(1r)S1, RELEASE SOFTWARE (fc1)
Technical Support: http://www.cisco.com/techsupport
Copyright (c) 2011 by cisco Systems, Inc.
Compiled Wed 07-Dec-11 07:33 by tinhuang
Current image running: Boot ROM0
2.Copy the ROMMON image to the bootflash on the active and standby RSP.
3.Use the "upgraderom-monitorfilename bootflash:rsp2_15_6_18r_s_rommon.pkgR0" command to upgrade the version.
Note - R0 represents RSP in slot0 of the chassis. Step 3 upgrades the ROMMON region of the RSP that is not used (ROM1 region) as ROM 0 region is used (in this procedure) in Step 1 to boot up the RSP.
4. Reload the router.
5. Repeat Step 3 to Step 5 to update the other region on the RSP (ROM0) region in this procedure.
Note - We recommend that both region ROM0 andROM1 are upgraded.
Above mentioned steps will upgrade both the rommon regions on a single RSP. For upgrading dual RSP system follwing procedure can be utilized to minimize impact -
Upgrade both the rommon regions on standby RSP (say R1)
Upgrade both the rommon regions on (new standby) previous active RSP (say R0)
You can minimize downtime by upgrading only one region of rommon with currently running IOS on the router and reloading router with new (target) IOS. Second rommon region can be upgraded on new IOS and required router reload can be done any time later during a planned/unplanned MW.
Auto rommon upgrade - New method of upgrading rommon (17.3.2 and beyond) -
ISSU Based Upgrades -
1. Starting 17.3.1 Primary rommon region gets automatically upgraded during IOS upgrade .however secondary region still needs to be upgraded manually (via procedure mentioned in old method above) …reload for the second region can be done later anytime (i.e. as part of any other MW)
2. Starting 17.4.1 ..both the rommon regions will automatically get upgraded with IOS upgrade when needed. User does not have to worry about upgrading rommon at all.
Minimum required rommon version for auto rommon upgrade functionality to work is 33r. If the current rommon version on any device is lower than 33r then it will have to be first manually upgraded to 33r.
Note - If you are running an old IOS (prior to 16.11.1) having rommon version < 33r and would like to to software upgrade to 17.3.1 and beyond via ISSU then you will need to do step ISSU upgrade in two steps-
i) ISSU upgrade to 16.9.6 or 16.12.5
ii) ISSU upgrade to 17.3.1 and beyond.
Note - For ASR920 upgrades please look at the following software advisory -
Hello everyone,I have a ASR 920 (ASR-920-12SZ-IM) currently on loan from the Amsterdam Demo Depot and I would need some help in configuring ethernet virtual connections. I have no experience in configuring these services. I have attached a drawing to...
Hi, Guys, There are two SRMS servers in the network, I wonder how SRMS Clients select the one of SRMS server as the active one, what's the election factors and how could i specify the one of SRMS server as the active server, the another one as redund...
On ASR-9904 Chassis with RSP5-SE. I was under the impression that the RSP - Chassis combo could support 1.8T per line card. However, when a A9K-8X100GE-TR is inserted, I get RATE LIMITED message. %FABRIC-FIA-1-RATE_LIMITER_ON : Set|fialc[...
Hey folks, I am trying to configure an intra-domain PCE/PCC setup with headend initiated ODN policy. It looks like PCEP is up and report messages gets delivered to the PCE, however it looks like the update messages aren't there and the ERO from PCC to PCE...