This is a discussion on Re: Disman Traps within the SNMP Coders forums, part of the Networking and Network Related category; On Thu, 2005-12-15 at 11:36 -0200, Wesley Naves de Faria wrote: > I added prErrorFlag == 0 but ...
|
|||||||
| FAQ | Members List | Calendar | Search | Today's Posts | Mark Forums Read |
|
|||
|
On Thu, 2005-12-15 at 11:36 -0200, Wesley Naves de Faria wrote:
> I added prErrorFlag == 0 but i got some problems. The snmp > always will send trap saying that process is up, But isn't that what you were asking for? One trap when the 'proc' entry detects a problem, and another trap when this problem disappears? That should be what a pair of monitor ... prErrorFlag == 0 monitor ... prErrorFlag != 0 directives provides. (And I've tested this with the 5.3 pre-release code, so I'm confident that it works properly). > 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. That's the third option I suggested. > How do you think that i can do this ? monitor ..... != prErrorFlag > Is it possible to add > this change in the original code of mteTriggerTable.c ? No. This form of expression relies on the re-written Event MIB implementation, that is being introduced with 5.3. There's a release candidate tarball on the project web site. Try using that. 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 |