Mailing List Archive

SNMP OIDs for Yellow/Red Alarm on MX204
Hi Guys,

i just found out that it seems not to be possible to poll Yellow/Red Alarm (Count or State) on MX204 via SNMP.

On other platforms the craft panel (craftd) handles that alarms and its not there on MX204 so you can't use it.

Also there seems to be no alternative OID to poll for Alarms ?

I dont like snmp traps as they can get lost ....

Any hints or ideas?

Regards
Joerg

_______________________________________________
juniper-nsp mailing list juniper-nsp@puck.nether.net
https://puck.nether.net/mailman/listinfo/juniper-nsp
Re: SNMP OIDs for Yellow/Red Alarm on MX204 [ In reply to ]
I expect you don't like the idea of syslog for the same reason as SNMP traps...

So perhaps you could craft something using SLAX? I would be a little surprised if someone hasn't already done this somewhere:

https://www.juniper.net/documentation/en_US/junos/topics/example/junos-script-automation-snmp-script-example.html

-----Original Message-----
From: juniper-nsp [mailto:juniper-nsp-bounces@puck.nether.net] On Behalf Of Joerg Staedele
Sent: Thursday, February 28, 2019 9:33 AM
To: juniper-nsp@puck.nether.net
Subject: [j-nsp] SNMP OIDs for Yellow/Red Alarm on MX204

Hi Guys,

i just found out that it seems not to be possible to poll Yellow/Red Alarm (Count or State) on MX204 via SNMP.

On other platforms the craft panel (craftd) handles that alarms and its not there on MX204 so you can't use it.

Also there seems to be no alternative OID to poll for Alarms ?

I dont like snmp traps as they can get lost ....

Any hints or ideas?

Regards
Joerg

_______________________________________________
juniper-nsp mailing list juniper-nsp@puck.nether.net
https://puck.nether.net/mailman/listinfo/juniper-nsp
_______________________________________________
juniper-nsp mailing list juniper-nsp@puck.nether.net
https://puck.nether.net/mailman/listinfo/juniper-nsp
Re: SNMP OIDs for Yellow/Red Alarm on MX204 [ In reply to ]
hey,

> i just found out that it seems not to be possible to poll Yellow/Red Alarm (Count or State) on MX204 via SNMP.

This is pretty sad, juniper, please fix this.

Polling for redAlarmCount > 0 or yellowAlarmCount > 0 has been a good
generic solution to cover a lot of ground quickly.

--
tarko
_______________________________________________
juniper-nsp mailing list juniper-nsp@puck.nether.net
https://puck.nether.net/mailman/listinfo/juniper-nsp
Re: SNMP OIDs for Yellow/Red Alarm on MX204 [ In reply to ]
These don't work on the 204?

Red Alarm: jnxRedAlarmState 1.3.6.1.4.1.2636.3.4.2.3.1
Yellow Alarm: jnxYellowAlarmState 1.3.6.1.4.1.2636.3.4.2.2.1

On Thu, Feb 28, 2019 at 2:51 PM Tarko Tikan <tarko@lanparty.ee> wrote:

> hey,
>
> > i just found out that it seems not to be possible to poll Yellow/Red
> Alarm (Count or State) on MX204 via SNMP.
>
> This is pretty sad, juniper, please fix this.
>
> Polling for redAlarmCount > 0 or yellowAlarmCount > 0 has been a good
> generic solution to cover a lot of ground quickly.
>
> --
> tarko
> _______________________________________________
> juniper-nsp mailing list juniper-nsp@puck.nether.net
> https://puck.nether.net/mailman/listinfo/juniper-nsp
>
_______________________________________________
juniper-nsp mailing list juniper-nsp@puck.nether.net
https://puck.nether.net/mailman/listinfo/juniper-nsp
Re: SNMP OIDs for Yellow/Red Alarm on MX204 [ In reply to ]
On Thu Feb 28, 2019 at 03:19:36PM -0500, Tom Beecher wrote:
> These don't work on the 204?
>
> Red Alarm: jnxRedAlarmState 1.3.6.1.4.1.2636.3.4.2.3.1
> Yellow Alarm: jnxYellowAlarmState 1.3.6.1.4.1.2636.3.4.2.2.1

