On 05/03/07, Ricardo Marin Vinuesa <[EMAIL PROTECTED]> wrote: > The first stage of the process was making tests generating the traps > manually. And it worked fine. In order to generate the traps, I was > executing the following command: > > bash# snmptrap -v3 -u usmuser -X passwd -A passwd localhost....
But those are *not* the same options that you listed in your "trapsess" line. In particular, you don't set an explicit engine ID here, whereas you did in the snmpd.conf file entry. And that trapsess line included the flag -Ci, to send an INFORM (rather than a TRAP). The command above is sending a TRAP. > At this very moment, I was trying to send the traps by unplugging the > network cable and configure the configuration files properly. You're probably trying to go too fast. If you need to trigger a trap from the agent, then the simplest way is probably to shut it down, or start it up. The trapsess line will send a notification to the trap receiver. > Regarding your suggestions: > > When I only leave the createUser and one authUser line in > snmptrapd.conf, I get the following line at the log: And what is in the snmpd.conf file? Just the "trapsess" line, or do you still have the "trapsink" ? This log fragment feels to be handling a v1/v2c trap, which is not relevant to SNMPv3 handling. Get rid of everything trap-related in the snmpd.conf file except the "trapsess" line, and use *exactly* the same options as your successful "snmptrap" command. Dave ------------------------------------------------------------------------- Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT & business topics through brief surveys-and earn cash http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV _______________________________________________ Net-snmp-coders mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/net-snmp-coders
