Re: Is it net-snmp's bug

On Sun, 04 Sep 2005 17:37:20 +0800 李晓栋 wrote:
> monitor -u trap -r 120 -o .1.3.6.1.2.1.2.2.1.2
> "packet" .1.3.6.1.2.1.2.2.1.11 > 1 monitor -u trap -r 120
> -o .1.3.6.1.2.1.2.2.1.2 "traffic" 1.3.6.1.2.1.2.2.1.10 > 1
> 
>  As You can see ,the record of trap of
> 17:04,17:06,17:08,17:10,17:12,17:16.... is not in the log file.

I think that you don't understand how the monitors works. It will not send a
trap every time the condition tests true. It will send a trap the first time
the condition tests true, and then will suppress future traps until the
condition is false. Then, on the next transition to true, it will send a
single trap again.

It probably wouldn't be too hard to add functionality to send the trap every
time, and add a flag to the conf file to enable such behavior. Patches
welcomed, or you could submit a feature request.

-- 
NOTE: messages sent directly to me, instead of the lists, will be deleted
      unless they are requests for paid consulting services.

Robert Story; NET-SNMP Junkie
Support: <http://www.net-snmp.org/> <irc://irc.freenode.net/#net-snmp>  
Archive: <http://sourceforge.net/mailarchive/forum.php?forum=net-snmp-users>

You are lost in a twisty maze of little standards, all different. 


-------------------------------------------------------
SF.Net email is Sponsored by the Better Software Conference & EXPO
September 19-22, 2005 * San Francisco, CA * Development Lifecycle Practices
Agile & Plan-Driven Development * Managing Projects & Teams * Testing & QA
Security * Process Improvement & Measurement * http://www.sqe.com/bsce5sf
_______________________________________________
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