They don't seem to exist on either MX10003 or MX204...

$ snmpwalk -v 2c -c xxx mx10003 .1.3.6.1.4.1.2636.3.4
iso.3.6.1.4.1.2636.3.4 = No Such Object available on this agent at this OID

$ snmpwalk -v 2c -c xxx mx204 .1.3.6.1.4.1.2636.3.4
iso.3.6.1.4.1.2636.3.4 = No Such Object available on this agent at this OID

Simon
_______________________________________________
juniper-nsp mailing list juniper-nsp@puck.nether.net
https://puck.nether.net/mailman/listinfo/juniper-nsp
Re: SNMP OIDs for Yellow/Red Alarm on MX204 [ In reply to ]
Wow that does suck … have used those alarm OID’s for a very long time with Juniper boxes ….

> On Feb 28, 2019, at 3:27 PM, Simon Lockhart <simon@slimey.org> wrote:
>
> On Thu Feb 28, 2019 at 03:19:36PM -0500, Tom Beecher wrote:
>> These don't work on the 204?
>>
>> Red Alarm: jnxRedAlarmState 1.3.6.1.4.1.2636.3.4.2.3.1
>> Yellow Alarm: jnxYellowAlarmState 1.3.6.1.4.1.2636.3.4.2.2.1
>
> They don't seem to exist on either MX10003 or MX204...
>
> $ snmpwalk -v 2c -c xxx mx10003 .1.3.6.1.4.1.2636.3.4
> iso.3.6.1.4.1.2636.3.4 = No Such Object available on this agent at this OID
>
> $ snmpwalk -v 2c -c xxx mx204 .1.3.6.1.4.1.2636.3.4
> iso.3.6.1.4.1.2636.3.4 = No Such Object available on this agent at this OID
>
> Simon
> _______________________________________________
> juniper-nsp mailing list juniper-nsp@puck.nether.net
> https://puck.nether.net/mailman/listinfo/juniper-nsp

_______________________________________________
juniper-nsp mailing list juniper-nsp@puck.nether.net
https://puck.nether.net/mailman/listinfo/juniper-nsp
Re: SNMP OIDs for Yellow/Red Alarm on MX204 [ In reply to ]
Weird.. those still show as valid through 18.4...



On Thu, Feb 28, 2019 at 3:31 PM Paul Stewart <paul@paulstewart.org> wrote:

> Wow that does suck … have used those alarm OID’s for a very long time with
> Juniper boxes ….
>
> > On Feb 28, 2019, at 3:27 PM, Simon Lockhart <simon@slimey.org> wrote:
> >
> > On Thu Feb 28, 2019 at 03:19:36PM -0500, Tom Beecher wrote:
> >> These don't work on the 204?
> >>
> >> Red Alarm: jnxRedAlarmState 1.3.6.1.4.1.2636.3.4.2.3.1
> >> Yellow Alarm: jnxYellowAlarmState 1.3.6.1.4.1.2636.3.4.2.2.1
> >
> > They don't seem to exist on either MX10003 or MX204...
> >
> > $ snmpwalk -v 2c -c xxx mx10003 .1.3.6.1.4.1.2636.3.4
> > iso.3.6.1.4.1.2636.3.4 = No Such Object available on this agent at this
> OID
> >
> > $ snmpwalk -v 2c -c xxx mx204 .1.3.6.1.4.1.2636.3.4
> > iso.3.6.1.4.1.2636.3.4 = No Such Object available on this agent at this
> OID
> >
> > Simon
> > _______________________________________________
> > juniper-nsp mailing list juniper-nsp@puck.nether.net
> > https://puck.nether.net/mailman/listinfo/juniper-nsp
>
>
_______________________________________________
juniper-nsp mailing list juniper-nsp@puck.nether.net
https://puck.nether.net/mailman/listinfo/juniper-nsp
Re: SNMP OIDs for Yellow/Red Alarm on MX204 [ In reply to ]
On Thu, 28 Feb 2019 20:19:36 +0000
Tom Beecher <beecher@beecher.cc> wrote:

