I agree with Chuck example of how to do it. That's how I would do it. However, as Chuck says "cross your fingers". I've had too many "bus stalls" and/or sup crashes that I would only do this during a maintenance interval.
As per Cisco Tech, I've "put it in too slowly" and "put it in too fast". Too hard to be Goldilocks and get it perfect. ---- Matthew Huff | 1 Manhattanville Rd Director of Operations | Purchase, NY 10577 OTA Management LLC | Phone: 914-460-4039 > -----Original Message----- > From: cisco-nsp [mailto:[email protected]] On Behalf Of Chuck > Church > Sent: Wednesday, May 29, 2013 12:28 PM > To: 'Edward Salonia'; 'Ben Hammadi, Kayssar (NSN - TN/Tunis)' > Cc: [email protected] > Subject: Re: [c-nsp] 6500 Supervisor redundancy > > If you've got a compact flash card (either a spare, or the one from the > running sup), you could put that in the new sup (if a spare, format it in > the existing sup, and copy that image file to it). Get your console > cable/PC ready, and attach to the new sup. In the existing sup, set the > redundancy mode to SSO. Cross your fingers, and push the new sup in. Break > into ROMMON, and manually boot it off the disk0: card. 'boot > disk0:s72033-....' . That should get the new sup up on the correct IOS, and > SSO should enable itself. Set your boot statement on the existing sup, and > write it, and verify (show bootvar) that both sups agree on the boot image > and confreg. Of course make sure boot images are in the right places now. > > Chuck > > -----Original Message----- > From: cisco-nsp [mailto:[email protected]] On Behalf Of > Edward Salonia > Sent: Wednesday, May 29, 2013 11:28 AM > To: Ben Hammadi, Kayssar (NSN - TN/Tunis) > Cc: [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/ > > _______________________________________________ > 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/
