I'm setting up a monitoring system and have the agents want to send v2 notifications from agents to a NMS. On this NMS I'm using snmptrapd and snmptt to handle the traps, as well as forwarding them to an upstream NMS. However, when they are forwarded to the upstream NMS I'm losing the original agent address and the notifications are appearing to have come from the intermediate NMS - with the result that the users of the upstream NMS can't tell on which piece of equipment the notification is being raised.
With SNMP v1 traps this isn't an issue because the agent address is supplied in the trap, but I can't find any suggestions as to the best way to communicate the agent address to the upstream agent. Should the original agent add a variable binding for it's address, should I modify snmptrapd to add this variable binding before forwarding it? Or is it better to have the intermediate NMS resend the packets but spoof the source address? Is there a standard way of handling this? Am I just going crazy :) Any advice gratefully received. Cheers -- Jonathan Barber <jonathan.bar...@gmail.com> ------------------------------------------------------------------------------ Beautiful is writing same markup. Internet Explorer 9 supports standards for HTML5, CSS3, SVG 1.1, ECMAScript5, and DOM L2 & L3. Spend less time writing and rewriting code and more time creating great experiences on the web. Be a part of the beta today. http://p.sf.net/sfu/beautyoftheweb _______________________________________________ Net-snmp-users mailing list Net-snmp-users@lists.sourceforge.net Please see the following page to unsubscribe or change other options: https://lists.sourceforge.net/lists/listinfo/net-snmp-users
