Cisco 9500-48Y4C IOS Upgradation

[Ganesh Devarshetty]

Today we have got maintenance window to perform cisco 9500 ios upgradation which is configured in stackwise virtual.

I have some doubts regarding IOS procedure for cisco 9500

We are using the install mode for IOS upgradation.

Thing is that i don't want to use the ISSU method for ios upgradation.Want to use the normal method.

If i'm going via normal method it is mandatory to load the IOS image in standby device or it will be pushed automatically.

Can you please help .

[balaji.bandi]

If you have physical access you can connect to the console - capture the logs in case anything go wrong.

Steps we follow most of the time work :

1. take the config backup out of the box (local Drive)

2. read the release notes carefully and understand any caveats

3. clean up the free space.

# install remove inactive

4. copy tftp:[[//location]/directory]/filename flash:

5. Verify the image in flash
# dir flash:*.bin

if you like you can also verify MD5 checksum.

6. Make sure show boot ( check Manual_Boot variable = No)

7. install add file flash:cat9k_iosxe.17.09.01.SPA.bin activate commit  ( change bin file depends on the requirement and file you looking to upgrade version).

at this stage do not not do anything on the keyboard - leave it as the installation go automatically

Note	The system reloads automatically after executing the install add file activate commit command. You do not have to manually reload the system.

Note : if you upgrading from older version - the ROMMON Upgrade automatically and you can not downgrade ROMMON (this is not an issue even if you like to downgrade.)

Once upgrade completed and verified 

clean up bin files :

# install remove inactive

[Ganesh Devarshetty]

Thanks for the reply.

There are two methods to IOS upgrade 9500 switches

1.Normal Method.

2.ISSU

I want to upgrade the switch via normal method.Is it mandatory to upload the ios image in both active and standby switches configured together in stackwise.

Can you please answer.

install add file flash:cat9k_iosxe.17.09.01.SPA.bin activate commit

install add file flash:cat9k_iosxe.17.09.01.SPA.bin activate issu commit

[balaji.bandi]

The steps provided are - Normal Method.

Is it mandatory to upload the ios image in both active and standby switches  -  not required. ( part of installation it automatically copy the image to chasis2 (standby switch)

install add file flash:cat9k_iosxe.17.09.01.SPA.bin activate commit  - this command take care of copy all files to rest of the members.

[Leo Laohoo]

---

@Ganesh Devarshetty wrote:
There are two methods to IOS upgrade 9500 switches

1.Normal Method.

2.ISSU

---

No, there are THREE (3) methods. 

"Normal Method" is the recommended method by Cisco and this will immediately reboot the platform. 

A third method, I call Install Mode (NSFW + One-Hit-Wonder) , unpacks the packages but will give the operator the benefit of rebooting the platform at a later date.  

NOTE:  

1.  I just completed firmware upgrading about 80 x 9500 (stand alone & VSS) to 17.9.4a (Install Mode) & without using DNAC, ISSU, FSU/eFSU/xFSU.  I uploaded the firmware (and unpacked the packages) back in December 2023 and scheduled the reboot for 03 January 2024 -- I did all this using the NSFW + One-Hit-Wonder method.

No failure.  

2.  Depending on what the current firmware the 9500 VSS is now, the VSS "location" has different names.  For "consistency" reasons, Cisco calls them "bootflash-2:" or "flash-2:" or "stby-bootflash:".  Check this one out before doing anything. 

3.  There is a known bug feature with the Cisco-recommended process.  During the unpacking of the packages, sometimes the "packages.conf" locks up and the process will not be able to rename the file.  And because the operator has entered "y", there is no way to see or check if this is happening.  This results in the platform rebooting to the old firmware.  However, the NSFW + One-Hit-Wonder avoids this because the renaming of the "packages.conf" file is done manually, plus, there is a check and verification at the end of the process.