> Interestingly when I looked at the man file for snmp.conf it said that
> all I needed was an informsink line
No.
This section is documenting three related directives:
trapsink
trap2sink
informsink
These commands define the hosts to receive traps...
You need *either* trapsink, *or* trap2sink, *or* informsink
(depending on what sort of notification you want to send).
> so I added "informsinc <host> public" to snmpd.conf. This gave me
> persistant snmpd: send_trap: Timeout messages.
Hmmm... Odd - I'll intestigate when I have a minute.
> When I changed snmpd.conf to read:-
>
> trapcommunity public
> trap2sink <host>
> informsink <host>
>
> it started to work.
You should *not* need both "trap2sink" and "informsink".
Such a configuration will (try) to send *two* copies of each trap
(one as a trap and one as an inform).
trapcommunity public
trap2sink <host>
should be directly equivalent to
trap2sink <host> public
and similarly for trapcommunity/informsink.
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
