Upgragding Cisco 6500 IOS

Dragon0x40 used Ask the Experts™
I have a Cisco 6509 switch with redundant 720/MSFC3 supervisors that needs the IOS upgraded to a newer version. I have new ios bin file: s72033-adventerprisek9_wan-mz.122-33.SXH5.bin

Would it be prudent to remove one of the supervisors and then upgrade the IOS and load the config on one supervisor?

My thinking is that way if the new IOS is not compatible with the supervisor or firmware, etc.. then I could just shut the switch down, swap supervisors, boot the switch and then I am back to where I was before.

The main question that I have is how the redundant supervisor works with online insertion?

Does the IOS and config both get sychronized automatically to a inserted supervisor or is that a manaul process? How do I verify that the sups have synced?

Do the files get overwritten or added to the inserted supervisor?

Is there a reason to upgrade both supervisors at the same time?

#sh ver
Cisco Internetwork Operating System Software
IOS (tm) s72033_rp Software (s72033_rp-ENTSERVICESK9_WAN-M), Version 12.2(18)SXE3, RELEASE SOFTWARE (fc1)
Technical Support: http://www.cisco.com/techsupport
Copyright (c) 1986-2005 by cisco Systems, Inc.
Compiled Tue 16-Aug-05 18:56 by kellmill
Image text-base: 0x40021040, data-base: 0x42B08000

ROM: System Bootstrap, Version 12.2(17r)S2, RELEASE SOFTWARE (fc1)
BOOTLDR: s72033_rp Software (s72033_rp-ENTSERVICESK9_WAN-M), Version 12.2(18)SXE3, RELEASE SOFTWARE (fc1)

 uptime is 1 year, 2 weeks, 3 days, 20 hours, 42 minutes
Time since switched to active is 1 year, 2 weeks, 3 days, 20 hours, 46 minutes
System returned to ROM by unknown reload cause - suspect boot_data[BOOT_COUNT] 0x0, BOOT_COUNT 0, BOOTDATA 19 (SP by power-on)
System restarted at 14:17:49 pst Wed Sep 30 2009
System image file is "disk0:s72033-entservicesk9_wan-mz.122-18.SXE3.bin"

This product contains cryptographic features and is subject to United
States and local country laws governing import, export, transfer and
use. Delivery of Cisco cryptographic products does not imply
third-party authority to import, export, distribute or use encryption.
Importers, exporters, distributors and users are responsible for
compliance with U.S. and local country laws. By using this product you
agree to comply with applicable laws and regulations. If you are unable
to comply with U.S. and local laws, return this product immediately.

A summary of U.S. laws governing Cisco cryptographic products may be found at:

If you require further assistance please contact us by sending email to

cisco WS-C6509 (R7000) processor (revision 3.2) with 458720K/65536K bytes of memory.
Processor board ID SAL09370F49
SR71000 CPU at 600Mhz, Implementation 0x504, Rev 1.2, 512KB L2 Cache
Last reset from power-on
SuperLAT software (copyright 1990 by Meridian Technology Corp).
X.25 software, Version 3.0.0.
Bridging software.
TN3270 Emulation software.
3 Virtual Ethernet/IEEE 802.3 interfaces
148 Gigabit Ethernet/IEEE 802.3 interfaces
16 Ten Gigabit Ethernet/IEEE 802.3 interfaces
1917K bytes of non-volatile configuration memory.
8192K bytes of packet buffer memory.

65536K bytes of Flash internal SIMM (Sector size 512K).
Configuration register is 0x2102

