>       But you only authorized execution, not logging.  Change "execute"
>to "log" above and you should see the notifications.
>
Nope - changed it to 'log' and I still don’t anything reported by the trap 
daemon.  I think the purpose of execute was there to allow it to run a script 
from the traphandle directive, right?  It wasn't doing that either.  Are there 
other switched worth trying with snmptrapd?

So just to be clear, at the 4 commands I'm sending it correct?  As I said I 
just cut/pasted these out of the faq and want to make sure I'm sending 
something legitmate:

snmptrap -v 1 -c public localhost "" "" 0 0  ""
snmptrap -v 1 -c public localhost "" "" 6 99 ""
snmptrap -v 2c -c public localhost "" UCD-SNMP-MIB::ucdStart
snmptrap -v 2c -c public localhost "" .1.3.6.1.4.1.2021.251.1

I may not have mentioned this but I'm running 5.4 of net-snmp.  I also tried 
running it with -D and it prints a ton of stuff.  If I then run one of the 
snmptrap commands it doesn't do a thing so clearly nothing is waking it up, if 
that helps.  Also if I run snmptrapd with -d, it doesn't report anything when I 
send traps.

-mark

>
>       HTH,
>
>Mike

------------------------------------------------------------------------------
This SF.Net email is sponsored by the Verizon Developer Community
Take advantage of Verizon's best-in-class app development support
A streamlined, 14 day to market process makes app distribution fast and easy
Join now and get one step closer to millions of Verizon customers
http://p.sf.net/sfu/verizon-dev2dev 
_______________________________________________
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

Reply via email to