|Subject:||RE: [nv-l] Different behavior for Acknowledge with ITSL.|
|From:||"Evans, Bill" <Bill.Evans@hq.doe.gov>|
|Date:||Tue, 17 May 2005 09:34:01 -0400|
|Delivery-date:||Tue, 17 May 2005 14:35:07 +0100|
Thank you, Leslie. We missed the normal migration path so I never saw 7.1.4 FP2 or ITSA 1.2.1. There was nothing in the list archives either.
There must be some propagation involved since the sequence I described propagates the normal-acknowledged combination as normal and resets the pre-existing acknowledged state I set.
I've seen this same behavior on some other strange combinations of status propagation on subnet submaps not involving Layer2. I didn't realize how to cope with it until after last evening's posting. I'll have a marginal state on a router with a combination of normal and acknowledged interfaces. Setting the router to ack, opening the submap, unacking the interfaces then acking them again will reset the router icon one submap up to normal. (I'm getting tired of typing "acknowledged".) I'll have to try the unack-ack combination on the specific interface for the submap instant to see if it is sufficient.
Now that I know how it works and why It is easier to understand. The problem I was having was node symbol status on maps other than the submap nodes not behaving the same as on the submaps.
|<Prev in Thread]||Current Thread||[Next in Thread>|
|Previous by Date:||Re: [nv-l] update process for MIB´s , James Shanks|
|Next by Date:||[nv-l] External Authentication Module - Netview Web Clients, Shipley, Rob|
|Previous by Thread:||Re: [nv-l] Different behavior for Acknowledge with ITSL., Leslie Clark|
|Next by Thread:||[nv-l] update process for MIB´s , Mildeberger, Thorsten|
|Indexes:||[Date] [Thread] [Top] [All Lists]|
Archive operated by Skills 1st Ltd
See also: The NetView Web