You might look at running an external script as an action in your rule to
do some additional processing for verification.  For the 'up', you could
use cron to do an external ping from information logged on the 'down'
script or from trapd.log.

Peace,
Blane Robertson
IT - ESM
CenterPoint Energy, Inc.
713.207.2002

If God is for us, who can be against us?  Rom. 8:31b

To ignore the facts does not change that they are the facts. - Andy Rooney

Whether you think you can, or think you can't, you're right. - Henry Ford

*******************************************************

Date: Tue, 21 Sep 2004 12:06:10 -0500
From: "Freeman, Michael" <mfreeman AT netcogov DOT com>
Subject: RE: [nv-l] question about modifying objects in netview 7.1.3

This is a multi-part message in MIME format.

- ------_=_NextPart_001_01C49FFD.4ABCCDEA
Content-Type: text/plain;
             charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

Our environment is made up with Cisco routers, switches, and what have you.
Yes it is a possibility to tune the timeout/retry information, but we are
running a large network and we cannot rely on the operators to take care of
that. In some geo's in our network we have unreliable devices or we have
NetView telling us that Node's are down when they really aren't, and we are
just trying to add some extra verification before we take that data and put
it into our SLA database.

We're just using Tivoli NetView 7.1.3 and have no options to purchase or
leverage other solutions, other than ones we can come up with on our own
using opensource software or our inhouse development team.