[prev in list] [next in list] [prev in thread] [next in thread] 

List:       opennms-discuss
Subject:    Re: [opennms-discuss] Suppress alarms for bogus traps
From:       "kobi.biton" <kobi () comns ! co ! il>
Date:       2011-06-27 21:53:16
Message-ID: 1309211596854-6522595.post () n2 ! nabble ! com
[Download RAW message or body]

Yep I have a simple idea for you , I am assuming the below:

 - You have configured notifications based on the Trap UEI

If so then all you should do:

 - edit your current notification entry which is responsible for the TRAP
UEI and use a filter like this : 
(IPADDR != 'xxx.xxx.xxx.xxx') 
   where xxx... is your flaky device 

The above will allow opennms to receive the trap from the flaky device
however the trap from this device will never pass the notification filter
thus no notification path will start ... --> no notifications

Hope it helps ...

Kobi,.

--
View this message in context: \
http://opennms.530661.n2.nabble.com/Suppress-alarms-for-bogus-traps-tp6509958p6522595.html
 Sent from the OpenNMS - discuss mailing list archive at Nabble.com.

------------------------------------------------------------------------------
All of the data generated in your IT infrastructure is seriously valuable.
Why? It contains a definitive record of application performance, security 
threats, fraudulent activity, and more. Splunk takes this data and makes 
sense of it. IT sense. And common sense.
http://p.sf.net/sfu/splunk-d2d-c2
_______________________________________________
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


[prev in list] [next in list] [prev in thread] [next in thread]