upgrade 6807 in VSS Quad-SUP using ( Fast Software Upgrade )

[dqalib23]

HI,

Planning to upgrade 6807 in VSS Quad-SUP using ( Fast Software Upgrade )
From version s6t64-adventerprisek9-mz.SPA.155-1.SY7 TO s6t64-adventerprisek9-mz.SPA.155-1.SY10.bin

Have few hours of maintenance window and would like to know best approach for this .

Sups are in slot 3/4 on each 6807 see attached config :
1) Can someone kindly confirm the directories I need to upload the new image to as cisco doc says (disk0: and slavedisk0:) ?

---------https://www.cisco.com/c/en/us/td/docs/switches/lan/catalyst6500/ios/15-5SY/config_guide/sup6T/15_5_sy_swcg_6T/enhanced_fast_software_upgrade_efsu.html

2) and finally is this guide all I need in this or is there more ?

---------https://www.cisco.com/c/en/us/td/docs/switches/lan/catalyst6500/ios/15-5SY/config_guide/sup6T/15_5_sy_swcg_6T/enhanced_fast_software_upgrade_efsu.html

Thanks

[Reza Sharifi]

Hi,

If you are trying to load it to the internal flash, it should be bootdisk: and slavebootdisk: and not disk0.

BOOT variable = bootdisk:s6t64-adventerprisek9-mz.SPA.155-1.SY7.bin,12;bootdisk:s6t64-adventerprisek9-mz.SPA.155-1.SY5.bin,12;

HTH

[dqalib23]

-

[Leo Laohoo]

Please avoid ISSU/FSU/eFSU/xFSU.  ISSU/FSU/eFSU/xFSU only works in "corner cases", labs or in demo.  When it fails, it will fail in a spectacular fashion. 

If someone is still h!llbent with ISSU/FSU/eFSU/xFSU regardless, make sure TAC is on a WebEx call so they can see for themselves when the process eventually fails.  

[dqalib23]

Do you suggest I go with 

FPGA Upgrade

www.cisco.com/c/en/us/td/docs/switches/lan/catalyst6500/ios/15-5SY/config_guide/sup6T/15_5_sy_swcg_6T/enhanced_fast_software_upgrade_efsu.html#40201

[Leo Laohoo]

That will depend on the line cards.  

ISSU/FSU/eFSU/xFSU do not support manual FPGA upgrade.  

Make sure to have console access to both units.  

[dqalib23 · Accepted solution]

HI Leo 

Thanks allot for your time , one more thing I have put together below steps for the upgrade any comments ?

1) Copy the IOS to the primary bootflash:
----------
Copy tftp://suchAndSuch/s6t64-adventerprisek9-mz.SPA.155-1.SY10.bin bootdisk:/
----------
2) Copy the IOS to the secondary bootflash:
----------
copy bootdisk:s6t64-adventerprisek9-mz.SPA.155-1.SY10.bin slavebootdisk:
----------

3) Remove the boot variable string pointing to the old IOS
----------
no boot system bootdisk:s6t64-adventerprisek9-mz.SPA.155-1.SY7.bin
no boot system bootdisk:s6t64-adventerprisek9-mz.SPA.155-1.SY5.bin
----------

4) Add the new boot variable string pointing to the new IOS
----------
boot system bootdisk:s6t64-adventerprisek9-mz.SPA.155-1.SY10.bin
----------

5) Insert the boot variable string pointing to the old IOS

----------
boot system bootdisk:s6t64-adventerprisek9-mz.SPA.155-1.SY7.bin
----------

6) Make sure the config-registry is 0x2102

------
config-register 0x2102
------

Save the config

show bootvar (to confirm the correct variable)
redundancy reload shelf

Reboot

[Reza Sharifi]

The steps look correct, but if you have 2 sups in each switch, you want to load the new IOS in all 4 sups first.

copy bootdisk:s6t64-adventerprisek9-mz.SPA.155-1.SY10.bin sw1-slot3-bootdisk:

copy bootdisk:s6t64-adventerprisek9-mz.SPA.155-1.SY10.bin sw1-slot4-bootdisk:

the same for sw-2

HTH

[dqalib23]

That is what I was missing thanks for that Reza, will upgrade this weekend will update many thanks 

[Reza Sharifi]

Also, for step 6, you don't necessarily need to type the command. As long as "sh ver" or "sh redun" shows the correct config-register (0x2102), you are good to go. It is also very important to save your config at the end and before you reload, which is step-7

And one more thing, once you load the IOS in the first sup, you can always copy from the first sup to the second sup (from slot-3 to slot-4). I have done this type of upgrade with one sup in each chassis. So, hope all goes well with 4. 

Good Luck!

6) Make sure the config-registry is 0x2102

------
config-register 0x2102

[Leo Laohoo]

I agree with @Reza Sharifi, steps look good. 

Make sure to have console access to the switch.  In case the FPGA required message appears, the only way to perform the FPGA upgrade will be console.

[dqalib23]

HI Community 

For switch one I don't the see SW1-slot3-bootdisk:  is that normal do I only Upload the images 

bootdisk:
slavebootdisk:
sw1-slot4-bootdisk:
sw2-slot3-bootdisk:
sw1-slot4-bootdisk:

[dqalib23]

HI

Change went successful , downtime of 12minutes , thanks to all of you 

[Leo Laohoo]

Good to hear everything went like flawlessly.

Did you have to do a manual FPGA upgrade?

[marzi]

Hi dqalib23

If I'm not wrong, it is correct that you didn't see SW1-slot3-bootdisk: because it was the active supervisor (bootdisk):

I had the opportunity to compare different Cisco 6807-XL-6T (wether 2 either 4 supervisor), and I noted that the bootdisk hasn't an alias like the Hot-standby supervisor  or other two supervisor (in case of quad-supervisor).

regards 

Fabrizio