User comments to blog posts.
seguse
New Member
Posts:
5
Joined:
Wed Aug 21, 2013 12:32 am
Certs:
A+, Net+, Security+, Server+, CCNA

Re: Upgrading with ISSU

Mon Aug 26, 2013 10:09 pm

How to you do an IOS upgrade on a VSS pair but NOT using the ISSU procedure?

Reload the active unit and then reload the standby unit (now active) 30 seconds later?

User avatar
burnyd
Post Whore
Posts:
3160
Joined:
Fri Nov 13, 2009 5:15 pm
Certs:
CCIE R&S/SP,CCNP-SP,JNCIA,VCP510,VCA-DCV

Re: Upgrading with ISSU

Tue Aug 27, 2013 7:38 am

my issue was funny. Turns out someone did not plug in the mgt port on the redundant sup.. So when it flipped over again I could not get into it again.
http://danielhertzberg.wordpress.com - I blog about networks!

seguse
New Member
Posts:
5
Joined:
Wed Aug 21, 2013 12:32 am
Certs:
A+, Net+, Security+, Server+, CCNA

Re: Upgrading with ISSU

Wed Aug 28, 2013 4:36 pm

seguse wrote:How to you do an IOS upgrade on a VSS pair but NOT using the ISSU procedure?

Reload the active unit and then reload the standby unit (now active) 30 seconds later?

To answer my own question...yes, this is how you would upgrade the ios using the non-issu upgrade procedure.

seguse
New Member
Posts:
5
Joined:
Wed Aug 21, 2013 12:32 am
Certs:
A+, Net+, Security+, Server+, CCNA

Re: Upgrading with ISSU

Wed Aug 28, 2013 5:39 pm

Crazy thing happened during a non-issu ios downgrade of my 4507R+E VSS pair. I was troubleshooting a bug with wccp with another cisco tac case and the cisco engineer said to downgrade my current code from 03.04.01.SG.151-2.SG1 to 03.03.00.SG.151-1.SG due to wccp was first introduced into the 4500 series code then. I should have caught this right away because vss was first introduced in 03.04.00.SG.151-2.SG code.

As you can imagine...everything was running fine on my 03.04.01 code and then setup everything to boot from the 03.03.00 code. After the reload process of both switches...they started to boot and scrolling and scrolling of "invalid interface" kept going on the screen. This of course got me worried and after it finished booting, I went and changed the boot statement to boot the latest code again and reloaded both switches. Which then put this on the screen...

********************* CAUTION ************************
* *
* Switch is booting up in VSS mode but *
* startup-config is being ignored. Autoboot is *
* disabled and now dropping into ROMMON. *
* *
* Please configure the switch for not ignoring *
* startup-config if it is needed to work in VSS Mode *
* OR *
* clear VS_SWITCH_NUMBER rommon variable to boot *
* the switch in standalone mode. *
*****************************************************

*Aug 28 03:13:16.593: %RF-5-RF_RELOAD: Self Reload. Reason: Startup-config ignore not allowed in VSS mode
*Aug 28 03:13:16.687: %SYS-5-RELOAD: Reload requested by Platform redundancy manager. Reload Reason: Startup-config ignore not allowed in VSS mode.Please stand by while rebooting the system...
Restarting system.

Each switch then went into ROMMON mode. From the so-called help it says to "clear VS_SWITCH_NUMBER". So I typed out...

rommon 1 >clear VS_SWITCH_NUMBER
Clear commands:

clear boot clear BOOT variable
clear bootldr clear BOOTLDR variable
clear config use 'clear config help' for more info
clear ip use 'clear ip help' for more info
clear issu_boot clear ISSU_BOOT variable

I see no where this VS_SWITCH_NUMBER. I had to get on the line with Cisco TAC and get them to help out. So the first thing he did was change that VS_SWITCH_NUMBER...

rommon 3 >set
PS1=rommon ! >
RommonVer=15.0(1r)SG5
SupportedFeatures=1
Fa1Enable=1
DiagMonitorAction=Normal
VS_SWITCH_NUMBER=1
DebugCallHome=00000
BOOT=bootflash:cat4500e-universalk9.SPA.03.04.01.SG.151-2.SG1.bin,12;
BootedFileName=bootflash:cat4500e-universalk9.SPA.03.04.01.SG.151-2.SG1.bin
ConsecPostPassedCnt=30
ConfigReg=0x2100
RET_2_RTS=03:21:20 UTC Wed Aug 28 2013
RET_2_RCALTS=1377660080

rommon 4 >VS_SWITCH_NUMBER=0

rommon 5 >set
PS1=rommon ! >
RommonVer=15.0(1r)SG5
SupportedFeatures=1
Fa1Enable=1
DiagMonitorAction=Normal
DebugCallHome=00000
BOOT=bootflash:cat4500e-universalk9.SPA.03.04.01.SG.151-2.SG1.bin,12;
BootedFileName=bootflash:cat4500e-universalk9.SPA.03.04.01.SG.151-2.SG1.bin
ConsecPostPassedCnt=30
ConfigReg=0x2100
RET_2_RTS=03:21:20 UTC Wed Aug 28 2013
RET_2_RCALTS=1377660080
VS_SWITCH_NUMBER=0
rommon 6 >

The next thing he did was change the config-register to 0x2102 with the ROMMON command "confreg" and reloaded the switch. Once the switch was re-loading he pressed CTRL+C to prevent autobooting and then manually booted the latest ios using the ROMMON command rommon 3 >boot bootflash:cat4500e-universalk9.SPA.03.04.01.SG.151-2.SG1.bin

The IOS finally came back but it was in standalone mode. At this point we had to re-build the VSS domain and VSL links manually as "some" of the configuration got erased. Everything under the physical interfaces seemed to get erased. After we re-built the vss domain and VSL links we converted the standalone switches into vss again and reloaded both of them. They finally came back to being the happy vss pair they were before. Except, all the physical interface config settings were gone. I had to manually paste the settings in and luckily I backed up the config before I started.

Never ever downgrade a vss pair below 03.04.00.SG.151-2.SG or you will live the hell I went through for 4 hours.

'
Previous

Return to Blog Comments

Who is online

Users browsing this forum: No registered users and 13 guests