nv-l
[Top] [All Lists]

Re: Cutting down on node down events

To: nv-l@lists.tivoli.com
Subject: Re: Cutting down on node down events
From: Vladimir Petr <petr@DATASYS.CZ>
Date: Fri, 18 Dec 1998 09:06:17 +0100
Organization: DATASYS
Reply-to: Discussion of IBM NetView and POLYCENTER Manager on NetView <NV-L@UCSBVM.UCSB.EDU>
Sender: Discussion of IBM NetView and POLYCENTER Manager on NetView <NV-L@UCSBVM.UCSB.EDU>
Hello, J.P.;

I think one way to achieve your goal would be letting ovactiond run an action 
upon receiving the
node down event/trap. The action would be running a script that checks the 
timestamp contained
within the event ($T or varbind 4) or the time on the NV box, the reception 
time (this might be a
little bit simpler). If it is not between the time limits you set then it will 
page your guys.
Otherwise, it will not.

You can do this for any node down event or you can copy that and create a new 
one running this
action only when the event is received from your critical nodes (Source).

Also, you can create a ruleset that do the same.

Hope this helps,
Best regards,
Vladimir.


"Giuliotti, J. P." wrote:
>
> Hello Group,
>
> I have a couple of critical nodes that are shut down nightly as part of
> a
> backup procedure. How do I insure that Netview will not try to discover
> these nodes in that time frame so we are not paged between 11pm and 3AM
> every night? Is there a standard way of handling this situation?
> Thanks,
> J.P. Giuliotti  - Massachusetts Financial Services
> (617) 954-5684
> JPG@MFS.COM

--
Vladimir Petr
DATASYS
-----------------------------

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

Archive operated by Skills 1st Ltd

See also: The NetView Web