[c-nsp] Sup720 Redundancy Problems

[Tammy Firefly]

Jeff,
We had the same but I changed it to bootflash: show bootvar shows the
changes, Do I need to cycle the running sup to make sure the synch stuff
sees the different path?

Thanks
--Tammy


On 8/17/14, 7:11:45, Jeffrey G. Fitzwater wrote:
> 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/
> 
> 
> 
> ----------
> 
> This email has been scanned for spam and viruses by Proofpoint Essentials cloud email security - visit the following URL to report this email as spam:
> https://us1.proofpointessentials.com/index01.php?mod_id&mod_option=logitem&midf729600&rid12411&report=1
>