> These don't work on the 204?
>
> Red Alarm: jnxRedAlarmState 1.3.6.1.4.1.2636.3.4.2.3.1
> Yellow Alarm: jnxYellowAlarmState 1.3.6.1.4.1.2636.3.4.2.2.1

No.

$ snmpwalk -v2c -c foobar 192.0.2.1 1.3.6.1.4.1.2636.3.4.2.3.1
SNMPv2-SMI::enterprises.2636.3.4.2.3.1 = No Such Object available on this agent at this OID

$ snmpwalk -v2c -c foobar 192.0.2.1 1.3.6.1.4.1.2636.3.4.2.2.1
SNMPv2-SMI::enterprises.2636.3.4.2.2.1 = No Such Object available on this agent at this OID

I had recently discovered this as well and opened a ticket about it
just to make sure. The responses I got included:

"There is no MIB available to monitor the chassis cluster state, only
SNMP traps are supported for failover and other events"

Unless there is some unknown (to me) hardware-related limitation, I
intend to contact our local sales rep for a feature request.
Presumably this is the right path for a change, so others should do
this as well as a signal to Juniper that there is customer demand.

John
_______________________________________________
juniper-nsp mailing list juniper-nsp@puck.nether.net
https://puck.nether.net/mailman/listinfo/juniper-nsp
Re: SNMP OIDs for Yellow/Red Alarm on MX204 [ In reply to ]
Once upon a time, Simon Lockhart <simon@slimey.org> said:
> On Thu Feb 28, 2019 at 03:19:36PM -0500, Tom Beecher wrote:
> > These don't work on the 204?
> >
> > Red Alarm: jnxRedAlarmState 1.3.6.1.4.1.2636.3.4.2.3.1
> > Yellow Alarm: jnxYellowAlarmState 1.3.6.1.4.1.2636.3.4.2.2.1
>
> They don't seem to exist on either MX10003 or MX204...

What about the other newer REs that run the RE in a VM? I wonder if
that's the change.
--
Chris Adams <cma@cmadams.net>
_______________________________________________
juniper-nsp mailing list juniper-nsp@puck.nether.net
https://puck.nether.net/mailman/listinfo/juniper-nsp
Re: SNMP OIDs for Yellow/Red Alarm on MX204 [ In reply to ]
On Thu Feb 28, 2019 at 03:33:44PM -0500, Tom Beecher wrote:
> Weird.. those still show as valid through 18.4...

I'm running 18.1R2.5 on these - wonder if they add it back in on later
versions...

Simon
_______________________________________________
juniper-nsp mailing list juniper-nsp@puck.nether.net
https://puck.nether.net/mailman/listinfo/juniper-nsp
Re: SNMP OIDs for Yellow/Red Alarm on MX204 [ In reply to ]
On Thu, 28 Feb 2019 20:48:52 +0000
Simon Lockhart <simon@slimey.org> wrote:

> I'm running 18.1R2.5 on these - wonder if they add it back in on later
> versions...

Not available on 18.4R1.8.

John
_______________________________________________
juniper-nsp mailing list juniper-nsp@puck.nether.net
https://puck.nether.net/mailman/listinfo/juniper-nsp
Re: SNMP OIDs for Yellow/Red Alarm on MX204 [ In reply to ]
I open TAC case about it few months ago
We tried hard with our SE and the JTAC but the developers didnt agreed to
add it
Maybe if more people will push it they will add it as QFX/SRX/EX ... does
not have craft interface and they support this MIB
BTW you can also try to monitor it with Netconf or the Rest API (set system
services rest http ) I just use it for SRX cluster status that dosent
support get (Just traps )

