Cisco 7606 with redundant Sup720 IOS upgrade

Unanswered Question
Jun 4th, 2008

I will be performing "Performing a Fast Software Upgrade "

Following link explains that

http://www.cisco.com/en/US/docs/routers/7600/ios/12.2SR/configuration/guide/redund.html#wp1089399



My question is do i have to upload new IOS on both sup-bootflash: and slavesup-bootflash or only to one ?

  • 1
  • 2
  • 3
  • 4
  • 5
Overall Rating: 3.5 (2 ratings)
Loading.
singhsaju Wed, 06/04/2008 - 12:18

Oleg,

Thanks for the reply.


But in step 5 when we do redundancy switchover , it is written in document that

"The redundant supervisor engine becomes the new active supervisor engine running the new Cisco IOS image. The modules are reloaded and the module software is downloaded from the new active supervisor engine.


The old active supervisor engine reboots with the new image and becomes the redundant supervisor engine

"


which means it copies IOS from new active SUP to old active . I have not tried this so i want to confirm . Have you done this before ?



Ryan Carretta Wed, 06/04/2008 - 23:43

When it says the module software it means the line cards. The line cards need to download their software from the active supervisor from the EOBC when they come up in the chassis.


You'll want to ensure that the image exists on both supervisor modules.

Many times. You need to copy IOS image to both Sups.


Look at: http://www.cisco.com/en/US/docs/switches/lan/catalyst6500/ios/12.2SXF/native/configuration/guide/redund.html#wp1089399


The complete procedure is as follows:


show file systems


copy tftp sup-bootflash:

copy tftp slavesup-bootflash:


Or use disk0: and slavedisk0:


show boot

no boot system flash


You MUST clear old boot configuration.


boot system flash sup-bootdisk:


The device name may be different on different Sups (Sup2, Sup720, etc.). DON'T use sup-bootflash: on Sup720 in THIS command. Use sup-bootdisk: instead. (sup-bootflash: is an alias for sup-bootdisk: for IOS, but ROM monitor MAY not be aware of that fact!). Use "show file systems" if unsure.


wr


You MUST save config. Otherwise boot settings are not propagated to the rommon.


show boot


Verify that BOTH rommons are updated with boot settings (on the Active and Standby Sups).


hw-module module reset


Wait long enough. Use


show module

show redundancy states


to verify.


Prepare for some downtime, because at this point RPR is used for redundancy, not SSO.


redundancy force-switchover


This command reloads the active Sup. When it boots SSO mode is activated automatically.


HTH


Actions

This Discussion