> From: Mohan M [mailto:[EMAIL PROTECTED]
> Sent: Wednesday, September 10, 2008 5:09 PM
> Good news that I am getting automatic traps from
> DISMAN/events for the below events
>
> a) When disk usage exceeds the % configured
> b) When the link is brought down
> c) When the configured process is stopped &
> d) The usual cold stop/start traps
>
> The problem is that this trap is sent to the waiting
> snmptrapd daemon only when the snmpd daemon is restarted. I
> get a flud of these traps when I restart the snmpd process.
That is expected behavior, including the fact that it may assert and
reset alarms more than once during startup, so don't react to them immediately
- wait until they've been up for awhile (you'll need to tune the value of
"awhile").
> Otherwise however long I wait (> 25 minutes) I dont get any
> traps even when I stop the httpd process many times and wait
> for the trap?
> Can you let me know what could be wrong!!
Dude....
[SNIP manpage="snmp.conf" section="proc"]
Note: This situation will not automatically trigger a trap to
report the problem - see the DisMan Event MIB section
later.
[/SNIP]
Congrats on getting this far, tho'.
Mike
-------------------------------------------------------------------------
This SF.Net email is sponsored by the Moblin Your Move Developer's challenge
Build the coolest Linux based applications with Moblin SDK & win great prizes
Grand prize is a trip for two to an Open Source event anywhere in the world
http://moblin-contest.org/redirect.php?banner_id=100&url=/
_______________________________________________
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
