Does the ACK clear from the network properly when connectivity is restored?
________________________________
From: nv-l-bounces AT lists.ca.ibm DOT com on behalf of Leslie Clark
Sent: Tue 3/27/2007 11:34 AM
To: Tivoli NetView Discussions
Subject: Re: [NV-L] Acknowledging UNREACHABLE interfaces
That's how it works, in my experience. I usually ack the network.
Cordially,
Leslie A. Clark
IT Services Specialist, Network Mgmt
Information Technology Services Americas
IBM Global Services
(248) 552-4968 Voicemail, Fax, Pager
"Rob Rinear" <rob.rinear AT engyro DOT com>
Sent by: nv-l-bounces AT lists.ca.ibm DOT com
03/27/2007 11:09 AM
Please respond to
Tivoli NetView Discussions <nv-l AT lists.ca.ibm DOT com>
To
<nv-l AT lists.ca.ibm DOT com>
cc
Subject
[NV-L] Acknowledging UNREACHABLE interfaces
I am running Netview for Windows 7.1.5 and, when a router goes Unreachable,
acknowledging the interfaces does not propagate up. The node and networks
remain white. This only happens for unreachable; acknowledging down interfaces
on a marginal router/node will propagate as expected.
I found hits regarding the variable OVW_NO_UNREACHABLE_PROPAGATION, but that
seems to control the propagation of unreachable, not the ACK, and the related
APAR states the variable has no effect when all interfaces are unreachable,
anyway.
One workaround is to ACK the node, also, be we have had occasions where the
node ACK does not clear when the interfaces do, and it remains dark green event
though it is completely up.
Can anyone confirm similar behavior and offer any better solution?
Thanks,
Rob _______________________________________________
NV-L mailing list
NV-L AT lists.ca.ibm DOT com
Unsubscribe:NV-L-leave AT lists.ca.ibm DOT com
http://lists.ca.ibm.com/mailman/listinfo/nv-l (Browser access limited to
internal IBM'ers only)
<<winmail.dat>> _______________________________________________
NV-L mailing list
NV-L AT lists.ca.ibm DOT com
Unsubscribe:NV-L-leave AT lists.ca.ibm DOT com
http://lists.ca.ibm.com/mailman/listinfo/nv-l (Browser access limited to
internal IBM'ers only)
|