Nitzan


On Thu, Feb 28, 2019 at 10:51 PM John Kristoff <jtk@depaul.edu> wrote:

> On Thu, 28 Feb 2019 20:48:52 +0000
> Simon Lockhart <simon@slimey.org> wrote:
>
> > I'm running 18.1R2.5 on these - wonder if they add it back in on later
> > versions...
>
> Not available on 18.4R1.8.
>
> John
> _______________________________________________
> juniper-nsp mailing list juniper-nsp@puck.nether.net
> https://puck.nether.net/mailman/listinfo/juniper-nsp
>
_______________________________________________
juniper-nsp mailing list juniper-nsp@puck.nether.net
https://puck.nether.net/mailman/listinfo/juniper-nsp
Re: SNMP OIDs for Yellow/Red Alarm on MX204 [ In reply to ]
Hi all,

do you have an ER (Enhancement Request) ID for us to beg our SE/sales rep for in order to support this?

Best regards,
Theo Voss

> Am 28.02.2019 um 23:00 schrieb Nitzan Tzelniker <nitzan.tzelniker@gmail.com>:
>
> I open TAC case about it few months ago
> We tried hard with our SE and the JTAC but the developers didnt agreed to
> add it
> Maybe if more people will push it they will add it as QFX/SRX/EX ... does
> not have craft interface and they support this MIB
> BTW you can also try to monitor it with Netconf or the Rest API (set system
> services rest http ) I just use it for SRX cluster status that dosent
> support get (Just traps )
>
> Nitzan
>
>
>> On Thu, Feb 28, 2019 at 10:51 PM John Kristoff <jtk@depaul.edu> wrote:
>>
>> On Thu, 28 Feb 2019 20:48:52 +0000
>> Simon Lockhart <simon@slimey.org> wrote:
>>
>>> I'm running 18.1R2.5 on these - wonder if they add it back in on later
>>> versions...
>>
>> Not available on 18.4R1.8.
>>
>> John
>> _______________________________________________
>> juniper-nsp mailing list juniper-nsp@puck.nether.net
>> https://puck.nether.net/mailman/listinfo/juniper-nsp
>>
> _______________________________________________
> juniper-nsp mailing list juniper-nsp@puck.nether.net
> https://puck.nether.net/mailman/listinfo/juniper-nsp
_______________________________________________
juniper-nsp mailing list juniper-nsp@puck.nether.net
https://puck.nether.net/mailman/listinfo/juniper-nsp
Re: SNMP OIDs for Yellow/Red Alarm on MX204 [ In reply to ]
The case was 2018-0913-0086
We didn't open ER

Nitzan

On Fri, Mar 1, 2019 at 12:06 AM Theo Voss <mail@theo-voss.de> wrote:

> Hi all,
>
> do you have an ER (Enhancement Request) ID for us to beg our SE/sales rep
> for in order to support this?
>
> Best regards,
> Theo Voss
>
> > Am 28.02.2019 um 23:00 schrieb Nitzan Tzelniker <
> nitzan.tzelniker@gmail.com>:
> >
> > I open TAC case about it few months ago
> > We tried hard with our SE and the JTAC but the developers didnt agreed to
> > add it
> > Maybe if more people will push it they will add it as QFX/SRX/EX ... does
> > not have craft interface and they support this MIB
> > BTW you can also try to monitor it with Netconf or the Rest API (set
> system
> > services rest http ) I just use it for SRX cluster status that dosent
> > support get (Just traps )
> >
> > Nitzan
> >
> >
> >> On Thu, Feb 28, 2019 at 10:51 PM John Kristoff <jtk@depaul.edu> wrote:
> >>
> >> On Thu, 28 Feb 2019 20:48:52 +0000
> >> Simon Lockhart <simon@slimey.org> wrote:
> >>
> >>> I'm running 18.1R2.5 on these - wonder if they add it back in on later
> >>> versions...
> >>
> >> Not available on 18.4R1.8.
> >>
> >> John
> >> _______________________________________________
> >> juniper-nsp mailing list juniper-nsp@puck.nether.net
> >> https://puck.nether.net/mailman/listinfo/juniper-nsp
> >>
> > _______________________________________________
> > juniper-nsp mailing list juniper-nsp@puck.nether.net
> > https://puck.nether.net/mailman/listinfo/juniper-nsp
>
_______________________________________________
juniper-nsp mailing list juniper-nsp@puck.nether.net
https://puck.nether.net/mailman/listinfo/juniper-nsp
Re: SNMP OIDs for Yellow/Red Alarm on MX204 [ In reply to ]
On Thu, 28 Feb 2019 22:06:27 +0000
Theo Voss <mail@theo-voss.de> wrote:

