logo       
Google Custom Search
    AddThis Social Bookmark Button
-->

Re: SNMP notifications: msg#00288

Subject: Re: SNMP notifications
 
> for (sink = sinks; sink; sink = sink->next) {
>     if (sink->version == SNMP_VERSION_1 && trap == -1) {
>         continue;     /* Skip v1 sinks for v2 only traps */

If you're using the default configuration, I think you should
find that that 'sinks' list may well be empty anyway.
  The agent uses the (SNMP-manageable) notification tables
in preference, which are handled by the two callbacks at the
end of this routine.  They should handle v1 & v2 traps properly.

If you've configured the agent to not use the notification table,
then I'm less surprised at the behaviour you're seeing.


> I am unsure of the best approach to work around this.
> I am using version 5.0.9

Upgrade to 5.1 :-)
We've re-coded the trap generation routines, so that they do
now translate between v1 and v2-style traps properly (in *both*
directions).   So things should Just Work as I explained previously.

   I'd actually forgotten that this wasn't part of the 5.0.x line
(and that the earlier sink-only handling had this broken behaviour).
Sorry about that.

Dave



-------------------------------------------------------
This SF.net email is sponsored by: The SF.net Donation Program.
Do you like what SourceForge.net is doing for the Open
Source Community?  Make a contribution, and help us add new
features and functionality. Click here: http://sourceforge.net/donate/


<Prev in Thread] Current Thread [Next in Thread>