cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
6933
Views
5
Helpful
5
Replies

IOS upgrade 6500 quad sup vss

Hello,

we are upgrading IOS on WS-C6509-E in vss with redundant sup in each switch this weekend. I have never done this before on this type of environment. Also see attachment for issu, redundancy and bootvar details.

It will be a great help if someone can take sometime and provide steps with actual module numbers and bootvar settings to accomplish this task successfully.

I have checked below URL: It is understandable, but since this is my first time upgrading a quad sup vss switch, I am being cautious as this is the Core of our clients network.

http://www.cisco.com/c/en/us/td/docs/switches/lan/catalyst6500/ios/15-1SY/config_guide/sup2T/15_1_sy_swcg_2T/fast_software_upgrade.html#58890

sh mod switch all
 Switch Number:     1   Role:   Virtual Switch Active
----------------------  -----------------------------
Mod Ports Card Type                              Model              Serial No.
--- ----- -------------------------------------- ------------------ -----------
  1   20  DCEF2T 4 port 40GE / 16 port 10GE      WS-X6904-40G       SAL17299YP5
  3   20  DCEF2T 4 port 40GE / 16 port 10GE      WS-X6904-40G       SAL17299YRV
  5    5  Supervisor Engine 2T 10GE w/ CTS (Acti VS-SUP2T-10G       SAL1731APXZ
  6    5  Supervisor Engine 2T 10GE w/ CTS (CSSO VS-SUP2T-10G       SAL1731AQ27
  8   24  CEF720 24 port 1000mb SFP              WS-X6824-SFP       SAL1730A3K2

Mod  Sub-Module                  Model              Serial       Hw     Status

---- --------------------------- ------------------ ----------- ------- -------
  1  Distributed Forwarding Card WS-F6K-DFC4-E      SAL1732B4AA  1.2    Ok
  3  Distributed Forwarding Card WS-F6K-DFC4-E      SAL1731AWSK  1.2    Ok
  5  Policy Feature Card 4       VS-F6K-PFC4        SAL1731AN4J  2.1    Ok
  5  CPU Daughterboard           VS-F6K-MSFC5       SAL1731ANQU  2.0    Ok
  6  Policy Feature Card 4       VS-F6K-PFC4        SAL1731ANBM  2.1    Ok
  6  CPU Daughterboard           VS-F6K-MSFC5       SAL1731ANQ3  2.0    Ok
  8  Distributed Forwarding Card WS-F6K-DFC4-A      SAL1731ARQ4  1.0    Ok

 Switch Number:     2   Role:  Virtual Switch Standby

----------------------  -----------------------------
Mod Ports Card Type                              Model              Serial No.
--- ----- -------------------------------------- ------------------ -----------
  1   20  DCEF2T 4 port 40GE / 16 port 10GE      WS-X6904-40G       SAL17299YMX
  3   20  DCEF2T 4 port 40GE / 16 port 10GE      WS-X6904-40G       SAL17299YQQ
  5    5  Supervisor Engine 2T 10GE w/ CTS (Hot) VS-SUP2T-10G       SAL1731APXD
  6    5  Supervisor Engine 2T 10GE w/ CTS (CSSO VS-SUP2T-10G       SAL1731APZY
  8   24  CEF720 24 port 1000mb SFP              WS-X6824-SFP       SAL1730AFG9

Mod  Sub-Module                  Model              Serial       Hw     Status

---- --------------------------- ------------------ ----------- ------- -------
  1  Distributed Forwarding Card WS-F6K-DFC4-E      SAL1731AWQH  1.2    Ok
  3  Distributed Forwarding Card WS-F6K-DFC4-E      SAL1731AWQE  1.2    Ok
  5  Policy Feature Card 4       VS-F6K-PFC4        SAL1731ANAF  2.1    Ok
  5  CPU Daughterboard           VS-F6K-MSFC5       SAL1731ANU8  2.0    Ok
  6  Policy Feature Card 4       VS-F6K-PFC4        SAL1731ANBK  2.1    Ok
  6  CPU Daughterboard           VS-F6K-MSFC5       SAL1730AGKL  2.0    Ok
  8  Distributed Forwarding Card WS-F6K-DFC4-A      SAL1731ANXJ  1.0    Ok

Many thanks in advance.

Raghav

1 Accepted Solution

Accepted Solutions

HI Leo,

Thank you. I followed the below process a little detailed. Might help someone.

 

Copy image in all sup’s and confirm image is present on Standby switch

#remote command switch-id 2 module 5 dir

Directory of bootdisk:/

    2  -rw-    85875056  Aug 14 2013 20:11:20 -04:00  s2t54-ipservicesk9-mz.SPA.150-1.SY4.bin

    3  -rw-    93441464  Aug 27 2013 22:22:36 -04:00  s2t54-ipservicesk9-mz.SPA.151-1.SY1.bin

   10  -rw-   113829304  Jan 31 2015 16:10:34 -05:00  s2t54-ipservicesk9-mz.SPA.151-2.SY4a.bin

#remote command switch-id 2 module 6 dir

Directory of bootdisk:/

    2  -rw-    85875056  Aug 14 2013 20:11:20 -04:00  s2t54-ipservicesk9-mz.SPA.150-1.SY4.bin

    3  -rw-    93441464  Aug 27 2013 22:22:36 -04:00  s2t54-ipservicesk9-mz.SPA.151-1.SY1.bin

   10  -rw-   113829304  Jan 31 2015 16:10:34 -05:00  s2t54-ipservicesk9-mz.SPA.151-2.SY4a.bin

Verify image integrity

verify /md5 sw1-slot5-bootdisk:s2t54-ipservicesk9-mz.SPA.151-2.SY4a.bin

verify /md5 sw1-slot6-bootdisk:s2t54-ipservicesk9-mz.SPA.151-2.SY4a.bin

verify /md5 sw2-slot5-bootdisk:s2t54-ipservicesk9-mz.SPA.151-2.SY4a.bin

verify /md5 sw2-slot6-bootdisk:s2t54-ipservicesk9-mz.SPA.151-2.SY4a.bin

Set boot var

conf t

no boot system flash

boot system flash bootdisk:s2t54-ipservicesk9-mz.SPA.151-2.SY4a.bin

boot system flash bootdisk:s2t54-ipservicesk9-mz.SPA.151-1.SY1.bin   //Secondary image

end

 

Check bootvar on Standby switch

#remote command switch-id 2 module 5 sh bootvar

#remote command switch-id 2 module 6 sh bootvar

# redundancy reload peer

Once peer came into rpr mode, reloaded active switch

# redundancy reload shelf 

View solution in original post

5 Replies 5

Leo Laohoo
Hall of Fame
Hall of Fame

Before you begin, you need to check the following:  

1.  config-registry value; and 

2.  Do an MD5 hash check of the file you're going to use.  The MD5 should have the same value as found in the Cisco website.

 

If you want how we've done ours:

 

1.  Copy the IOS from the TFTP to the active blade supervisor card:  copy tftp:///IOS.bin sup-bootflash:

2.  Copy the IOS from the TFTP to the secondary blade supervisor card:  copy tftp:///IOS.bin slavesup-bootflash:

5.  Go to enable mode and change the bootstring/boot variable.

NOTE:  In this step, what we've done is specify that the chassis boot the NEW IOS and also specify that the chassis boot the old or existing IOS in case the first one fails.

 

conf t

NO boot system flash sup-bootdisk:OLD_IOS.bin

boot system flash sup-bootdisk:NEW_IOS.bin

boot system flash sup-bootdisk:OLD_IOS.bin

end

copy run start

reboot

HI Leo,

Thank you. I followed the below process a little detailed. Might help someone.

 

Copy image in all sup’s and confirm image is present on Standby switch

#remote command switch-id 2 module 5 dir

Directory of bootdisk:/

    2  -rw-    85875056  Aug 14 2013 20:11:20 -04:00  s2t54-ipservicesk9-mz.SPA.150-1.SY4.bin

    3  -rw-    93441464  Aug 27 2013 22:22:36 -04:00  s2t54-ipservicesk9-mz.SPA.151-1.SY1.bin

   10  -rw-   113829304  Jan 31 2015 16:10:34 -05:00  s2t54-ipservicesk9-mz.SPA.151-2.SY4a.bin

#remote command switch-id 2 module 6 dir

Directory of bootdisk:/

    2  -rw-    85875056  Aug 14 2013 20:11:20 -04:00  s2t54-ipservicesk9-mz.SPA.150-1.SY4.bin

    3  -rw-    93441464  Aug 27 2013 22:22:36 -04:00  s2t54-ipservicesk9-mz.SPA.151-1.SY1.bin

   10  -rw-   113829304  Jan 31 2015 16:10:34 -05:00  s2t54-ipservicesk9-mz.SPA.151-2.SY4a.bin

Verify image integrity

verify /md5 sw1-slot5-bootdisk:s2t54-ipservicesk9-mz.SPA.151-2.SY4a.bin

verify /md5 sw1-slot6-bootdisk:s2t54-ipservicesk9-mz.SPA.151-2.SY4a.bin

verify /md5 sw2-slot5-bootdisk:s2t54-ipservicesk9-mz.SPA.151-2.SY4a.bin

verify /md5 sw2-slot6-bootdisk:s2t54-ipservicesk9-mz.SPA.151-2.SY4a.bin

Set boot var

conf t

no boot system flash

boot system flash bootdisk:s2t54-ipservicesk9-mz.SPA.151-2.SY4a.bin

boot system flash bootdisk:s2t54-ipservicesk9-mz.SPA.151-1.SY1.bin   //Secondary image

end

 

Check bootvar on Standby switch

#remote command switch-id 2 module 5 sh bootvar

#remote command switch-id 2 module 6 sh bootvar

# redundancy reload peer

Once peer came into rpr mode, reloaded active switch

# redundancy reload shelf 

Hi Leo,

 

Can you please detail further the steps in upgrading the IOS code of a quad SUP-2T VSS on a WS-C6509 Chassis. I really appreciate your help if you can do that for the rest of community members.

 

Thank you in advance.

Chie

This may be a little late, but I've recently successfully upgraded a pair of C6513-E VSS switches with quad 2T-SUPs using the steps below. Hope this information can help someone out in the future!

 

Step1: Copy the image over to the core switch via TFTP

copy tftp: bootdisk:

Address or name of remote host []? <IP of TFTP server>

Source filename []? s2t54-advipservicesk9-mz.SPA.151-2.SY12.bin

Destination filename [s2t54-advipservicesk9-mz.SPA.151-2.SY12.bin]? 

 

Step2: Check the image in bootdisk:

dir bootdisk:

 

Step3: Verify the md5 checksum for the image in bootdisk:

verify /md5 bootdisk:s2t54-advipservicesk9-mz.SPA.151-2.SY12.bin

 

Step4: The 2T-SUPs are in slots 7 and 8 on both switches. Check to make sure that slot 7 of switch 1 already has the image (by default, copying the image to bootdisk will automatically generate the image in sw1-slot7-bootdisk)

dir sw1-slot7-bootdisk:

 

Step5: Copy the IOS image from the active SUP to the other 3 SUPs.

copy sw1-slot7-bootdisk:s2t54-advipservicesk9-mz.SPA.151-2.SY12.bin sw1-slot8-bootdisk:

copy sw1-slot7-bootdisk:s2t54-advipservicesk9-mz.SPA.151-2.SY12.bin sw2-slot7-bootdisk:

copy sw1-slot7-bootdisk:s2t54-advipservicesk9-mz.SPA.151-2.SY12.bin sw2-slot8-bootdisk:

 

Step6: Verify that the image is present on the both the active and standby switches.

dir sw1-slot7-bootdisk:

dir sw1-slot8-bootdisk:

dir sw2-slot7-bootdisk:

dir sw2-slot8-bootdisk:

 

Step7: Verify that the image is good on all the SUPs.

verify /md5 sw1-slot7-bootdisk:s2t54-advipservicesk9-mz.SPA.151-2.SY12.bin

verify /md5 sw1-slot8-bootdisk:s2t54-advipservicesk9-mz.SPA.151-2.SY12.bin

verify /md5 sw2-slot7-bootdisk:s2t54-advipservicesk9-mz.SPA.151-2.SY12.bin

verify /md5 sw2-slot8-bootdisk:s2t54-advipservicesk9-mz.SPA.151-2.SY12.bin

 

Step8: Set the boot variable. Keep the old image as backup in case the new image fails.

conf t

no boot system flash

boot system flash bootdisk:/s2t54-advipservicesk9-mz.SPA.151-2.SY12.bin

boot system flash bootdisk:/s2t54-advipservicesk9-mz.SPA.151-2.SY7.bin

end

wr

 

Step9: Check the boot variable for all SUPs on both the active and standby switches.

remote command switch-id 1 module 7 show bootvar

remote command switch-id 1 module 8 show bootvar

remote command switch-id 2 module 7 show bootvar

remote command switch-id 2 module 8 show bootvar

 

Step 10: Check to make sure the configuration register is set to 0x2102.

show version | i x2102

 

Step11: Reload the standby switch.

redundancy reload peer

 

Step12: Once the peer comes into RPR mode (show redundancy), reload the active switch.

redundancy reload shelf

 

Dears,

 

What about the required down time? As far as I know, the down time will be required during the switch over between the two chassis . Is there is a way to minimize the downtime to the minimum? Is there a way to do the upgrade without downtime using normal upgrade FSU -NOT eFSU-?  

 

Best Regards,

Mohammad 

Getting Started

Find answers to your questions by entering keywords or phrases in the Search bar above. New here? Use these resources to familiarize yourself with the community:

Innovations in Cisco Full Stack Observability - A new webinar from Cisco