> do you have an ER (Enhancement Request) ID for us to beg our SE/sales
> rep for in order to support this?

I just requested from a local rep. When and if I get one I'll respond
to this thread.

John
_______________________________________________
juniper-nsp mailing list juniper-nsp@puck.nether.net
https://puck.nether.net/mailman/listinfo/juniper-nsp
Re: SNMP OIDs for Yellow/Red Alarm on MX204 [ In reply to ]
Hi,

Our rep opened ER-080949 last month.

Cheers.

--
Arzhel

On Thu, Feb 28, 2019, at 23:59, John Kristoff wrote:
> On Thu, 28 Feb 2019 22:06:27 +0000
> Theo Voss <mail@theo-voss.de> wrote:
>
> > do you have an ER (Enhancement Request) ID for us to beg our SE/sales
> > rep for in order to support this?
>
> I just requested from a local rep. When and if I get one I'll respond
> to this thread.
>
> John
> _______________________________________________
> juniper-nsp mailing list juniper-nsp@puck.nether.net
> https://puck.nether.net/mailman/listinfo/juniper-nsp
>
_______________________________________________
juniper-nsp mailing list juniper-nsp@puck.nether.net
https://puck.nether.net/mailman/listinfo/juniper-nsp
Re: SNMP OIDs for Yellow/Red Alarm on MX204 [ In reply to ]
Maybe you can use an SNMP script as a workaround?
https://www.juniper.net/documentation/en_US/junos/topics/example/junos-script-automation-snmp-script-example.html

/Roger

On Fri, Aug 7, 2020 at 3:32 PM Arzhel Younsi <arzhel@younsi.org> wrote:

> Hi,
>
> Our rep opened ER-080949 last month.
>
> Cheers.
>
> --
> Arzhel
>
> On Thu, Feb 28, 2019, at 23:59, John Kristoff wrote:
> > On Thu, 28 Feb 2019 22:06:27 +0000
> > Theo Voss <mail@theo-voss.de> wrote:
> >
> > > do you have an ER (Enhancement Request) ID for us to beg our SE/sales
> > > rep for in order to support this?
> >
> > I just requested from a local rep. When and if I get one I'll respond
> > to this thread.
> >
> > John
> > _______________________________________________
> > juniper-nsp mailing list juniper-nsp@puck.nether.net
> > https://puck.nether.net/mailman/listinfo/juniper-nsp
> >
> _______________________________________________
> juniper-nsp mailing list juniper-nsp@puck.nether.net
> https://puck.nether.net/mailman/listinfo/juniper-nsp
>
_______________________________________________
juniper-nsp mailing list juniper-nsp@puck.nether.net
https://puck.nether.net/mailman/listinfo/juniper-nsp
Re: SNMP OIDs for Yellow/Red Alarm on MX204 [ In reply to ]
Hi Guys.

I still can't understand why Juniper is not integrating a "mapping" for the alarm-OIDs. I know, there's no craftd on the MX204 but in the CLI it also shows yellow/red alarms so the info is already available ...

