Re: DR election

Acee Lindem <acee@REDBACK.COM> Tue, 13 May 2003 13:25 UTC

Received: from cherry.ease.lsoft.com (cherry.ease.lsoft.com [209.119.0.109]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA11193 for <ospf-archive@LISTS.IETF.ORG>; Tue, 13 May 2003 09:25:06 -0400 (EDT)
Received: from walnut (209.119.0.61) by cherry.ease.lsoft.com (LSMTP for Digital Unix v1.1b) with SMTP id <13.009BDFD1@cherry.ease.lsoft.com>; Tue, 13 May 2003 9:28:07 -0400
Received: from DISCUSS.MICROSOFT.COM by DISCUSS.MICROSOFT.COM (LISTSERV-TCP/IP release 1.8e) with spool id 665984 for OSPF@DISCUSS.MICROSOFT.COM; Tue, 13 May 2003 09:28:07 -0400
Received: from 155.53.12.9 by WALNUT.EASE.LSOFT.COM (SMTPL release 1.0i) with TCP; Tue, 13 May 2003 09:28:06 -0400
Received: from redback.com (login003.redback.com [155.53.12.55]) by prattle.redback.com (Postfix) with ESMTP id A35A085BD80 for <OSPF@DISCUSS.MICROSOFT.COM>; Tue, 13 May 2003 06:28:05 -0700 (PDT)
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.0.2) Gecko/20030208 Netscape/7.02
X-Accept-Language: en-us, en
MIME-Version: 1.0
References: <AAB4B3D3CF0F454F98272CBE187FDE2F02BD9BD5@is0004avexu1.global.avaya.com>
Content-Type: text/plain; charset="us-ascii"; format="flowed"
Content-Transfer-Encoding: 7bit
Message-ID: <3EC0F2E5.5020507@redback.com>
Date: Tue, 13 May 2003 09:28:05 -0400
Reply-To: Mailing List <OSPF@DISCUSS.MICROSOFT.COM>
Sender: Mailing List <OSPF@DISCUSS.MICROSOFT.COM>
From: Acee Lindem <acee@REDBACK.COM>
Subject: Re: DR election
To: OSPF@DISCUSS.MICROSOFT.COM
Precedence: list
Content-Transfer-Encoding: 7bit

Hi Dror,

Zebaida, Dror (Dror) wrote:
> I understand that if there is already a DR/BDR then R4 will not become the DR.

As described succintly in Russ White's e-mail below.

> However, when an interface transitions out of the WAIT state, if it thinks it is
> alone on the network, it declares itself the DR.  If after that, it connects to the
> network, there are 2 routers declaring themselves DR. In our case R3 and R4.
> At this stage, is a new DR elected, or does R3 remain the DR.
>
> The scenario I am describing is R4 is conneced to the network after it transitioned
> out of the WAIT state (after 40 seconds)

This really should never happen on a broadcast or NBMA network unless you have
some type of connectivity or an NBMA configuration problem. I have seen it happen
on an NBMA network if the existing DR and BDR are using the RFC 2328 appendix C
suggested X.25 poll interval of 2 minutes and all the DR eligible neighbors are
not configured as eligible on all the DR eligible routers. When it happens a new
DR election will be triggered and R4 will become DR. I believe R2 will remain
as BDR.

Thanks,
Acee

>
> Thanks
>
>
>
> -----Original Message-----
> From: Russ White [mailto:ruwhite@CISCO.COM]
> Sent: Tuesday, May 13, 2003 2:56 PM
> To: OSPF@DISCUSS.MICROSOFT.COM
> Subject: Re: DR election
>
>
> As long as there is already a dr on the link, R4 would not take over as the
> DR. Or it shouldn't. Think of it this way: The DR isn't elected first, the
> BDR is. Then the routers attached to the link "discover" there is no DR,
> and promote the BDR to DR, and elect a new BDR.
>
> :-)
>
> Russ
>
> On Tue, 13 May 2003, Dror wrote:
>
>
>>Hi,
>>
>>I have a question regarding a DR election algorithm.  If I have a netowrk
>>with 3 routers R1,-R3, each having the same priority and with router IDs
>>0.0.0.1, 0.0.0.2, 0.0.0.3 respectively.
>>
>>After a DR election process is done, R3 will be DR, R2 will be BDR and R1
>>will be DR-Other.  This is the result of the DR election process since R3
>>has the largest router ID.
>>
>>If I add a new router R4 with router ID 0.0.0.4, do I expect R4 to become
>>the DR, or does it just become another DR-other since there is already a DR
>>in the network.
>>
>>Does the result depend on whether R4 is connected to the network when it is
>>still in the WAIT state, or the result is the same nevertheless.
>>
>>Thanks
>>Dror
>>
>
>
> __________________________________
> riw@cisco.com CCIE <>< Grace Alone
>


--
Acee