Re: rfc: Disman Event MIB

Wes, et al.

I believe that I've basically finished the new Event-MIB implementation.
There are doubtless a few minor bugs to iron out - the "internal query"
GET mechanism seems to ignore anything other than the first varbind,
and there's an issue relating to duplicate trigger entries.
But in general, things seem to be working OK.

It would be useful if people could give this a whirl, and let me know
of any problems they encounter. If I don't hear of anything by early
next week, I'll switch the main development line over to use this by
default.



One other question has come to light:
When the current implementation sets up a "monitor" directive,
it doesn't appear to run the test immediately - even if the test
does actually hold true. Instead, it waits until the monitor
frequency has expired, and *then* sends the trap. In other words,
it behaves as if the 'mteTriggerBooleanStartup' flag was cleared
(although in fact this flag is set).

The new implementation takes proper notes of this flag, so would
generate the trap immediately. Should I retain the same visible
behaviour as the current code (i.e. have "monitor" default to
mteTriggerBooleanStartup = false), or keep the same MIB settings
as the current code (and have the behaviour change) ?

The new "monitor" directive includes an extra pair of options
(-s/-S) to explicitly set this either way - so the sysadmin can
always force a particular required behaviour. The only question
is what the defaults should be.

Thoughts?

Dave


-------------------------------------------------------
This SF.Net email is sponsored by:
Power Architecture Resource Center: Free content, downloads, discussions,
and more. http://solutions.newsforge.com/ibmarch.tmpl
_______________________________________________
Net-snmp-coders mailing list
Net-snmp-coders@lists.sourceforge.net
https://lists.sourceforge.net/lists/...et-snmp-coders