> From: nf-vale [mailto:nf-v...@critical-links.com] > Sent: Wednesday, January 06, 2010 2:59 PM
> The problem I'm facing is that I only receive one trap (either trapsink, > trap2sink or informsink work the same) if I restart the snmpd agent (I > suppose > that if I would force the available disk space to set the dskErrorFlag > from > "noerror" to "error" this would work as well, as expected). > > So my doubt here is: is this the correct behaviour, or should it send > one trap > for each verification cycle, even if the error flag did not change > between the > verifications (dskErrorFlag = 1)? It should send the trap only for the state change from under to over threshold. This is desireable to prevent trap flooding during major problem times (power outage, etc.). Since traps can be lost, you should supplement the disman monitoring with MIB polling. HTH, Mike ------------------------------------------------------------------------------ This SF.Net email is sponsored by the Verizon Developer Community Take advantage of Verizon's best-in-class app development support A streamlined, 14 day to market process makes app distribution fast and easy Join now and get one step closer to millions of Verizon customers http://p.sf.net/sfu/verizon-dev2dev _______________________________________________ Net-snmp-users mailing list Net-snmp-users@lists.sourceforge.net Please see the following page to unsubscribe or change other options: https://lists.sourceforge.net/lists/listinfo/net-snmp-users