[j-nsp] MX-series Redundant RE - Unable to mask fxp0 down alarm

[David Lockuan]

Hi Chris,

I have a MX960 with Junos 10.4R1.9 and I have the same problem, I have to do
a restart of chassis-control process and the alarmas was cleared.

I hope to have help you.

---
David

On Mon, May 2, 2011 at 1:03 AM, Brent Jones <brent at servuhome.net> wrote:

> On Sun, May 1, 2011 at 6:00 PM, Chris Kawchuk <juniperdude at gmail.com>
> wrote:
> > Heh. Good question! I just had to double check:
> >
> >> show config system
> >        commit synchronize;
> >
> > Thats in there...... OK let's try it manually.....
> >
> > ckawchuk at jmx480# commit synchronize and-quit
> > re0:
> > configuration check succeeds
> > re1:
> > commit complete
> > re0:
> > commit complete
> > Exiting configuration mode
> >
> > {master}
> > ckawchuk at jmx480> 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
> >
> > Yeah... alarm still there. No worries - it's just an annoyance more than
> anything.
> >
> > - Chris.
> >
> >
> > On 2011-05-02, at 10:52 AM, OBrien, Will wrote:
> >
> >> 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
> >
> >
> > _______________________________________________
> > juniper-nsp mailing list juniper-nsp at puck.nether.net
> > https://puck.nether.net/mailman/listinfo/juniper-nsp
> >
>
> On EX switches, I've had the alarm get stuck. I had to restart
> chassis-control and it went away
>
> --
> Brent Jones
> brent at servuhome.net
>
> _______________________________________________
> juniper-nsp mailing list juniper-nsp at puck.nether.net
> https://puck.nether.net/mailman/listinfo/juniper-nsp
>