Leslie,
Thanks for the reply. A little background on how we use Acking.
We have a "Container Icon" representing multiple nodes (where each node has
one network interface). We use Compound Propigation to move statuses up the
tree. Our situation is a node will turn yellow, the yellow status will
propigate to the Container Icon yellow. Our operators will Ack the
Container Icon (not the node that changes color). If the node changes red,
we would like the red status to be propigated up to the container icon,
removing the Acked status. We would like the same for red -> yellow
statuses also. We have found that the only time the Acked status will
change is when the node changes to OVwNormalStatus. This was confirmed by
reading that pasted section from the OVw app-default file. If I am
misunderstanding something, please let me know.
We are in the process of getting the 7.1 media to review it for our
customer. We are not as flexable as most with respect to change. Our
customer is internal, thus stubburn.
Can you point me in the direction of the Release notes that discuss this
functionality? I do know Global Acking was introduced in 6.01, but I have
not seen this reference.
Thanks again for the time you took in replying,
Jason Allison
Principal Engineer
ARINC Incorporated
Office: (410) 266-2006
FAX: (410) 573-3026
-----Original Message-----
From: Leslie Clark [mailto:lclark@us.ibm.com]
Sent: Tuesday, March 26, 2002 12:32 AM
To: Allison, Jason (JALLISON)
Subject: Re: [nv-l] Acknowledging paradigm
See my comments interspersed...
Cordially,
Leslie A. Clark
IBM Global Services - Systems Mgmt & Networking
Detroit
"Allison,
Jason To: "'nv-l'"
<nv-l@lists.tivoli.com>
(JALLISON)" cc:
<JALLISON@arin Subject: [nv-l] Acknowledging
paradigm
c.com>
03/25/02 04:28
PM
List:
We use Ack/Unack to maintain known problems and keep top level statuses in
sync.
I just read this is /usr/OV/app-defaults/OVw
!********************************************************************
!
! If the *overrideAcknowledge resource is set to False, when
! an Acknowledged node comes up (changes to ovwNormalStatus), the
! Acknowledged status will *not* be replaced with the
! ovwNormalStatus. The node will remain Acknowledged.
!
! If the *overrideAcknowledge resource is set to True, then if
! an Acknowledged node comes up (changes to ovwNormalStatus), then
! the Acknowledged status will be replaced with ovwNormalStatus.
!
! In other words, if you want Acknowledged nodes to have their
! Acknowledged status turned off when they come back up, set the
! resource to True.
!
!********************************************************************
*overrideAcknowledge: True
My questions are:
1. Does this mean the only time the Acknowledged status will be removed
automatically (by Netview), will be when the Object status is set to
OVwNormalStatus?
>> Yes, that is the default behavior. The option to have the Ack stay
>> until you clear it was added, probably at the request of a customer,
>> a long time ago, but it is not used much in my experience. IMPORTANT
>> NOTE: The intent here was that you would acknowledge at the interface
>> level. That way propogation works all the way up to the top, making
>> the map green. Interfaces are either up or down, so by the default
>> setting, once they come up again, the Ack is cleared. If you are
>> Acking at the node level, and some of the interfaces come up but
>> not all, the Ack on the node (I think) will probably NOT clear.
2. Is there a way to configure Netview (OVw) so that -any time- there is a
status change for an object, the Acknowledged tag is removed?
>> That is the default behavior if you do your Acking at the inteface
>> level. This is a training issue with operators, usually.
3. If I know the Object, can I manually (programmatically) set the objects
status to 'Unacknowledged'?
>> Yes you can. This. This ability was introduced in 6.0.1 and is
>> documented in the release notes. I see it is also covered in the
>> 7.1 release notes.
>> Another comment: Some people hesitate to Ack at the interface level
>> because the green node looks the same as a regular normal node.
>> However, the IP Status of the node is still 'Marginal' or 'Critical',
>> and the interface is still 'Critical', so they can still be shown
>> in Smartsets. I use a smartset of ProblemNodes and also one of
>> ProblemInterfaces. It is easy to see there which ones are Ack'd.
Thanks in advance,
Jason Allison
Principal Engineer
ARINC Incorporated
Office: (410) 266-2006
FAX: (410) 573-3026
---------------------------------------------------------------------
To unsubscribe, e-mail: nv-l-unsubscribe@lists.tivoli.com
For additional commands, e-mail: nv-l-help@lists.tivoli.com
*NOTE*
This is not an Offical Tivoli Support forum. If you need immediate
assistance from Tivoli please call the IBM Tivoli Software Group
help line at 1-800-TIVOLI8(848-6548)
|