nv-l
[Top] [All Lists]

Re: Netview "autosupervision"

To: nv-l@lists.tivoli.com
Subject: Re: Netview "autosupervision"
From: Tim Clark <Tim.Clark@TAVVE.COM>
Date: Fri, 16 Oct 1998 09:36:35 -0400
Reply-to: Tim Clark <Tim.Clark@tavve.com>
Sender: Discussion of IBM NetView and POLYCENTER Manager on NetView <NV-L@UCSBVM.UCSB.EDU>
We fix this problem by creating an hourly entry to restart the daemons.  We
don't address the part of sending notification that a daemon died (although
that's a great idea). you want it we'll build it....
www.tavve.com


-----Original Message-----
From: Luc BARNOUIN AIRSYS-ATM SSD/TCE-TAP
<Luc.L.B.BARNOUIN@FR.AIRSYSATM.THOMSON-CSF.COM>
To: NV-L@UCSBVM.UCSB.EDU <NV-L@UCSBVM.UCSB.EDU>
Date: Friday, October 16, 1998 7:36 AM
Subject: Netview "autosupervision"


>Hi everybody,
>
>I am currently running TME10 Netview 4.1E for Digital Unix (but intend to
migrate to TME10 NV5.1 for Digital Unix as soon as available). One of our
needs is to detect any Netview internal deamons failure, and either warn the
operator for manual action (ovstatus, ovstop/ovstart) or perform some
automatic action (stop/restart the failed deamon, stop/restart NV, reboot
the computer, ...).
>Is there any mechanism within ovspmd to implement such a facility? Has
anyone already tryied to perform some kind of "autosupervision" of Netview
and associated applications (we have developped our own WELL_BEHAVED
deamons, interfaced with gtm APIs, to manage a specific topology)?
>
>Thanks for any solution or investigation tracks.
>
>Luc Barnouin
>Airsys ATM
>

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

Archive operated by Skills 1st Ltd

See also: The NetView Web