Router Upgrade in INSTALL Mode

[TW80CJ5]

Good Morning...

Saw this fantastic link from Leo The Legend..

https://community.cisco.com/t5/networking-documents/cisco-isr-amp-asr-1k-routers-ios-xe-firmware-upgrade-install/ta-p/4426457

Quick question, after I set the packages.conf to boot, can I set the most recent .bin file to boot next? For example, if I am updgrading the router to 17.3.4 and using it install mode, can I set second boot variable to: boot system flash bootlfash:/17.3.4.bin?

Better example:

The sh boot would be: BOOT variable = flash:packages.conf,12; flash:/isr440v2-universal9.17.03.04a.SPA.bin

[balaji.bandi]

instead i would suggest to upgrade using install method :

copy the image to flash or bootflash
install add file flash:IOS_XE.bin activate commit

You need to consider from what version you like to upgrade, some time ROMMON need to be upgrade required.

read the release notes:

https://www.cisco.com/c/en/us/td/docs/routers/asr1000/release/notes/xe-17-3/asr1000-rel-notes-xe-17-3.html

[TW80CJ5]

Morning BB..

Thanks for the info. Yes, the router is already in INSTALL mode. I am asking if the router doesnt boot the packages.conf IOS for whatever reason, can the second boot variable be the 17.03.04.bin?

[balaji.bandi]

Honestly never tried that option. again if the current version running too old compare to 17.3.04.bin file, then the router go in to ROMMON.

why do you think package.conf go bad ? is this upgrade process ?

[TW80CJ5]

Well, I was thinking to have it as a backup option for booting...If something happened to the packages.conf file, then the .bin file would boot.

[balaji.bandi]

sh boot

flash:packages.conf,12; flash:/isr440v2-universal9.17.03.04a.SPA.bin

this should work for you, @Leo Laohoo thanks for confirming.

[Leo Laohoo]

---

@TW80CJ5 wrote:

BOOT variable = flash:packages.conf,12; flash:/isr440v2-universal9.17.03.04a.SPA.bin

---

Yes, it will work.  

[TW80CJ5]

Morning Leo...

Now you are bringing up something I need a little clarification on...In your previous posts you have mentioned the Cisco IOS XE strictly enforces the following: boot system flash bootflash:IOS_XE_FILENAME or you run the risk of booting into ROMMON.

I am trying to understand the difference between that and: boot system flash:IOS_XE_FILENAME

And to make sure clearly undertand the command including the packages.conf and .bin would be the following:

boot system flash bootflash:packages.conf

boot system flash:isr4400v2-universal9.17.03.04a.SPA.bin

sh boot

flash:packages.conf,12; flash:/isr440v2-universal9.17.03.04a.SPA.bin

Thanks for all of the help!

[Leo Laohoo]

---

@TW80CJ5 wrote:

Now you are bringing up something I need a little clarification on...In your previous posts you have mentioned the Cisco IOS XE strictly enforces the following: boot system flash bootflash:IOS_XE_FILENAME or you run the risk of booting into ROMMON.

---

In the first few years after IOS-XE was released the developers were "unaware" of the repercussions when they "insist" on using "boot system flash bootflash:" -- This change in behaviour was undocumented (CSCvg37458) and caught a lot of operators in a very embarrassing situation.  

This led the developers to allow the use of "flash:" (instead of "bootflash:") in later ROMMON version.  

For the safety sake, stick to "bootflash:" since no one knows if-and-when a develop would "remove" the fix.

[TW80CJ5]

Thanks Leo....

So the following:

boot system flash bootflash:packages.conf

boot system flash bootflash:isr4400v2-universal9.17.03.04a.SPA.bin

????????

[Leo Laohoo · Accepted solution]

---

@TW80CJ5 wrote:

boot system flash bootflash:packages.conf

boot system flash bootflash:isr4400v2-universal9.17.03.04a.SPA.bin

---

The syntax is correct.  Continue using it.

IMPORTANT: 

• Do not forget to check the contents of the packages.conf file using the command "more bootflash:packages.conf".  
• Do not forget to verify the boot statement:  sh boot

[TW80CJ5]

Thanks LEO!!!!!

[Leo Laohoo]

Can I impart a handy tip I teach new team members:  Console into the router, switch, AP, ASA, etc, look-n-learn at the output of each device(s) during bootup. 

It is not as "boring" as anyone thinks.  This forum/community is filled with problems that were easily fixed just by looking at the "boring" bootup processes.  

[TW80CJ5]

Hey Leo...

I couldn't agree more. You can learn a lot about a device by watching it boot up. What's normal and not...

Matter of fact, I used the forum's to figure out why my ISR 4461 was booting with no config after upgrading into install mode with 17.03.04 (see previous posts    )

And whaddya know: I needed to enter: controller-mode disable. I set the latest running config to start and rebooted. All is well.

Thanks again for all of the help!