Dears ,
I did it successfully tonight , the code on the new Sup was SXJ4 however
the code on the running Sup is SXI8a . I just insert the new SUP and it come up
with RPR mode so I copy the SXI8 from Sup-bootdisk to the Slavesub-bootdisck
and reconfigured the boot to make the path change on the new Sup then reset it
and it come to SSO.
The only strange thinks I encounter is that the slot 6 where I inserted the
new Sup was disabled but this didn't prevent the Sup to come up with RPR:
TSA3-PACOSWB9004(config)#no power enable module 6
%FRU Absent. Power admin state updated
TSA3-PACOSWB9004(config)#
TSA3-PACOSWB9004#
May 30 00:37:52.248 GMT+1: %PFREDUN-SP-4-VERSION_MISMATCH: Defaulting to RPR
mode (Different sw versions)
May 30 00:37:53.281 GMT+1: %PFREDUN-SP-6-ACTIVE: Standby initializing for RPR
mode
May 30 00:37:54.437 GMT+1: %FABRIC-SP-5-FABRIC_MODULE_BACKUP: The Switch Fabric
Module in slot 6 became standby
May 30 00:37:57.032 GMT+1: %DIAG-SP-6-RUN_MINIMUM: Module 6: Running Minimal
Diagnostics...
May 30 00:37:57.084 GMT+1: %PFINIT-SP-5-CONFIG_SYNC: Sync'ing the startup
configuration to the standby Router.
May 30 00:38:01.202 GMT+1: %OIR-SP-6-INSCARD: Card inserted in slot 6,
interfaces are now online
May 30 00:38:01.718 GMT+1: %PFREDUN-SP-4-BOOTSTRING_INVALID: The bootfile
sup-bootdisk:s72033-advipservicesk9-mz.122-33.SXI8a.bin is present on the
active supervisor but not on the standby
May 30 00:38:02.583 GMT+1: %RF-SP-5-RF_TERMINAL_STATE: Terminal state reached
for (RPR)
TSA3-PACOSWB9004#
Thanks for your help.
BEN HAMMADI Kayssar
NOKIA SIEMENS NETWORKS
Lead Engineer -BroadBand Connectivity
JNCIE-M (#471), JNCIE-SP (#1147), CCIP
Mobile : +216 29 349 952 / +216 98 349 952
FIX : +216 71 108 173
Skype : kayssar ben hammadi
[email protected]
-----Original Message-----
From: ext Edward Salonia [mailto:[email protected]]
Sent: Wednesday, May 29, 2013 4:28 PM
To: Ben Hammadi, Kayssar (NSN - TN/Tunis)
Cc: ext Justin M. Streiner; [email protected]
Subject: Re: [c-nsp] 6500 Supervisor redendancy
While your mileage may vary I have has great success in doing this exact thing.
RMA sups don't necessarily come with the same code as what you are running. Put
the new sup in (same hardware, right?) and it should boot up into RPR standby
cold due to the mid matched code. At this point copy the code from the flash of
one sup to the other 'wr mem', check 'show red' to ensure config reg and boot
var are correct and a 'redundancy reload peer' should do the trick.
Out of curiosity, what code are you running on this?
Also is your box configured for SSO mode currently and is running in simplex,
or is it configured for RPR. If the latter, I think it may require a reload to
change modes, but I don't recall.
Good luck.
- Ed
On May 28, 2013, at 5:10 PM, "Ben Hammadi, Kayssar (NSN - TN/Tunis)"
<[email protected]> wrote:
> Hi,
>
> My major concern is about the IOS difference , should I find a way to check
> what is the IOS on the new Supervisor or this will not make difference , I
> read the successful stories in Cisco websites but here I am asking people who
> really did that on live Switchs.
>
> Br.
>
> BEN HAMMADI Kayssar
>
> NOKIA SIEMENS NETWORKS
> Lead Engineer -BroadBand Connectivity
> JNCIE-M (#471), JNCIE-SP (#1147), CCIP
>
>
> -----Original Message-----
> From: cisco-nsp [mailto:[email protected]] On Behalf Of ext
> Justin M. Streiner
> Sent: Tuesday, May 28, 2013 9:58 PM
> To: [email protected]
> Subject: Re: [c-nsp] 6500 Supervisor redendancy
>
> On Tue, 28 May 2013, Ben Hammadi, Kayssar (NSN - TN/Tunis) wrote:
>
>> I have a 6509 with a standalone Sup720 and I am preparing to add a
>> redundant one, I don't know the software on the new Supervisor and my
>> final goal is to make both work on SSO mode. Can someone propose a
>> procedure with happy end :) ?
>
> There are numerous resources online that talk about how to configure dual
> supervisors in a Cat6500 switch.
>
> You might be better off asking specific questions, based on things you've
> tried or read through, rather than asking other people to do the majority
> of the work for you.
>
> jms
> _______________________________________________
> cisco-nsp mailing list [email protected]
> https://puck.nether.net/mailman/listinfo/cisco-nsp
> archive at http://puck.nether.net/pipermail/cisco-nsp/
>
> _______________________________________________
> cisco-nsp mailing list [email protected]
> https://puck.nether.net/mailman/listinfo/cisco-nsp
> archive at http://puck.nether.net/pipermail/cisco-nsp/
_______________________________________________
cisco-nsp mailing list [email protected]
https://puck.nether.net/mailman/listinfo/cisco-nsp
archive at http://puck.nether.net/pipermail/cisco-nsp/
