Buy or Renew
Buy or Renew
cancel
Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
Showing results for 
Search instead for 
Did you mean: 
cancel
Start a conversation
8657
Views
12
Helpful
15
Replies

IOS-XE upgrade discussion - "install" mode vs. "request platform"

Go to solution
vv0bbLeS
Level 1
Level 1

‎03-08-2023 05:23 PM - edited ‎03-08-2023 05:28 PM

Hello all,

In terms of doing IOS-XE software upgrades, there are 2 ways to do it - the install mode way, or the request platform way. @Leo Laohoo has written some great guides for upgrading ISR models with request platform and upgrading Cat 9k models with install mode (See attached file).

The bummer about install mode is that it's very difficult to schedule a reboot, it's kind of an all-or-nothing thing. With the request platform method however, you can unpack the files beforehand, and then run a simple reload command when you're ready to upgrade.

My question is, can you use the request platform method on any device running IOS-XE ? If so, wouldn't that be the preferred method since it's so easy to schedule your reboots? Why would anyone use the install mode?

0xD2A6762E
Labels:
Preview file
525 KB
0 Helpful
1 Accepted Solution

Accepted Solutions

Go to solution
Leo Laohoo
Hall of Fame
Hall of Fame

‎03-08-2023 06:36 PM - edited ‎07-09-2023 11:12 PM

@vv0bbLeS wrote:
The bummer about install mode is that it's very difficult to schedule a reboot, it's kind of an all-or-nothing thing. 

There is a "NSFW" (aka, not "recommended" by Cisco) method to do the Install Mode, using the "install add file", and schedule the reboot at a later date without using DNAC or PI.  

It is "NSFW" not because it is not documented officially by Cisco.  I call it "NSFW" because once the command is entered, no one should touch the keyboard after that.  I will explain this shortly.

IMPORTANT: 

  • Read and understand the steps below first.  
  • I call the following method the "one-hit-wonder" because I am going to combine all three process (unpacking, commit and activate) in one "go". 

Install Mode (NSFW + One-Hit-Wonder) Steps:

1.  Copy the (firmware) file into the switch.  For VSS switch, just copy the file into the Active switch.

2.  Invoke the command:  

 

install add file bootflash:filename.bin activate commit

 

WARNING:  DO NOT TOUCH THE KEYBOARD

3.  About three minutes into the process, the system will pause and ask a "y/n" question.  It is of the utmost importance the operator must press "N" or "n".   (Press any key other than the "n" or "N" and it can potentially cause the switch stack to continue the process and reboot.)

4.  About 2 minutes after pressing the "N" or "n", the process will come to an abrupt halt.  This is to be expected.  

5a.  Enter the command "dir flash:*.conf".

5b.  (VSS)  Enter the command "dir stby-bootflash:*.conf"

6.  In steps 5a &/or 5b, pay attention to two files in particular, they are:  packages.conf and the "destination".conf file.  The destination file is the firmware to upgrade to, example if I was upgrading to 17.9.2, the file would be called cat9k_iosxe.17.09.02.SPA.conf.

7a.  Rename the packages.conf file to be something else: 

 

rename flash:packages.conf flash:packages.conf.00-

 

7b.  (VSS) 

 

rename stby-bootflash:packages.conf stby-bootflash:packages.conf.00-

 

8a  Rename the destination file to be the new packages.conf file:  

 

rename flash:cat9k_iosxe.17.06.04.SPA.conf flash:packages.conf

 

8b (VSS)