nv-l
[Top] [All Lists]

AW: working with Collections

To: nv-l@lists.tivoli.com
Subject: AW: working with Collections
From: Schiffinger Ralph 2100 <Ralph.Schiffinger@ERSTEBANK.AT>
Date: Wed, 9 Feb 2000 11:55:20 +0100
Dietmar,

You unmanage a node and all it's interfaces become unmanaged.
You unmanage the node's only interface and the node becomes unknown (blue).

You ack a node and all it's critical interfaces stay critical, this works as
designed.
You ack all critical interfaces and the status change is propagated upwards,
i.e. the node becomes lime green (or whatever colour you have in .Xdefaults,
I prefer magenta).

What I am missing since NetView 4.1 is a
"one-click-automatic-drill-down-ACK-function",
i.e. You ack a node and all it's CRITICAL interfaces become ack-ed as well.

Running AIX 4.2, Netview 5.1.2, Framework 3.6

Cordially, Ralph.
iT-AUSTRIA / OE2100 / TK-NWM
Tel  (mobil)  0664 1908469
Tel  (iT-A)    21717 58948
FAX (iT-A)    21717 58979
Mailto:Ralph.Schiffinger@erstebank.at


> -----Ursprüngliche Nachricht-----
> Von:  Dietmar Gaulhofer [SMTP:dietmar_gaulhofer@AT.IBM.COM]
> Gesendet am:  Mittwoch, 09. Februar 2000 11:26
> An:   NV-L@UCSBVM.ucsb.edu
> Betreff:      working with Collections
> 
> Hi,
> 
> I have an situation which i would like to clear - i hope someone could
> help me
> on that. Env. is AIX 4.3.2 and Netview 5.1.2.
> 
> If i unmanage or ack. an Node in an Collection - is then this change also
> happening on the Interface level ? A Customer
> has a problem that very often the Interface keeps managed.  I have the
> same
> behavior on an Testinstallation of V 6 that
> if i ack. an Critical node in an specific Collection the Interface is
> still in
> status Critical....
> 
> Is this works as designed ? anyone have/had the same problem ?
> 
> Thanks for any help,
> 
> Kr, Dietmar


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

Archive operated by Skills 1st Ltd

See also: The NetView Web