Summary:
The purpose of this document is to assist someone who has received a replacement supervisor and they need to restore their 6500 switch to full SSO redundancy. (This procedure should also work for 7600 and 4500.)
Procedure:
You can add or replace a supervisor in an OIR (6500, 7600, 4500) chassis without causing an outage. Please keep in mind that any time one is moving or changing hardware a service interruption is possible. Therefore it is advised to make all changes during a change window in off-peak hours.
In order to get your supervisors in SSO they generally need to be running the same version of IOS. This is probably the most common reason that supervisors are not in SSO. (As seen via the "show redundancy" command. The standby supervisor should be in "Standby Hot" for SSO to be operational.)
That said, again as long as the new supervisor is not the active, you would simply:
(If a CF card exists in the current supervisor, or you have one onsite, please use Method 1. Otherwise please use Method 2. )
Method 1:
1) Remove the failing supervisor (which should not be the current active)
2) Insert the replacement supervisor into the chassis, but don’t fully seat it yet
3)*!* Remove the CF (compact flash) from the problem supervisor and insert it into the replacement
supervisor
4) Plug your laptop into the console port of the replacement supervisor and get your terminal program
working
5) Firmly insert the replacement supervisor, it should now power on.
6) When you see the supervisor starting to boot on your console screen please break into rommon by
doing CTRL+Break (at the same time)
7) When you’re at the rommon1> prompt please type: [Note:You will need to use your correct IOS .bin]
a. command: BOOT=disk0:s72033-advipservicesk9_wan-mz.122-33.SXI2a.bin
b. command: Confreg 0x2102
c. command: sync
d. command: reset
8) The supervisor should then reload and boot into 12.2(33)SXI2a. (Or whichever IOS you specify.)
9) If you log into the active supervisor, the standby should show as “STANDBY HOT”
10) If this is the end result you are done.
Caveat *!*:
If there isn't a compact flash in the old supervisor and you have a compact
flash available you can insert the CF into the current active supervisor and
then copy the IOS from the bootflash to the CF card, then continue this
process as normal.
a) Insert CF into Active supervisor
b) command: copy bootflash:s72033-advipservicesk9_wan-mz.122-33.SXI2a.bin disk0:
c) command: verify disk0:s72033-advipservicesk9_wan-mz.122-33.SXI2a.bin
d) Once the verify is successful please resume the previous process.
Method 2:
1) Remove the failing supervisor (which should not be the current active)
2) Plug your laptop into the console port of the replacement supervisor and get your terminal program
working
3) Insert the replacement supervisor into the chassis, firmly seating the supervisor into the chassis.
4) Watch the supervisor come up, making sure that it boots properly and doesn't get stuck in <rommon>
5) Log in to the current active supervisor
6) command: show redundancy
You're looking to see that the new supervisor is listed as <Standby> or <Standby Cold>
7) If the above is true continue to step 8, if the state is <Other> or <Unknown> please check to make sure
the new supervisor isn't in rommon
8) command: copy bootflash:s72033-advipservicesk9_wan-mz.122-33.SXI2a.bin
slavebootflash:s72033-advipservicesk9_wan-mz.122-33.SXI2a.bin
9) command: dir slavebootflash:
Confirm that the IOS is now on the slavebootflash:
10)command: verify slavebootflash:s72033-advipservicesk9_wan-mz.122-33.SXI2a.bin
Confirm the CRC is correct
11)command: hw-module module <x> reset
The value <x> is the slot number of the module that was replaced. If you enter this incorrectly
you may reload the entire chassis, use with caution
12)Wait for the standby supervisor to fully load
13)command: show redundancy
Should show the state of the standby supervisor as "Standby Hot"
14)Now you're done.
Please post requests for clarification below.
If this helped you resolve an issue please leave feedback so we can continue to improve our community efforts.
Thank you.
