[j-nsp] MX-series Redundant RE - Unable to mask fxp0 down alarm
OBrien, Will
ObrienH at missouri.edu
Sun May 1 20:52:49 EDT 2011
Silly question... You did use commit sync, correct?
Will O'Brien
On May 1, 2011, at 7:51 PM, "Chris Kawchuk" <juniperdude at gmail.com> wrote:
> Hi Paul..!
>
> Yeah - I tried that as well initially with no luck.... (and just tried again just now...)
>
> me at wowter> show configuration chassis
> alarm {
> management-ethernet {
> link-down ignore;
> }
> }
>
> user at wowter> show chassis alarms
> 1 alarms currently active
> Alarm time Class Description
> 2011-04-07 11:19:35 EST Major Host 1 fxp0 : Ethernet Link Down
>
> ... Which now definitely leads me to suspect it's a bug in this release; as you don't seem have this issue in 10.0 =)
>
> Thanks! I'll ignore it for now, and see what happens when we do our 10.4 upgrade soon.
>
> - Chris.
>
>
>
> On 2011-05-02, at 10:42 AM, Paul Stewart wrote:
>
>> Hey Chris...
>>
>> On MX480's running 10.0R3.10 we just have it setup as:
>>
>> paul at core2.toronto1> show chassis alarms
>> No alarms currently active
>>
>> paul at core2.toronto1> show configuration chassis alarm
>> management-ethernet {
>> link-down ignore;
>> }
>>
>> Thanks,
>>
>> Paul
>
>
> _______________________________________________
> juniper-nsp mailing list juniper-nsp at puck.nether.net
> https://puck.nether.net/mailman/listinfo/juniper-nsp
More information about the juniper-nsp
mailing list