Upgrade Cisco6807-SUP-2T and Cisco6807-SUP-6T

[marzi]

Hi all

I have to do an IOS upgrade to these platform

model	old release	new release (suggested)
C6807-XL-S6T-BUN	15.5(1)SY1	15.5.1-SY10
C6807-XL-S6T-BUN	15.4(1)SY1	15.5.1-SY10
C6807-XL-S6T-BUN	15.5(1)SY1	15.5.1-SY10
C6807-XL-S6T-BUN	15.4(1)SY2	15.5.1-SY10
C6807-XL-S6T-BUN	15.3(1)SY	15.5.1-SY10
C6807-XL-S6T-BUN	15.5(1)SY8	15.5.1-SY10
C6807-XL-S2T-BUN	15.2(1)SY1a	15.5.1-SY10

I haven't find an upgrade procedure in the release note suggested, please is there anyone that could tell me where find how to do ?

Thank's in advance

FM

[balaji.bandi]

You read the release notes :

https://www.cisco.com/c/en/us/td/docs/switches/lan/catalyst6500/ios/15-5SY/release_notes/release_notes_15_5_SY.html

is this VSS or stand alone switch :

below upgrade steps should work :

https://www.cisco.com/c/en/us/td/docs/switches/lan/catalyst6500/ios/15-5SY/config_guide/sup2T/15_5_sy_swcg_2T/fast_software_upgrade.html

[Leo Laohoo]

Please read the Release Notes very, very carefully because the destination is 15.5(1)SY train.  Special care to "read between the lines" because the BU has deliberately hidden the information about manual FPGA.  The vital information about "what are the affected line cards" have been removed and the hidden command to perform the FPGA upgrade is not incorporated into the Release Notes documentation and instead, a hyperlink to some other document. 

If the FPGA upgrade to the affected line card(s) are not performed, the affected line card(s) will stay down.  

It is of utmost importance that someone read and, most importantly, understand Performing FPGA Upgrade.  Make sure to have console access to the Sup2T and Sup6T so can be possible to perform the manual FPGA upgrade.

Word of Warning:  

Do not, under any circumstance, make any attempts to upgrade the IOS using ISSU, FSU/eFSU/xFSU.  

[marzi]

Hi Leo

I've read the link about upgrading FPGA, and I could be in the condition to do an upgrade,
forgive my trivial question but about the following command:

For VSS case:
Device# upgrade winters-flash switch switch-number slot slot-number bundled-image gold

slot nomber is referred to the line card module ?

for example:

vss1#sh inventory

NAME: "Chassis 1 1", DESCR: "Chassis 1 C6800-32P10G DCEF2T 8 port 40GE / 32 port 10GE Rev. 1.2"
PID: C6800-32P10G , VID: V01, SN: SALXXXXXXXXX

NAME: "Chassis 2 1", DESCR: "Chassis 2 C6800-32P10G DCEF2T 8 port 40GE / 32 port 10GE Rev. 1.2"
PID: C6800-32P10G , VID: V01, SN: SALYYYYYYYYY

the command will be

vss1# upgrade winters-flash switch 1 slot 1 bundled-image gold

vss1# upgrade winters-flash switch 2 slot 1 bundled-image gold

Is it correct ?

Thanks
FM

[Leo Laohoo]

Yes, the syntax is correct.

[marzi]

Hi Leo

Following I describe all the step needed for the uppgrade which do not fall within ISSU, FSU/eFSU/xFSU cases (I suppose):

!1. Copy the new image into the active supervisor inside the

bootdisk

                                              

vss1#copy tftp:s6t64-adventerprisek9-mz.SPA.155-1.SY10.bin bootdisk:

!2. Copy the new image into the standby supervisor inside the

slavebootdisk

vss1 #copy bootdisk:s6t64-adventerprisek9-mz.SPA.155-1.SY10.bin slavebootdisk:

!3 verify 

