Solved: Re: VSS - Catalyst 4500 - Rollback

inteldarvid · ‎01-03-2023

hi team

good morning

Team, I have some doubts about VSS, I'm about to upgrade the version of a WS-C4506-E catalyst switch, but I don't have a procedure in case the update fails.

Team, is there a rollback procedure due to failure to upgrade the version in a vss?

Thank you

regards,

Leo Laohoo · ‎01-03-2023

So this is how we've "formulated" the method to upgrade the ROMMON and the IOS in one reboot/reload:

NOTE: 4500X IOS-XE comes in two file extensions: BIN or TAR. Make sure to get the TAR file extension!

1. Upload the IOS-XE to the active unit: archive tar /x tftp://<TFTP IP_Address>/IOS_filename.tar bootflash:
2. Upload the IOS-XE to the secondary unit: archive tar /x tftp://<TFTP IP_Address>/IOS_filename.tar slavebootflash:
3. Copy the ROMMON file to the active unit: copy ftp://<TFTP IP_Address>/IOS_filename bootflash:
4. Copy the ROMMON file to the secondary unit: copy ftp://<TFTP IP_Address>/IOS_filename slavebootflash:
5. Change the boot variable string: Remove all the "old" boot variable string, insert a new boot variable string to point to the ROMMON file, point another boot variable string to point to the NEW IOS and then put another boot variable string to point to the old IOS

conf t
 no boo system bootflash:old_ios.bin
 boot system bootflash:ROMMON_filename
 boot system bootflash:NEW_IOS_filename.bin
 boot system bootflash:OLD_IOS_filename.bin
end

6. Make sure boot variable string is "0x2102"
7. Save the config
8. Reboot

OPTIONAL:
1. Check the MD5 hash of the IOS files (including the ROMMON) using the command "verify /md5 bootflash:filename.bin <MD5 hash from the Cisco website>"
2. Backup the config to somewhere external.
Hope this helps.

View solution in original post

balaji.bandi · ‎01-03-2023

The role back same way the one we discussed other post. since image already in the chasis. you need to move back your boot system to old and reload.

Also see any gotachas in release notes, i am sure you never required roleback plan - until something really gone bad.

Other approach if you are so concerned and worried.

you can reload standby that will prove everything working as expected, before other shelf you can reboot by switching over.

also refer :

Upgrade the Software Images on Redundant Supervisor Modules Without a System Reload

https://www.cisco.com/c/en/us/support/docs/switches/catalyst-4000-series-switches/27848-179.html

BB

***** Rate All Helpful Responses *****

How to Ask The Cisco Community for Help

Leo Laohoo · ‎01-03-2023

So this is how we've "formulated" the method to upgrade the ROMMON and the IOS in one reboot/reload:

NOTE: 4500X IOS-XE comes in two file extensions: BIN or TAR. Make sure to get the TAR file extension!

1. Upload the IOS-XE to the active unit: archive tar /x tftp://<TFTP IP_Address>/IOS_filename.tar bootflash:
2. Upload the IOS-XE to the secondary unit: archive tar /x tftp://<TFTP IP_Address>/IOS_filename.tar slavebootflash:
3. Copy the ROMMON file to the active unit: copy ftp://<TFTP IP_Address>/IOS_filename bootflash:
4. Copy the ROMMON file to the secondary unit: copy ftp://<TFTP IP_Address>/IOS_filename slavebootflash:
5. Change the boot variable string: Remove all the "old" boot variable string, insert a new boot variable string to point to the ROMMON file, point another boot variable string to point to the NEW IOS and then put another boot variable string to point to the old IOS

conf t
 no boo system bootflash:old_ios.bin
 boot system bootflash:ROMMON_filename
 boot system bootflash:NEW_IOS_filename.bin
 boot system bootflash:OLD_IOS_filename.bin
end

6. Make sure boot variable string is "0x2102"
7. Save the config
8. Reboot

OPTIONAL:
1. Check the MD5 hash of the IOS files (including the ROMMON) using the command "verify /md5 bootflash:filename.bin <MD5 hash from the Cisco website>"
2. Backup the config to somewhere external.
Hope this helps.

inteldarvid · ‎01-09-2023

Thank you

regards,