Create an alarm northbound implementation for SNMP Traps
Description
Acceptance / Success Criteria
None
blocks
depends on
Lucidchart Diagrams
Activity
Show:
David Hustace January 4, 2016 at 4:39 PM
Awesome!
Alejandro Galue January 4, 2016 at 3:07 PM
Done!
Branch jira/HZN-564
Alejandro Galue January 4, 2016 at 2:33 PM
Sample trap sink:
I'll leave the port and community, and use them if they are supplied and the target version is v1 or v2c. Otherwise, I'll grab the settings from snmp-config.xml using SnmpAgentConfigFactory
Alejandro Galue January 4, 2016 at 2:24 PMEdited
I figured out that it is not hard to support all traps and informs (assuming that the code from org.opennms.netmgt.scriptd.helper.SnmpTrapHelper defined on opennms-services is accurate, which is what I'm using as a base for the code I use to build the target packets).
As David has suggested, I'm going to use snmp-config.xml to grab the credentials and settings, and remove them from snmptrap-northbounder-config.xml.
Currently, OpenNMS has northbound implementations for Syslog, HTTP and JMS.
There are several use cases that justify forward alarms as SNMP Traps.
For this purpose, we need to design how to map the information available on an alarm to a set of SNMP Varbinds, in order to send a well formed SNMP Trap based on a given MIB.
That will cover the "destination message format", if we compare this with the syslog northbound interface. Of course, we need several destinations and filters, in order to be able to forward traps to different trap receivers using different trap varbinds.