AB> Simply add a community to the informsink line:
AB>
AB> informsink <host> public
AB>
AB> should solve the timeout.
But if you look at David's original report, he *did* have a community
field as part of that entry:
vvvvvv
DG> .... I added "informsinc <host> public" to snmpd.conf. This gave me
DG> persistant snmpd: send_trap: Timeout messages.
I think the problem is more likely to be related to using
(acknowledged) INFORM requests, rather than (unacknowledged) traps.
The obvious question (which I forgot to ask):
David - do you have a trap-handler application listening for
such notifications on the remote host?
Does it support SNMPv2 ?
Dave
-------------------------------------------------------
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