nv-l

Re: Acknowledging

2002-01-08 13:03:30
Subject: Re: Acknowledging
From: William.Stringfellow AT bankofamerica DOT com
To: nv-l AT lists.tivoli DOT com
Date: Tue, 08 Jan 2002 10:03:30 -0800

Allison,
     Our experience is that acknowledging containers is bad.  There is a bug
where the isAcknowledged variable is not reset to "FALSE" when the container
comes back to a normal status.  This only occurs on non-interface objects.
     The problem is, that if the object comes back to normal, then later has
a problem, the object will still be in the acknowledged state, so your
operators will not get the indications they expect, ie Red or Yellow status.
     The fix is to only acknowledge interfaces, these do get the variable
reset as expected and will always show you the correct current status.
     There is an APAR open to fix this, IY24273, and it will show up in the
next patch to the system.

          Regards,
          Bill

**************************     ORIGINAL MESSAGE
**************************************


From: Allison, Jason (JALLISON) [mailto:JALLISON AT arinc DOT com]
Sent: Tuesday, November 27, 2001 1:34 PM
To: 'nv-l AT tkg DOT com'
Subject: [NV-L] Acknowledging


AIX 4.3.3 - Netview 5.1.3

We are now instructing our operators to acknowledge container symbols when
there is a failure that is known.  This works fine when we have one instance
of 'netview' running.  Acknowledging works as expected.  We have come across
some problems when bringing up another instance of 'netview' (TME10 GUI).


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