I need to convert a working subagent application to migrate from sending
SNMP version 2 traps to version 3 traps. From what I have read, the
send_v2trap API is equivalent to send_v3trap, other than the latter
having a context argument.
So how do I configure my Net-SNMP agent to utilize the send_v2trap() API
calls to send version 3 traps? Is this something that can be done via
changes
to the configuration files, or are there programmatic APIs that need to be
called to have send_v2trap() as v3 traps?
What API can be used by an external SNMP system manager to learn the
engineID of the trap sender for adding to its local database? Is this
necessary if the engineID is provided as the "context" argument to the
send_v3trap API? In general, how do SNMP System Manager's know
apriori the engine ids necessary for receiving v3 traps?
____________________________________________________________________________
________
Bob O'Neil | <mailto:[email protected]> mailto:[email protected]
| <http://www.robocomai.com/> http://www.robocomai.com
513.376.9197(office)| 513.829.6769 (home) |
RoboComAI, LLC | 175 Tri County Parkway Suite 112 | Cincinnati, OH
45246
------------------------------------------------------------------------------
Live Security Virtual Conference
Exclusive live event will cover all the ways today's security and
threat landscape has changed and how IT managers can respond. Discussions
will include endpoint security, mobile security and the latest in malware
threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
_______________________________________________
Net-snmp-users mailing list
[email protected]
Please see the following page to unsubscribe or change other options:
https://lists.sourceforge.net/lists/listinfo/net-snmp-users
