[c-nsp] 4500X in VSS - Upgrading IOS XE

CiscoNSP List CiscoNSP_list at hotmail.com
Tue Apr 5 19:20:29 EDT 2016

Disconnecting VSS/removing VSS/VSL conf was a recommendation from TAC(For a non ISSU upgrade)....which sounded like a very unusual requirement lol.....hence my question here.


From: Garrett Skjelstad <garrett at skjelstad.org>
Sent: Wednesday, 6 April 2016 8:35 AM
To: CiscoNSP List
Cc: cisco-nsp at puck.nether.net
Subject: Re: [c-nsp] 4500X in VSS - Upgrading IOS XE

Why would you need to disconnect the VSS link? We've upgraded them successfully from 3.6 to 3.7 without disconnecting the VSS links and reloading them individually.

On Tue, Apr 5, 2016 at 2:22 PM, CiscoNSP List <CiscoNSP_list at hotmail.com<mailto:CiscoNSP_list at hotmail.com>> wrote:

Hi Everyone(Sent this to the list yesterday, but it still hasnt shown up?  So re-sending),

I need to upgrade IOS XE on a pair of 4500X's...Id prefer not to try/use ISSU, as they are remote switches and in production....so Im hoping someone has performed an upgrade on these boxes(In VSS) and can provide some guidance on a method that "works" :)

Ive read where people disconnect the VSS link (Or shutdown those ports), and perform the upgrade on the 2 switches, then reconnect VSS....but could you do something like this:

conf reg on both switches is already set to 0x2102, so the switches should honour the bootvar variables

copy new IOS XE to bootflash & slavebootflash

update boot var to point to new XE image

boot system flash bootflash:xxx

wr mem and check bootvar is updated

and reload both switches:

redundancy reload shelf

This should reload both switches, and they should come up with the new image, and VSS should re-establish?

Thanks in advance for any advice/recommendations

cisco-nsp mailing list  cisco-nsp at puck.nether.net<mailto:cisco-nsp at puck.nether.net>
archive at http://puck.nether.net/pipermail/cisco-nsp/

More information about the cisco-nsp mailing list