verify/md5 Following I describe all the step needed for the uppgrade :

!4. Check that IOS is correctly copied inside both supervisor

vss1#dir bootdisk:

vss1#dir slavebootdisk:

!4. Setting the boot.

vss1 #config terminal

vss1 (config ) #boot system flash bootdisk:s6t64-adventerprisek9-mz.SPA.155-1.SY10.bin

!5. Save the configuration, automatically the conf. will be saved into standby supervisors.

vss1 #copy running-config startup-config

Destination filename [startup-config]?

Building configuration...

Compressed configuration from 14022 bytes to 5201 bytes[OK]

!6. Chek the boot system with the correct IOS                                                                

vss1#show bootvar

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

CONFIG_FILE variable =

BOOTLDR variable =

Configuration register is 0x2102


Standby BOOT variable = bootdisk:s6t64-adventerprisek9-mz.SPA.155-1.SY10.bin bootdisk,1;

Standby CONFIG_FILE variable =

Standby BOOTLDR variable =

Standby Configuration register is 0x2102

!7. Reload the entire chassis, this operation will reload the two supervisor too      

!Note: It is important to reload both the supervisor because the IOS must be the same version

vss1#redundancy reload shelf

Reload the entire shelf [confirm]

Preparing to reload this shelf

*Jul  4 06:18:55.308: %RF-5-RF_RELOAD: Shelf reload. Reason: Reload Shelf CLI

*Jul  4 06:18:57.020: %SYS-5-RELOAD: Reload requested by console. Reload Reason: Reload Shelf CLI.

!8. Verify VSS Switch Redundancy                                                

!   After that the two chassis coming up verify that the two supervisor have the same IOS version  

vss1#show switch virtual redundancy

Now, I've got two question more :

1) If something should goes wrong, pointing again to the old image could be a solution ?

   for example :  boot system flash bootdisk:/s2t54-adventerprisek9-mz.SPA.152-1.SY1a.bin

2) I think that further attention I must pay for an eventually upgrade of the rommon too, are you agree ?

Thanks for all support

FM

[Leo Laohoo · Accepted solution]

---

@marzi wrote:

!3 verify 

verify/md5 Following I describe all the step needed for the uppgrade :

---

verify /md5 bootdisk:s6t64-adventerprisek9-mz.SPA.155-1.SY10.bin 72065376fd1203415f7bdba8847650e3
verify /md5 slavebootdisk:s6t64-adventerprisek9-mz.SPA.155-1.SY10.bin 72065376fd1203415f7bdba8847650e3 

[Leo Laohoo · Accepted solution]

---

@marzi wrote:

!7. Reload the entire chassis, this operation will reload the two supervisor too      

!Note: It is important to reload both the supervisor because the IOS must be the same version

vss1#redundancy reload shelf

Reload the entire shelf [confirm]

Preparing to reload this shelf

*Jul  4 06:18:55.308: %RF-5-RF_RELOAD: Shelf reload. Reason: Reload Shelf CLI

*Jul  4 06:18:57.020: %SYS-5-RELOAD: Reload requested by console. Reload Reason: Reload Shelf CLI.

---

Save the config. 

Export the config to an external device. 

Reboot using the command

reload

.   Do not use the

redundancy

command to reboot both units.

[Leo Laohoo · Accepted solution]

---

@marzi wrote:

1) If something should goes wrong, pointing again to the old image could be a solution ?

---

Correct.  Fall back to the old IOS.  This should be in the boot variable statement.  

conf t
 boot system flash bootdisk:s6t64-adventerprisek9-mz.SPA.155-1.SY10.bin
 boot system flash bootdisk:s2t54-adventerprisek9-mz.SPA.152-1.SY1a.bin
 boot system flash bootdisk: 
end
wr

---

@marzi wrote:

2) I think that further attention I must pay for an eventually upgrade of the rommon too, are you agree ?

---

On a 6807 & 6880, I never upgrade the ROMMON.