On 19 June 2012 21:29, Bob O'Neil <[email protected]> wrote: > I need to convert a working subagent application to migrate from sending > SNMP version 2 traps to version 3 traps.
Does this subagent handle sending the traps itself, or does it pass them off to the master agent? (If you're not sure, then it passes them to the master!) > 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 Yes. If you set up the snmpd.conf file using a suitable 'trapsess' line, then *all* traps will be sent via SNMPv3 - regardless of whether they were generated using send_v2trap, send_v3trap or even send_easy_trap. Similarly for 'trapsink', 'trap2sink', etc. The API used to request the trap is purely concerned with how the trap PDU is specified by the code that calls it. This API has no effect on the SNMP version(s) of the trap(s) that are ultimately generated. See the tutorial pages on SNMPv3 notifications for more details. Dave ------------------------------------------------------------------------------ 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
