Re: single snmp trap/event to multiple opennms instances

This is something worth investigating: https://github.com/sleinen/samplicator

> On 31. Jul 2018, at 13:39, David Hustace <[email protected]> wrote:
> 
> Signed PGP part
> 
> 
>> On Jul 31, 2018, at 07:01, Mike Kelly <[email protected]> wrote:
>> 
>> I haven't used the second solution (having OpenNMS send traps), so I can't speak further to it.
> 
> The SNMP Trap North Bounder is for sending Alarm updates to another console.  It's not a trap proxy/forwarder so to speak.  So, that won't work for duplicating traps.  The best two way are:
> 
> 1) As you described, from the source (the devices/servers), send traps to two different NMS'; a.k.a. SNMP Trap sinks.
> 
> 2) Use a load balancer solution and configure your devices to send all traps to a the load balanced VIP which then is configured to forward the UDP datagrams to each NMS.
> 
> Option 1 is most economical.  Option 2 is nice because you only need to configure one address in the devices and that IP can be managed with routing and application layer tools such as a load balancer.
> 
> Using a proxy introduces complications with determining the source of SNMP v2c notifications (traps).
> 
> 
> 
> David Hustace
> The OpenNMS Group, Inc.
> +1 (919) 443-1562
> 
> 
> 


------------------------------------------------------------------------------
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