VSS IOS Upgrade for (WS-C4500X-32 X 2) and (WS-C4507R+E with Sup 7-E x 2)

[Alan.A]

Hi Experts,

I need your input to check if my procedure are correct. I will be upgrading our switches but I want to reload the entire chassis to make the upgrade simple. Below are the sequence. Please let me know your feedback. thank you

Step 1: Copy the rommon image to the bootflash
copy ftp://<username>:<password>@10.X.X.X/firmwareupgradeallK10-150_1r_SG15.SPA bootflash:

Step 2: Copy the rommon image to the slavebootflash
copy ftp://<username>:<password>@10.X.X.X/firmwareupgradeallK10-150_1r_SG15.SPA slavebootflash:

Step 3: Verify the rommon image in bootflash
verify /md5 bootflash:firmwareupgradeallK10-150_1r_SG15.SPA b0bb463b920172c6de4006944a80b1df

Step 4: Verify the rommon image in slavebootflash
verify /md5 slavebootflash:firmwareupgradeallK10-150_1r_SG15.SPA b0bb463b920172c6de4006944a80b1df

Step 5: Copy the new Image to the bootflash
copy ftp://<username>:<password>@10.X.X.X/cat4500e-universalk9.SPA.03.11.04.E.152-7.E4.bin bootflash:

Step 6: Copy the new Image to the slavebootflash
copy ftp://<username>:<password>@10.X.X.X/cat4500e-universalk9.SPA.03.11.04.E.152-7.E4.bin slavebootflash:

Step 7: verify the new Image in bootflash:
verify /md5 bootflash:cat4500e-universalk9.SPA.03.11.04.E.152-7.E4.bin a08e94e32a290080d7e5bed405e8866c

Step 8: Verify the new Image in slavebootflash
verify /md5 slavebootflash:cat4500e-universalk9.SPA.03.11.04.E.152-7.E4.bin a08e94e32a290080d7e5bed405e8866c

Step 9: Set the boot variable
conf t
no boot system
boot system flash bootflash:firmwareupgradeallK10-150_1r_SG16.SPA
boot system flash bootflash:cat4500e-universalk9.SPA.03.11.04.E.152-7.E4.bin (new image)
boot system flash bootflash:cat4500e-universalk9.SPA.03.06.08.E.152-2.E8.bin (existing image)
end
show bootvar

Step10: Make sure Configuration register is 0x2102

Step11: Save the configuration and reload the switch by the command "redundancy reload shelf"
(I want to reload the entire chassis but I'm not sure if command "reload" can do that that is why I will issue the "redundancy reload shelf")

Step 12: After reload and once the new image is verified delete the rommon firmware and old image from bootflash and slavebootflash
delete bootflash:/firmwareupgrade-151_1r_SG18.SPA
delete slavebootflash:/firmwareupgrade-151_1r_SG18.SPA
delete bootflash:/cat4500e-universalk9.SPA.03.06.08.E.152-2.E8.bin
delete slavebootflash:/cat4500e-universalk9.SPA.03.06.08.E.152-2.E8.bin

Step 13: Update the boot variable by removing the rommon firmware and old image

conf t
no boot system
boot system flash bootflash:cat4500e-universalk9.SPA.03.11.04.E.152-7.E4.bin
end

show bootvar

Step 14: Wr mem

Note: I will be doing this via ssh but I'm in front of the chassis, I will just console the switch if needed.

[balaji.bandi · Accepted solution]

All good

Step10: Make sure Configuration register is 0x2102

After this step - save config and reboot (reload - whole VSS that is what you want to as per message)

no step 11 reload shelves rquired, if you reload whole VSS

[Alan.A]

Thank you Balaji. I will give feedback tomorrow.

 Do you know why the image (cat4500e-universalk9.SPA.03.11.04.E.152-7.E4.bin) is not a goldstar in catalyst C4507R+E? and it is a goldstar for 4500-x-32 in software.cisco.com?

[balaji.bandi]

Not sure not reviewed since Long,

Note : Beofre upgrade look and read the release notes, make sure this is not effecting your environement.

[Leo Laohoo]

---

@Alan.A wrote:

Do you know why the image (cat4500e-universalk9.SPA.03.11.04.E.152-7.E4.bin) is not a goldstar in catalyst C4507R+E? and it is a goldstar for 4500-x-32 in software.cisco.com?

---

Cisco moves the "star" based on the volume of TAC Cases so it is really not an "indicator" that the version is "stable".  

Pick a version and read the Release Notes.  If it is possible, test the firmware before deploying.  

[Alan.A]

when I issue a "reload" command only the standby is reloading and it keeps on rebooting.. 

I can still access the active switch. this is 4500-X

*May 14 21:07:45.026: %VSLP-5-RRP_ROLE_RESOLVED: Role resolved as STANDBY by VSLP
*May 14 21:08:22.444: %C4K_REDUNDANCY-2-IOS_VERSION_CHECK_FAIL: STANDBY:IOS version mismatch. Active supervisor version is 15.2(5)E (cat4500e-UNIVERSALK9-M). Standby supervisor version is 15.2(7)E4 (cat4500e-UNIVERSALK9-M). Redundancy feature may not work as expected.
*May 14 21:08:22.444: %C4K_REDUNDANCY-2-NON_SYMMETRICAL_REDUNDANT_SYSTEM: STANDBY:STANDBY supervisor will operate in fallback redundancy mode rpr.
*May 14 21:08:26.482: %C4K_REDUNDANCY-3-COMMUNICATION: STANDBY:Communication with the peer Supervisor has been established
*May 14 21:08:27.470: %C4K_REDUNDANCY-2-VS_REBOOT_ON_RPR_FALLBACK: STANDBY:Supervisor in virtual-switch configuration cannot operate in redundancy mode RPR, will be reset
*May 14 21:08:27.715: %RF-5-RF_RELOAD: STANDBY:Self Reload. Reason: Virtual-switch fallback to RPR
*May 14 21:08:27.750: %SYS-5-RELOAD: STANDBY:Reload requested by Platform redundancy manager. Reload Reason: Virtual-switch fallback to RPR.
<Fri May 14 21:08:27 2021> Message from sysmgr: Reason Code:[3] Reset Reason:Reset/Reload requested by [console]. [Reload command]

[Leo Laohoo]

---

@Alan.A wrote:

when I issue a "reload" command only the standby is reloading and it keeps on rebooting.. 

---

Because the primary is running an old version and the secondary is running a different version.

[Alan.A]

I decided to boot to the old image and when everything back to normal. issue the command“redundancy reload shelf” after that both chassis rebooted and upgrade went successful.