Re: DISMAN Event MIB configuration: monitor

2009-12-01 Thread Dave Shield
2009/12/1 Sam V : > Is there another patch for existence triggers? > startup condition would be present, absence, or both. Hmmm... that's going to be harder. The parsing of the "monitor" directive currently treats the existence tests as an enumeration, rather than as three independent bits. And

RE: DISMAN Event MIB configuration: monitor

2009-12-01 Thread Sam V
Thanks Dave for your reply. I'll try to see if this would work. Now, is there another patch for existence triggers? startup condition would be present, absence, or both. > Date: Tue, 1 Dec 2009 08:51:41 + > Subject: Re: DISMAN Event MIB configuration: monitor >

Re: DISMAN Event MIB configuration: monitor

2009-12-01 Thread Dave Shield
2009/11/30 Sam V : > Now, in case of a threshold > trigger > which have multiple startup cases, Raising, Falling, RisingAndFalling. How > can specify that I want a startup condition to be true on for the rising case > and not all cases? In term of conf

Re: DISMAN Event MIB configuration: monitor

2009-11-30 Thread Alex Tarumian
Hi, Disman is evaluating the condition (see for details snmpd.conf man page) every interval defined there and sends a trap first time the condition is met (as opposed to first time it is evaluated). Next trap will be sent only if condition becomes FALSE and then TRUE again. That is the base for pro

DISMAN Event MIB configuration: monitor

2009-11-30 Thread Sam V
Hi Guys, I have a question about the syntax used to configure the disman event MIB in snmpd.conf. Specifically, startup condition in monitor keyword. I noticed there is an option -s to evaluate trigger on startup, and there is option -S not to evaluate the trigger on startup. Now, in case of