On 06/03/07, Ricardo Marin Vinuesa <[EMAIL PROTECTED]> wrote: > I was followintg your suggestions. At this moment, my snmpd.conf file > looks like: > > snmpd.conf > createUser madeiracomm MD5 madeiramadeira DES madeiramadeira > trapsess -v3 -u usmuser -a MD5 -A md5passwd > -x DES -X despasswd localhost
> snmptrapd.conf > createUser usmuser MD5 md5passwd DES despasswd > authuser log,execute,net usmuser priv Hmmm... That's probably OK, though you might need to specify an explicit engineID for one (or both) of these users. > Log of the snmptrap: > bash# snmptrapd -f -Lo -D [snip] > -----------------------%<----------------------------------------------------- > > This log occurs when I unplug the cable from the Network Interface Card. > It seems as if an alarm has reached (snmp_alarm: run alarm 2). However, > there is some problems with the 'agentx'. I think you can ignore both the agentx and alarm stuff. Neither of them feel relevant to this problem. My concern is that there's nothing in this log fragment that look like the snmptrapd receiving a request (of any sort). Let alone receiving one and discarding it. Can you please try shutting the agent down and restarting it. That should generate two notifications, which should be sent to the snmptrapd receiver. What does the log show then? 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