Kind regards
Joerg

> -----Original Message-----
> From: juniper-nsp <juniper-nsp-bounces@puck.nether.net> On Behalf Of
> Roger Wiklund
> Sent: Wednesday, August 19, 2020 12:30 PM
> To: Arzhel Younsi <arzhel@younsi.org>
> Cc: juniper-nsp <juniper-nsp@puck.nether.net>
> Subject: Re: [j-nsp] SNMP OIDs for Yellow/Red Alarm on MX204
>
> Maybe you can use an SNMP script as a workaround?
> https://www.juniper.net/documentation/en_US/junos/topics/example/jun
> os-script-automation-snmp-script-example.html
>
> /Roger
>
> On Fri, Aug 7, 2020 at 3:32 PM Arzhel Younsi <arzhel@younsi.org> wrote:
>
> > Hi,
> >
> > Our rep opened ER-080949 last month.
> >
> > Cheers.
> >
> > --
> > Arzhel
> >
> > On Thu, Feb 28, 2019, at 23:59, John Kristoff wrote:
> > > On Thu, 28 Feb 2019 22:06:27 +0000
> > > Theo Voss <mail@theo-voss.de> wrote:
> > >
> > > > do you have an ER (Enhancement Request) ID for us to beg our SE/sales
> > > > rep for in order to support this?
> > >
> > > I just requested from a local rep. When and if I get one I'll respond
> > > to this thread.
> > >
> > > John
> > > _______________________________________________
> > > juniper-nsp mailing list juniper-nsp@puck.nether.net
> > > https://puck.nether.net/mailman/listinfo/juniper-nsp
> > >
> > _______________________________________________
> > juniper-nsp mailing list juniper-nsp@puck.nether.net
> > https://puck.nether.net/mailman/listinfo/juniper-nsp
> >
> _______________________________________________
> juniper-nsp mailing list juniper-nsp@puck.nether.net
> https://puck.nether.net/mailman/listinfo/juniper-nsp
_______________________________________________
juniper-nsp mailing list juniper-nsp@puck.nether.net
https://puck.nether.net/mailman/listinfo/juniper-nsp
Re: SNMP OIDs for Yellow/Red Alarm on MX204 [ In reply to ]
Le 19/08/2020 à 12:43, Joerg Staedele a écrit :
> Hi Guys.
>
> I still can't understand why Juniper is not integrating a "mapping" for the alarm-OIDs. I know, there's no craftd on the MX204 but in the CLI it also shows yellow/red alarms so the info is already available ...
>
> Kind regards
> Joerg
>
>> -----Original Message-----
>> From: juniper-nsp<juniper-nsp-bounces@puck.nether.net> On Behalf Of
>> Roger Wiklund
>> Sent: Wednesday, August 19, 2020 12:30 PM
>> To: Arzhel Younsi<arzhel@younsi.org>
>> Cc: juniper-nsp<juniper-nsp@puck.nether.net>
>> Subject: Re: [j-nsp] SNMP OIDs for Yellow/Red Alarm on MX204
>>
>> Maybe you can use an SNMP script as a workaround?
>> https://www.juniper.net/documentation/en_US/junos/topics/example/jun
>> os-script-automation-snmp-script-example.html
>>
>> /Roger
>>
>> On Fri, Aug 7, 2020 at 3:32 PM Arzhel Younsi<arzhel@younsi.org> wrote:
>>
>>> Hi,
>>>
>>> Our rep opened ER-080949 last month.
>>>
>>> Cheers.
>>>
>>> --
>>> Arzhel
>>>
>>> On Thu, Feb 28, 2019, at 23:59, John Kristoff wrote:
>>>> On Thu, 28 Feb 2019 22:06:27 +0000
>>>> Theo Voss<mail@theo-voss.de> wrote:
>>>>
>>>>> do you have an ER (Enhancement Request) ID for us to beg our SE/sales
>>>>> rep for in order to support this?
>>>> I just requested from a local rep. When and if I get one I'll respond
>>>> to this thread.
>>>>
>>>> John