#sh mod
Mod Ports Card Type                              Model              Serial No.
--- ----- -------------------------------------- ------------------ -----------
  1   48  CEF720 48 port 1000mb SFP              WS-X6748-SFP       Serial Number
  2    4  CEF720 4 port 10-Gigabit Ethernet      WS-X6704-10GE      Serial Number
  4    4  CEF720 4 port 10-Gigabit Ethernet      WS-X6704-10GE      Serial Number
  5    2  Supervisor Engine 720 (Active)         WS-SUP720-BASE     Serial Number
  6    2  Supervisor Engine 720 (Hot)            WS-SUP720-BASE     Serial Number
  7    4  CEF720 4 port 10-Gigabit Ethernet      WS-X6704-10GE      Serial Number
  8    4  CEF720 4 port 10-Gigabit Ethernet      WS-X6704-10GE      Serial Number
  9   48  48 port 10/100/1000mb EtherModule      WS-X6148-GE-TX     Serial Number

Mod MAC addresses                       Hw    Fw           Sw           Status
--- ---------------------------------- ------ ------------ ------------ -------
  1  0021.d88b.d10c to 0021.d88b.d13b   1.12  12.2(14r)S5  12.2(18)SXE3 Ok
  2  0021.553a.20a4 to 0021.553a.20a7   2.7   12.2(14r)S5  12.2(18)SXE3 Ok
  4  0014.f23e.2d1c to 0014.f23e.2d1f   2.2   12.2(14r)S5  12.2(18)SXE3 Ok
  5  0012.dae4.487c to 0012.dae4.487f   3.3   8.1(3)       12.2(18)SXE3 Ok
  6  0012.dae4.7790 to 0012.dae4.7793   3.3   8.1(3)       12.2(18)SXE3 Ok
  7  0014.a9f7.7cac to 0014.a9f7.7caf   2.2   12.2(14r)S5  12.2(18)SXE3 Ok
  8  0019.56f3.0c78 to 0019.56f3.0c7b   2.5   12.2(14r)S5  12.2(18)SXE3 Ok
  9  0009.125a.d5c8 to 0009.125a.d5f7   1.1   7.2(1)       8.5(0.46)ROC Ok

Mod Sub-Module                  Model              Serial        Hw     Status
--- --------------------------- ------------------ ------------ ------- -------
  1 Centralized Forwarding Card WS-F6700-CFC       Serial Number   4.1    Ok
  2 Centralized Forwarding Card WS-F6700-CFC       Serial Number   4.0    Ok
  4 Centralized Forwarding Card WS-F6700-CFC       Serial Number   2.0    Ok
  5 Policy Feature Card 3       WS-F6K-PFC3A       Serial Number   2.5    Ok
  5 MSFC3 Daughterboard         WS-SUP720          Serial Number   2.5    Ok
  6 Policy Feature Card 3       WS-F6K-PFC3A       Serial Number   2.5    Ok
  6 MSFC3 Daughterboard         WS-SUP720          Serial Number   2.5    Ok
  7 Centralized Forwarding Card WS-F6700-CFC       Serial Number   2.0    Ok
  8 Centralized Forwarding Card WS-F6700-CFC       Serial Number   3.0    Ok

Mod Online Diag Status
--- -------------------
  1 Pass
  2 Pass
  4 Pass
  5 Pass
  6 Pass
  7 Pass
  8 Pass
  9 Pass

#sh mod 5
Mod Ports Card Type                              Model              Serial No.
--- ----- -------------------------------------- ------------------ -----------
  5    2  Supervisor Engine 720 (Active)         WS-SUP720-BASE     Serial Number

Mod MAC addresses                       Hw    Fw           Sw           Status
--- ---------------------------------- ------ ------------ ------------ -------
  5  0012.dae4.487c to 0012.dae4.487f   3.3   8.1(3)       12.2(18)SXE3 Ok

Mod Sub-Module                  Model              Serial        Hw     Status
--- --------------------------- ------------------ ------------ ------- -------
  5 Policy Feature Card 3       WS-F6K-PFC3A       Serial Number   2.5    Ok
  5 MSFC3 Daughterboard         WS-SUP720          Serial Number   2.5    Ok

Mod Online Diag Status
--- -------------------
  5 Pass
Watch Question

Do more with

