06-09-2017 06:51 AM - edited 03-08-2019 10:55 AM
I have two 6513-E switches with 4 Supervisor 2T modules between them. They are set up in a quad-sup VSS-SSO arrangement.
I want to upgrade this system to a newer IOS version. I have copied the new IOS file to the bootdisk: and slavebootdisk: but I am unsure as to where to copy the file to on supervisor modules 3 & 4
so my questions are these
where should I copy the IOS to for supervisors 3 and 4?
Are there any caveats when doing an upgrade procedure in a quad-sup arrangement?
06-09-2017 03:35 PM
Can you please post the complete output to the command "dir ?".
06-21-2017 10:04 AM
CA-DIST6513-01#dir
Directory of bootdisk:/
2 -rw- 33554432 May 31 2013 06:13:26 +00:00 sea_console.dat
3 -rw- 98145752 May 31 2013 06:27:08 +00:00 s2t54-advipservicesk9-mz.SPA.151-1.SY1.bin
4 drw- 0 Jun 1 2013 06:52:22 +00:00 call-home
5 -rw- 91133856 Jun 24 2013 16:14:50 +00:00 s2t54-adventerprisek9-mz.SPA.150-1.SY4.bin
6 -rw- 21134 Jun 27 2013 20:37:48 +00:00 startup-config.converted_vs-20130627-203741
9 -rw- 162481304 Feb 21 2017 19:58:34 +00:00 s2t54-advipservicesk9-mz.SPA.154-1.SY1.bin
7 -rw- 33554432 May 31 2013 07:05:06 +00:00 sea_log.dat
8 -rw- 28856320 May 31 2013 07:49:38 +00:00 c6500-fpd-pkg.151-1.SY1.pkg
1024557056 bytes total (576716800 bytes free)
CA-DIST6513-01#dir sw2-slot7-bootdisk:
Directory of slavebootdisk:/
2 -rw- 33554432 May 30 2013 19:52:40 +00:00 sea_console.dat
3 -rw- 98145752 May 30 2013 20:06:24 +00:00 s2t54-advipservicesk9-mz.SPA.151-1.SY1.bin
4 drw- 0 May 31 2013 20:31:14 +00:00 call-home
5 -rw- 91133856 Jun 24 2013 16:41:54 +00:00 s2t54-adventerprisek9-mz.SPA.150-1.SY4.bin
6 -rw- 21065 Jun 27 2013 20:39:18 +00:00 startup-config.converted_vs-20130627-203854
9 -rw- 162481304 Feb 21 2017 20:27:32 +00:00 s2t54-advipservicesk9-mz.SPA.154-1.SY1.bin
7 -rw- 33554432 May 30 2013 20:43:36 +00:00 sea_log.dat
8 -rw- 28856320 May 30 2013 21:27:08 +00:00 c6500-fpd-pkg.151-1.SY1.pkg
1024557056 bytes total (576716800 bytes free)
CA-DIST6513-01#dir sw1-slot8-bootdisk:
Directory of sw1-slot8-bootdisk:/
2 -rw- 33554432 May 31 2013 04:22:18 +00:00 sea_log.dat
3 -rw- 33554432 May 31 2013 04:23:02 +00:00 sea_console.dat
4 -rw- 98145752 May 31 2013 04:28:16 +00:00 s2t54-advipservicesk9-mz.SPA.151-1.SY1.bin
5 drw- 0 Jun 1 2013 07:01:50 +00:00 call-home
6 -rw- 91133856 Jun 24 2013 16:11:32 +00:00 s2t54-adventerprisek9-mz.SPA.150-1.SY4.bin
7 -rw- 441622 Aug 16 2014 20:48:32 +00:00 crashinfo_20140816-204833-UTC
8 -rw- 162481304 Feb 21 2017 19:53:32 +00:00 s2t54-advipservicesk9-mz.SPA.154-1.SY1.bin
1024557056 bytes total (605175808 bytes free)
CA-DIST6513-01#dir sw2-slot8-bootdisk:
Directory of sw2-slot8-bootdisk:/
2 -rw- 33554432 May 30 2013 18:31:12 +00:00 sea_console.dat
3 -rw- 33554432 May 30 2013 18:31:58 +00:00 sea_log.dat
4 -rw- 98145752 May 30 2013 18:37:10 +00:00 s2t54-advipservicesk9-mz.SPA.151-1.SY1.bin
5 drw- 0 May 31 2013 20:40:42 +00:00 call-home
6 -rw- 91133856 Jun 24 2013 16:39:52 +00:00 s2t54-adventerprisek9-mz.SPA.150-1.SY4.bin
7 -rw- 162481304 Feb 21 2017 19:46:36 +00:00 s2t54-advipservicesk9-mz.SPA.154-1.SY1.bin
06-21-2017 01:14 PM
From the output you posted, it seems that you have the IOS loaded in all 4 sups (2 in chassis 1 blade 7 and 8 and 2 in chassis 2 blade 7 and 8).
HTH
06-21-2017 03:21 PM
If the system is meant to boot "s2t54-advipservicesk9-mz.SPA.154-1.SY1.bin" then issue the command on the active supervisor card (only) "boot system flash bootflash:s2t54-advipservicesk9-mz.SPA.154-1.SY1.bin" and save the config.
This will instruct all the supervisor cards to boot the file.
Don't forget to check the config-registry value to make sure it is set to 0x2102.
Discover and save your favorite ideas. Come back to expert answers, step-by-step guides, recent topics, and more.
New here? Get started with these tips. How to use Community New member guide