On 19 May 2010 21:50, Joan Landry <joan.lan...@overturenetworks.com> wrote: > I have used a v2 trap2sink in the past and so I know the basic trap > mechanism works in my system.
Note that community-based traps are a *lot* simpler to work with than SNMPv3 notifications. Ron has already pointed you to the relevant tutorial page. It's definitely worth working through that, step by step. Get things working with that particular configuration first, and then try adapting it to your own setup. > For v3 I have the following set up in snmpd.conf: None of the access control stuff is relevant to sending traps. The only entries you need worry about are: > authtrapenable 1 > trapsess -e ENGINEID -l noauth -u v3user4 10.11.12.171 > createUser v3user4 > > where ENGINEID - is the value I read from > engineIDLen = snmpv3_get_engineID(engineID, SNMP_MAXBUF); What settings do you have in your snmptrapd.conf ? How have you created the SNMPv3 user there? What access control directives do you have in the trapd config file? > I am not seeing any error messages. > I use send_v2trap(var_list) in my code to send the traps. > But the receiving station never get them. Try sending test notifications using "snmptrap". Make sure that the trap receiver gets them. Then use the same options for your 'trapsess' line. Dave ------------------------------------------------------------------------------ _______________________________________________ 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
