topic RE: Netsight alarm self clear in ExtremeCloud IQ- Site Engine Management Center

Netsight alarm self clear

Justsomebodi — Wed, 29 Jul 2015 19:52:00 GMT

Is there a way to have alarms auto clear if the event causing the alarms clear.

RE: Netsight alarm self clear

Curtis_Parish1 — Wed, 29 Jul 2015 20:09:00 GMT

In alarm details, third tab (other options) there is a check box for "cleared by alarms." You have to create an "alarm" that clears the first one. So if your alarm is for interface down you create another alarm for interface up and put that one in the "cleared by" option of the interface down alarm.

RE: Netsight alarm self clear

Justsomebodi — Wed, 29 Jul 2015 20:13:00 GMT

Great, but what does one do with something like a Loop alarm which doesn't send a loop gone trap?

RE: Netsight alarm self clear

Curtis_Parish1 — Thu, 30 Jul 2015 21:10:00 GMT

Is the loop alarm a trap?

RE: Netsight alarm self clear

Justsomebodi — Thu, 30 Jul 2015 22:29:00 GMT

Hi

Yes and know. We do have a trap, but we use the syslog for the alarm.

RE: Netsight alarm self clear

Curtis_Parish1 — Thu, 30 Jul 2015 22:59:00 GMT

I would suggest looking at syslog severity levels and see if there are any messages at the info level that say the loop condition is gone.

RE: Netsight alarm self clear

Chad5 — Fri, 03 Jul 2020 00:42:00 GMT

How about auto clear an alarm after a certain number of hours or days have passed?

Thanks,

RE: Netsight alarm self clear

Dan15 — Thu, 09 Jul 2020 18:30:00 GMT

I think it’s dependent whether the device sends something if the loop is gone or not. Doesn’t matter if trap or syslog. Personally I prefer to work with traps whenever possible because most manufacturer implement traps with clear defined states. So for example Fan running = trapOID.x.x.x.1, Fan defect = trapOID.x.x.x.2
This makes it a lot simpler in XMC to work with self clearing alarms then with syslog and parsed strings. Also if you have different device manufacturers in XMC, parsed syslog strings are difficult to handle.