Re: DR election
kamatchi soundaram <kamatchi@TDD.SJ.NEC.COM> Tue, 13 May 2003 17:37 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 NAA21543 for <ospf-archive@LISTS.IETF.ORG>; Tue, 13 May 2003 13:37:59 -0400 (EDT)
Received: from walnut (209.119.0.61) by cherry.ease.lsoft.com (LSMTP for Digital Unix v1.1b) with SMTP id <2.009BE742@cherry.ease.lsoft.com>; Tue, 13 May 2003 13:40:59 -0400
Received: from DISCUSS.MICROSOFT.COM by DISCUSS.MICROSOFT.COM (LISTSERV-TCP/IP release 1.8e) with spool id 666635 for OSPF@DISCUSS.MICROSOFT.COM; Tue, 13 May 2003 13:40:59 -0400
Received: from 131.241.15.4 by WALNUT.EASE.LSOFT.COM (SMTPL release 1.0i) with TCP; Tue, 13 May 2003 13:40:59 -0400
Received: from netkeeper.sj.nec.com (netkeeper.sj.nec.com [131.241.31.2]) by mail4.nec.com (/) with ESMTP id h4DHevoX010713 for <OSPF@discuss.microsoft.com>; Tue, 13 May 2003 10:40:57 -0700 (PDT)
Received: from necsun.tdd.sj.nec.com (localhost [127.0.0.1]) by netkeeper.sj.nec.com (/) with ESMTP id h4DHepmR023972 for <OSPF@discuss.microsoft.com>; Tue, 13 May 2003 10:40:51 -0700 (PDT)
Received: from bunny.tdd.sj.nec.com (bunny.tdd.sj.nec.com [131.241.9.33]) by necsun.tdd.sj.nec.com (8.12.8/8.12.8) with ESMTP id h4DHULsC024362 for <OSPF@discuss.microsoft.com>; Tue, 13 May 2003 10:30:21 -0700 (PDT)
Received: from ems12 (ems12 [131.241.5.17]) by bunny.tdd.sj.nec.com with SMTP id h4DHUJYS024772 for <OSPF@discuss.microsoft.com>; Tue, 13 May 2003 10:30:19 -0700 (PDT)
References: <AAB4B3D3CF0F454F98272CBE187FDE2F02BD9BD5@is0004avexu1.global.avaya.com> <3EC0F2E5.5020507@redback.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 5.50.4133.2400
X-MIMEOLE: Produced By Microsoft MimeOLE V5.50.4133.2400
Message-ID: <163601c31977$c0b2c5d0$1105f183@b90.tdd.sj.nec.com>
Date: Tue, 13 May 2003 10:47:41 -0700
Reply-To: Mailing List <OSPF@DISCUSS.MICROSOFT.COM>
Sender: Mailing List <OSPF@DISCUSS.MICROSOFT.COM>
From: kamatchi soundaram <kamatchi@TDD.SJ.NEC.COM>
Subject: Re: DR election
To: OSPF@DISCUSS.MICROSOFT.COM
Precedence: list
Content-Transfer-Encoding: 7bit
Yes! i did see that happened. You can easily simulate this condition. Connect R1, R2 and R3 to the Network first. In that R3 will become DR and R2 will Become BDR. Meantime, start R4 separately (mean, don't hook-up the R4 Lan cable to the network.). In that case, since R4 didn't see anyother router in the network, it will become as DR. Then when you put the R4 also into the network, R4 will become the DR and R2 remained as BDR. Well! i had seen this scenario in my network. GKS. ----- Original Message ----- From: "Acee Lindem" <acee@redback.com> To: <OSPF@discuss.microsoft.com> Sent: Tuesday, May 13, 2003 6:28 AM Subject: Re: DR election > 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 >
- DR election Dror
- Re: DR election Igor Miroshnik
- Re: DR election Russ White
- Re: DR election Zebaida, Dror (Dror)
- Re: DR election Acee Lindem
- Re: DR election Phil Chen
- Re: DR election Zebaida, Dror (Dror)
- Re: DR election Vivek Dubey
- Re: DR election Michael J Barnes
- Re: DR election kamatchi soundaram
- Re: DR election kamatchi soundaram
- DR election Ilan Bercovich
- Re: DR election Krishnan, Vijay G.
- Re: DR election Erblichs
- Re: DR election Naresh Paliwal
- Re: DR election Acee Lindem
- Re: DR election Erblichs
- A writeup on interface state machine (Re: DR elec… Mukul Goyal
- Re: DR election Acee Lindem
- Re: A writeup on interface state machine (Re: DR … Filippo Cugini