From: Ayman Hamza (ayhamza@cisco.com)
Date: Thu Oct 03 2002 - 16:28:21 GMT-3
Very good question . You are right in yur guess. When the verify timer expires
and the entry is stale, then any new test frame will be sent as explorer
request to the peer that we have its related entry stall. Only after
the entry is deleted, -i.e. the cahe-timeout expires - then the exploere
frames can be sent to all the peers.
So what you have said is correct.
Regards;
Ayman
> From nobody@groupstudy.com Thu Oct 3 20:52:09 2002
> Date: Thu, 3 Oct 2002 20:38:27 +0200 (CEST)
> From: =?iso-8859-1?q?giuseppe=20ciferri?= <joscite@yahoo.it>
> Subject: Re: dlsw+ timers and caching
> To: ccielab@groupstudy.com
> MIME-Version: 1.0
> Content-Transfer-Encoding: 7bit
> X-ASK-Info: Whitelist match
> Sender: nobody@groupstudy.com
> Reply-To: =?iso-8859-1?q?giuseppe=20ciferri?= <joscite@yahoo.it>
>
> Thanks Ayman, you are very clear. I have another
> question:
> In dlsw+ case with load balance (fault tollerant mode)
> with cost selection (1 peer with dlsw local cost 2 and
> other cost 4):
>
> when preferred peer went down the capable peer makes
> preferred, but if the previous-preferred peer come up
> when the remote-peer re-selects this peer ?
> I suppose after sna-cache timeout...
>
> thanks
> Giuseppe
>
> ______________________________________________________________________
> Mio Yahoo!: personalizza Yahoo! come piace a te
> http://it.yahoo.com/mail_it/foot/?http://it.my.yahoo.com/
This archive was generated by hypermail 2.1.4 : Tue Nov 05 2002 - 08:35:38 GMT-3