nv-l

"HeartBeat" Event to Monitor NV6K Alive Status

1998-06-01 16:49:43
Subject: "HeartBeat" Event to Monitor NV6K Alive Status
From: "Mull, John" <jmull AT HERSHEYS DOT COM>
To: nv-l AT lists.tivoli DOT com
Date: Mon, 1 Jun 1998 16:49:43 -0400
Good Day Netview Admins.

We are running NV V4.1.2 on AIX platform.  We are running the secured
tecadapter to our TEC box (Solaris 2.5.1 TEC3.1).  Once events pass
through the TEC rulesbase, trouble tickets that are deemed critical or
fatal are passed to our Trouble Ticket System - ala..Remedy.

Here's the question.

We want to monitor the entire process from the Netview Box through the
adapter to TEC and onto Remedy.  Knowing that NV6K polls
the entire network, what do you need to do to ensure the NV6K box and
all the necessary processes are up themselves all the time.  Does NV6K
issue a trap or other events before the processes on the box crash?  We
have Tivoli Distributed Monitor installed on NV6K monitoring files
structures, and other processes.  But then if the oserv dies on this
box, we are out of luck for any of its monitors.  Our attempt here is
NOT to rely on Tivoli for all monitoring purposes.  Sort of a
contingency backup failover system to make sure our Enterprise Systems
Management boxes are healthy.

Our thinking here is creating a new event within NV6K EventConfiguration
panel which would fire every 30-60 minutes.  Using Tivoli
rulesbase we could have the event pass eventually to  Remedy where it
could handle filtering and deem the system is up.  If the event is
not received at Remedy by a certain point, then we can assume somewhere
in the process has experienced a failure.

Thanks for any tips anyone can offer that may have configured a similar
"HeartBeat" event to monitor the health of the entire process.
John Mull
Hershey Foods Corporation
Information Technology & Integration
Enterprise Systems Management
(717)534-7959
email:jmull AT hersheys DOT com

<Prev in Thread] Current Thread [Next in Thread>