Re: active monitoring behavior

On 09/10/2007, Chris Liles <[email protected]> wrote:
> Does anyone know if it is possible to change the behavior of the agent so
> that it will send a new trap even is the ErrorFlag has not changed?

The simplest would probably be to tweak the code that implements
the DisMan monitoring.

Take a look at the file 'agent/mibgroup/disman/event/mteTrigger.c',
and the routine 'mteTrigger_run()'.

This is a fairly long stretch of code :-),  but if you search for the token
MTE_ARMED_BOOLEAN, you should find a line:

       vp1->index &= ~MTE_ARMED_BOOLEAN;

(around line 855).   Comment this line out, and recompile.

If you want the same behaviour for threshold-based tests,
then comment out the two lines:

      cmp &= ~MTE_ARMED_TH_RISE;    (line 952)
and
      cmp &= ~MTE_ARMED_TH_FALL;    (line 981)
as well.

That should provide the behaviour that you are looking for.


>  I would guess that this is a "feature" to prevent spamming of
> the snmp trap receiver,

Sort of - it's the behaviour required by the DisMan Event MIB
specification.   See the description of the object mteTriggerTest
(third para).

Dave

-------------------------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems?  Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now >> http://get.splunk.com/
_______________________________________________
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