The "Node Down" event gets generated based upon your polling configuration
settings in the "SNMP Configuration".  If a particular INTERFACE is
unreachable, taking into account the configured timeouts and retries in
"SNMP Configuration", an "Interface down" message is generated.  If ALL of
the interfaces on the particular device become unreachable, a "Node down"
event is generated.  You can not change this logic - it is part of the
"netmon" daemon.  However, you can create a rule that executes a particular
action if a corresponding "Node up" is not generated for the particular node
within a give time period.  We have created such a rule in our environment
to execute an auto. paging script if the node is "down" (i.e., unreachable
via ping) for 15 minutes, where our polling is configured to every 5
minutes.

Joe Prokott
Network Architect
West Group
St. Paul, MN  55123
e-mail: joe.prokott AT westgroup DOT com

-----Original Message-----
From: Mark van Kerkwyk [mailto:kerkwyk AT COMTECH.COM DOT AU]
Sent: Wednesday, February 10, 1999 8:13 PM
To: NV-L AT UCSBVM.UCSB DOT EDU
Subject: How can I threshold Node_Down events ?


Hi ,
     I must have surely missed something here , but I cannot work out how
to tell Netview not to send Node_Down events until a threshold (time) has
been met.
My customer wants Netview to only send a Node_Down alert when the node has
node responded to 2 or 3 ping attempts.
Since there is only on Node_Down event generated, I can't use a ruleset to
correlate the events together and seta threshold.

Anyone know of a simply way to do this ?

Mark :-)