Hi,

ER-080949 was closed :/

We've just discovered this behavior when integrating mx204, and asked to
raise new ER-083047,  for consistent management behavior between all
(mx204/10003) Junos devices.

We said them there is also no craft panel on other gears like EX, but
craftd is there and Yellow/Red alarms are responsive ..

For insterested ones, please join us and escalate to your Juniper rep
once again.

Greetings,

Fabien




_______________________________________________
juniper-nsp mailing list juniper-nsp@puck.nether.net
https://puck.nether.net/mailman/listinfo/juniper-nsp
Re: SNMP OIDs for Yellow/Red Alarm on MX204 [ In reply to ]
Hi.

As a workaround,
https://gist.github.com/tonusoo/2f95c1d377bf658dcf5c8b7c9dba5f57 could
be used. Few examples:

$ snmpwalk -v 2c -c public mx204 .1.3.6.1.4.1.2636.3.4
JUNIPER-ALARM-MIB::jnxYellowAlarmState.0 = INTEGER: off(2)
JUNIPER-ALARM-MIB::jnxYellowAlarmCount.0 = Gauge32: 0
JUNIPER-ALARM-MIB::jnxRedAlarmState.0 = INTEGER: off(2)
JUNIPER-ALARM-MIB::jnxRedAlarmCount.0 = Gauge32: 0
$
$ snmpwalk -v 2c -c public mx204 jnxYellowAlarmCount.0
JUNIPER-ALARM-MIB::jnxYellowAlarmCount.0 = Gauge32: 0
$
$ snmpwalk -v 2c -c public mx204 jnxYellowAlarmCount
JUNIPER-ALARM-MIB::jnxYellowAlarmCount.0 = Gauge32: 0
$
$ snmpget -v 2c -c public mx204 jnxRedAlarmState.0
JUNIPER-ALARM-MIB::jnxRedAlarmState.0 = INTEGER: off(2)
$


Installation:

root@mx204> file list /var/db/scripts/snmp/

/var/db/scripts/snmp/:
mx204_yellow_and_red_alarm.slax

root@mx204> show configuration system scripts snmp | display
inheritance no-comments
/* jnxYellowAlarmState, jnxYellowAlarmCount, jnxRedAlarmState and
jnxRedAlarmCount support */
file mx204_yellow_and_red_alarm.slax {
oid .1.3.6.1.4.1.2636.3.4.2.2.1;
oid .1.3.6.1.4.1.2636.3.4.2.2.2;
oid .1.3.6.1.4.1.2636.3.4.2.3.1;
oid .1.3.6.1.4.1.2636.3.4.2.3.2;
checksum sha-256
bbe81079f38d18c85cf6d8799a7fa459ce3418c5582f746cf743b00a73e0ab91;
}

root@mx204>


The script looks for "Major" or "Minor" alarms in the output of RPCs
for both the "show system alarms" and "show chassis alarms". This
means that alarms listed in both outputs are counted twice for
jnxRedAlarmCount and jnxYellowAlarmCount.

Based on my experience the chassis alarms are a subset of system
alarms, but I'm not sure. It seems to work in a way that certain alarm
types(seen in the XML output) like "ETHER" or "Chassis" are seen in
the output of "show chassis alarms" while all the alarm types are
listed in the output on "show system alarms". On the other hand, the
https://www.juniper.net/documentation/us/en/software/junos/cli-reference/topics/ref/command/show-chassis-alarms.html
states that:

"In Junos, the chassis alarms are different from the system alarms
(viewed by using the show system alarms command)."

Perhaps someone from Juniper could clarify this.


Martin
_______________________________________________
juniper-nsp mailing list juniper-nsp@puck.nether.net
https://puck.nether.net/mailman/listinfo/juniper-nsp