[c-nsp] Sup720 Redundancy Problems

[Jeffrey G. Fitzwater]

We had a problem when we first used redundant sups because we defined boot config to be on disk0: .

The standby sup would constantly reboot until I removed that command and used the boot from nvram.

Jeff Fitzwater


Princeton University


On Aug 17, 2014, at 5:35 AM, Ben Hammadi, Kayssar (NSN - TN/Tunis) <kayssar.ben_hammadi at nsn.com> wrote:

> Hi,
> 
> Try : redundancy config-sync ignore mismatch , then reload the standby
> 
> Cdt
> Kayssar
> 
>> On Aug 17, 2014, at 4:04, "ext Tammy Firefly" <tammy-lists at wiztech.biz> wrote:
>> 
>> 
>>> On 8/16/14, 20:53:18, Frank Bulk wrote:
>>> Looks like you got them all on =)
>>> 
>>> When you successfully boot the new SUP in a separate chassis is it running
>>> the exact same software as the production SUP?
>> 
>> Yup exact same image.
>> 
>>> 
>>> One other article I read suggested changing the mode to RPR
>>> (http://www.cisco.com/c/en/us/td/docs/ios/12_2sr/release/notes/122SRcavs2.pd
>>> f) which means:
>>> conf t
>>> redundancy
>>> mode rpr
>>> end
>> Ill give this a try.
>> 
>> 
>> One thing I did notice is the new sup has a 128MB CF card in a flash
>> adapter on the sup, the other sup has a 64mb flash module.
>> Would that cause this?
>> 
>>> 
>>> Frank
>> 
>> _______________________________________________
>> cisco-nsp mailing list  cisco-nsp at 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 at puck.nether.net
> https://puck.nether.net/mailman/listinfo/cisco-nsp
> archive at http://puck.nether.net/pipermail/cisco-nsp/