Traps - Alarm and clear use the same SNMP trap

Marc Doesburg <[email protected]>
Newsgroups gmane.network.opennms.general
Message-ID <CAE_XvpanBfrN=C7djyUwnG=On-Lt3JuU7udZhgmKDKOZjhz=0g@mail.gmail.com>
Hello All,

I’ve 2 questions regarding SNMP traps.

We have a system that sends “the same” trap message for an alarm and a
clear. Depending on %parm[#4]% it’s either an alarm or a clear.

I’m able to configure the event as an alarm. But now the clear also
generates an alarm in the log and doesn't clear the original alarm.

My first question is: Is there a way to set the severity using %parm[#4]%?
So, I don’t have to manually set/configure all the alarm severity’s
individually?

My second question is: Can I use %parm[#4]% to clear the previous alarm?
Also, the clear needs to be linked to the right original alarm. For
example, if the machines lose connection to 2 different end-points (i.e.
endpoint A and endpoint B) the clear for endpoint A needs to clear the
alarm of endpoint A and not B 😊. I’m not sure yet, but I think %parm[#3]%
describes the endpoint.

I’m also not sure if it’s useful, but I’ve added the events.xml for the
system I’m trying to configure this for. I’m currently trying to configure
it for “AcBoard defined trap event: acIpGroupNoRouteAlarm”, but a lot of
the alarms are going to need this.

Thanks in advance for your help.

Best regards,

Marc D.

------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot

_______________________________________________
Please read the OpenNMS Mailing List FAQ:
http://www.opennms.org/index.php/Mailing_List_FAQ

opennms-discuss mailing list

To *unsubscribe* or change your subscription options, see the bottom of this page:
https://lists.sourceforge.net/lists/listinfo/opennms-discuss
AcBoard.events.rar (application/rar, 11.3 KB) - not displayed
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.