Expert Office
EXPERT OFFICE® is a registered trademark of EXPERTS EXCHANGE®
Why not just have the new IOS boot first and keep the old IOS as a backup on the primary supervisor in case the new IOS fails to boot it will search for another IOS to load from. Or just have the IOS point to a TFTP server to pull from.


thanks Paktusjet,

If there is room on the flash then that would make sense.

Then I would not have to reload the configuration?

Do you have a link to a step by step procedure for doing the upgrade that way?
It's the same way just TFTP the IOS to the switch then set the boot system to the new image. After you do that keep the old IOS on the Flash. With the 6509 you should have well more then enough space on the flash to store it.
Should you be charging more for IT Services?

Do you wonder if your IT business is truly profitable or if you should raise your prices? Learn how to calculate your overhead burden using our free interactive tool and use it to determine the right price for your IT services. Start calculating Now!


I will not need to reload the configuration as it should work with the new IOS?
yes, your only upgrading the IOS. The configurations are stored in a config.text file that is stored within your flash.


My current boot configuration is this:
#sh run | inc boot
boot system flash disk0:

So I would change to something like this?
(config)#boot system flash disk:0/s72033-entservicesk9_wan-mz.122-18.SXE3.bin

I don't have a copy tftp option? Do I have to use ftp?

#copy ?
  /erase               Erase destination file system.
  /noverify            Don't verify image signature before reload.
  /verify              Verify image signature before reload.
  bootflash:           Copy from bootflash: file system
  cns:                 Copy from cns: file system
  const_nvram:         Copy from const_nvram: file system
  dfc#1-bootflash:     Copy from dfc#1-bootflash: file system
  dfc#2-bootflash:     Copy from dfc#2-bootflash: file system
  dfc#4-bootflash:     Copy from dfc#4-bootflash: file system
  dfc#7-bootflash:     Copy from dfc#7-bootflash: file system
  dfc#8-bootflash:     Copy from dfc#8-bootflash: file system
  disk0:               Copy from disk0: file system
  disk1:               Copy from disk1: file system
  flexwan-fpd:         Copy from flexwan-fpd: file system
  ftp:                 Copy from ftp: file system
  null:                Copy from null: file system
  nvram:               Copy from nvram: file system
  rcp:                 Copy from rcp: file system
  running-config       Copy from current system configuration
  scp:                 Copy from scp: file system
  slavebootflash:      Copy from slavebootflash: file system
  slaveconst_nvram:    Copy from slaveconst_nvram: file system
  slavedisk0:          Copy from slavedisk0: file system
  slavedisk1:          Copy from slavedisk1: file system
  slavenvram:          Copy from slavenvram: file system
  slavercsf:           Copy from slavercsf: file system
  slavesup-bootflash:  Copy from slavesup-bootflash: file system
  slavesystem:         Copy from slavesystem: file system
  startup-config       Copy from startup configuration
  sup-bootflash:       Copy from sup-bootflash: file system
  sup-microcode:       Copy from sup-microcode: file system
  system:              Copy from system: file system
  tar:                 Copy from tar: file system


never mind I found the tftp option after the tar:


(config)#boot system flash disk:0/s72033-entservicesk9_wan-mz.122-18.SXE3.bin

If I have two ios images in disk0: do I need to put the prepend option on the end of the above boot command?


copy tftp: disk0:
**ip address x.x.x.x
**source file name: s72033-adventerprisek9_wan-mz.122-33.SXH7.bin
**destination file name: s72033-adventerprisek9_wan-mz.122-33.SXH7.bin

dir disk0:

boot system flash disk:0/s72033-adventerprisek9_wan-mz.122-33.SXH7.bin


show version

show redundancy

show redundancy states

redundancy force-switchover (test the hot supervisor)

redundancy force-switchover (shift control back to primary supervisor)

Does this make sense?


Had to copy IOS to slavedisk0: also.

Do more with

Expert Office
Submit tech questions to Ask the Experts™ at any time to receive solutions, advice, and new ideas from leading industry professionals.

Start Today