If your goal is to intentionally run different code on your two
supervisors, with a cold standby to take over in case some bug in SXH5
causes a supervisor crash, then no it's not a problem you've got it
operating as planned.
But few people do it that way, I assume you want the whole system to
be running SXH5, and have a Hot standby who will take over quickly in
the event of hardware failure. If that's the case, then like Matthew
said, you need to get the SXH5 code on your standby sup, and reboot it
on that code ("redundancy reload peer" IIRC). They should show up
with the same IOS in the "show module" command, and should be Standby
Hot, not Standby Cold.
You mention booting off a CF card. If that's your desired method, you
need a second CF card plugged into the second supervisor, with the
same code on it. Otherwise you can boot from the sup-bootdisk, but
you still need a copy on both supervisors. Any filesystem (disk0,
bootflash, sup-bootdisk, etc) can be reached on the backup Supervisor
by calling it slave[name of filesystem], like slavedisk0: or
slavebootflash:
-Geoff
On Fri, Jul 17, 2009 at 10:17 AM, Bill
Blackford<bblackf...@nwresd.k12.or.us> wrote:
> I recently installed these sups and the 6748. I'm noticing that the active
> sup lists the IOS I'm booting up from the CF card and the in-active sup lists
> the IOS on sup-bootflash. The 6748 lists the newer IOS as well.
>
> 1. Is this a problem?
> 2. If #1 = yes, then how must one fix the problem?
>
> Thank you
>
>
> Mod Ports Card Type Model Serial No.
> --- ----- -------------------------------------- ------------------
> -----------
> 1 48 48 port 10/100 mb RJ45 WS-X6348-RJ-45 SAL
> 2 48 CEF720 48 port 10/100/1000mb Ethernet WS-X6748-GE-TX SAL
> 3 8 8 port 1000mb GBIC Enhanced QoS WS-X6408A-GBIC SAD
> 4 16 16 port 1000mb GBIC ethernet WS-X6416-GBIC SAL
> 5 2 Supervisor Engine 720 (Active) WS-SUP720-3BXL SAL
> 6 2 Supervisor Engine 720 (Cold) WS-SUP720-3BXL SAL
>
> Mod MAC addresses Hw Fw Sw Status
> --- ---------------------------------- ------ ------------ ------------
> -------
> 1 0004.2861.2750 to 0004.2861.277f 2.2 5.4(2) 8.7(0.22)BUB Ok
> 2 0025.840c.9310 to 0025.840c.933f 3.0 12.2(18r)S1 12.2(33)SXH5 Ok
> 3 0002.fc25.0984 to 0002.fc25.098b 1.3 5.4(2) 8.7(0.22)BUB Ok
> 4 0008.a4f6.1784 to 0008.a4f6.1793 2.2 5.4(2) 8.7(0.22)BUB Ok
> 5 001f.6c77.13b0 to 001f.6c77.13b3 5.8 8.5(3) 12.2(33)SXH5 Ok
> 6 001f.6c77.13c8 to 001f.6c77.13cb 5.8 8.5(3) 12.2(18)SXF1 Ok
>
> Mod Sub-Module Model Serial Hw Status
> ---- --------------------------- ------------------ ----------- -------
> -------
> 2 Centralized Forwarding Card WS-F6700-CFC SAL 4.1 Ok
> 5 Policy Feature Card 3 WS-F6K-PFC3BXL SAL 1.10 Ok
> 5 MSFC3 Daughterboard WS-SUP720 SAL 3.3 Ok
> 6 Policy Feature Card 3 WS-F6K-PFC3BXL SAL 1.10 Ok
> 6 MSFC3 Daughterboard WS-SUP720 SAL 3.3 Ok
>
> Mod Online Diag Status
> ---- -------------------
> 1 Pass
> 2 Pass
> 3 Pass
> 4 Pass
> 5 Pass
> 6 Pass
>
>
>
> -b
>
> --
> Bill Blackford
> Senior Network Engineer
> Northwest Regional ESD
>
> my /home away from home
>
>
> _______________________________________________
> cisco-nsp mailing list cisco-...@puck.nether.net
> https://puck.nether.net/mailman/listinfo/cisco-nsp
> archive at http://puck.nether.net/pipermail/cisco-nsp/
>
_______________________________________________
cisco-nsp mailing list cisco-nsp@puck.nether.net
https://puck.nether.net/mailman/listinfo/cisco-nsp
archive at http://puck.nether.net/pipermail/cisco-nsp/
