Re: Disman Traps

I added prErrorFlag == 0 but i got some problems. The snmp always will send
trap saying that process is up, so i think that i need to implemant any
thing that keep the last state of process and send a trap just when this
state change. How do you think that i can do this ? Is it possible to add
this change in the original code of mteTriggerTable.c ?

-------------
Wesley Naves de Faria
Analista de suporte
FreeBSD/OpenBSD/Linux
AGANP - Agência Goiana de Administração Negócios Públicos
Contato: +55 (0XX62) 201-6582


----- Original Message -----
From: "Dave Shield" <D.T.Shield@csc.liv.ac.uk>
To: "Wesley Naves de Faria" <wesley.faria@aganp.go.gov.br>
Cc: <net-snmp-coders@lists.sourceforge.net>
Sent: Thursday, December 15, 2005 10:56 AM
Subject: Re: Disman Traps


> On Thu, 2005-12-15 at 10:28 -0200, Wesley Naves de Faria wrote:
> > When I implementation a var proc in snmpd.conf ( proc httpd ),
> > the snmpd send a trap if the process stop to run, but when the
> > process go back to run, the snmpd not send a trap.
>
> That's not strictly the realm of the DisMan Event MIB - at least
> not directly. Boolean monitor triggers are defined to fire when
> the monitored expression becomes true - not when it becomes false.
>
> The monitor entry doesn't actually care what the expression is
> looking at - just whether it evaluates to true or false.
>
>
> > I need receive trap when the service stop to run and when
> > the service go back to run.
>
> One option would be to define *two* monitor entries - one
> watching for 'prErrorFlag != 0' (as with the default monitoring),
> and a complementary one watching for 'prErrorFlag == 0'.
>
> Alternatively, you could try setting up a threshold monitor
> on prErrorFlag, with both the upper and lower thresholds set
> to 0. (Or both set to 1). I think that should have the
> same effect, though I haven't tried it.
>
> Or you could set up an existance "changed" monitor on prErrorFlag,
> which would fire whenever the value changed. That's only available
> with the new 5.3 'disman/event' implementation (rather than the
> previous 'disman/event-mib' version). Though I haven't tried that
> one either.
>
>
> Bottom line - the DisMan Event MIB *can* provide the behaviour
> you are looking for, but you'll have to configure this yourself.
> That's something we could perhaps look at for a future release,
> but now is not the time to make such changes!
>
> Dave
>
>
>
> -------------------------------------------------------
> This SF.net email is sponsored by: Splunk Inc. Do you grep through log
files
> for problems? Stop! Download the new AJAX search engine that makes
> searching your log files as easy as surfing the web. DOWNLOAD SPLUNK!
> http://ads.osdn.com/?ad_id=7637&alloc_id=16865&op=click
> _______________________________________________
> Net-snmp-coders mailing list
> Net-snmp-coders@lists.sourceforge.net
> https://lists.sourceforge.net/lists/...et-snmp-coders
>
>



-------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc. Do you grep through log files
for problems? Stop! Download the new AJAX search engine that makes
searching your log files as easy as surfing the web. DOWNLOAD SPLUNK!
http://ads.osdn.com/?ad_id=7637&alloc_id=16865&op=click
_______________________________________________
Net-snmp-coders mailing list
Net-snmp-coders@lists.sourceforge.net
https://lists.sourceforge.net/lists/...et-snmp-coders