On Fri, 22 Oct 2004 10:11:57 +0100 David wrote: DG> Interestingly when I looked at the man file for snmp.conf it said that DG> all I needed was an informsink line (or at least that was the way I read DG> it), so I added "informsinc <host> public" to snmpd.conf. This gave me DG> persistant snmpd: send_trap: Timeout messages. When I changed DG> snmpd.conf to read:- DG> DG> trapcommunity public DG> trap2sink <host> DG> informsink <host> DG> DG> it started to work. Is the man file in need of updating to make it clearer DG> that you need all of them?
Informsink sends SNMPv3 inform messages. If your trap receiver/NMS doesn't support SNMPv3, then it would probably drop the traps, thus the timeout. Likewise, trap2sink sends SNMPv2c traps, which will also be dropped if your NMS doesn't support SNMPv2c. -- Robert Story; NET-SNMP Junkie <http://www.net-snmp.org/> <irc://irc.freenode.net/#net-snmp> Archive: <http://sourceforge.net/mailarchive/forum.php?forum=net-snmp-users> You are lost in a twisty maze of little standards, all different. ------------------------------------------------------- This SF.net email is sponsored by: IT Product Guide on ITManagersJournal Use IT products in your business? Tell us what you think of them. Give us Your Opinions, Get Free ThinkGeek Gift Certificates! Click to find out more http://productguide.itmanagersjournal.com/guidepromo.tmpl _______________________________________________ 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
