Neohapsis is currently accepting applications for employment. For more information, please visit our website www.neohapsis.com or email email@example.com
Re: DR election
From: kamatchi soundaram (kamatchiTDD.SJ.NEC.COM)
Date: Tue May 13 2003 - 12:47:41 CDT
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.
----- Original Message -----
From: "Acee Lindem" <aceeredback.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
> 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
> > 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
> > out of the WAIT state (after 40 seconds)
> This really should never happen on a broadcast or NBMA network unless you
> some type of connectivity or an NBMA configuration problem. I have seen it
> on an NBMA network if the existing DR and BDR are using the RFC 2328
> suggested X.25 poll interval of 2 minutes and all the DR eligible
> not configured as eligible on all the DR eligible routers. When it happens
> DR election will be triggered and R4 will become DR. I believe R2 will
> as BDR.
> > Thanks
> > -----Original Message-----
> > From: Russ White [mailto:ruwhiteCISCO.COM]
> > Sent: Tuesday, May 13, 2003 2:56 PM
> > To: OSPFDISCUSS.MICROSOFT.COM
> > Subject: Re: DR election
> > As long as there is already a dr on the link, R4 would not take over as
> > DR. Or it shouldn't. Think of it this way: The DR isn't elected first,
> > 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:
> >>I have a question regarding a DR election algorithm. If I have a
> >>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
> >>will be DR-Other. This is the result of the DR election process since
> >>has the largest router ID.
> >>If I add a new router R4 with router ID 0.0.0.4, do I expect R4 to
> >>the DR, or does it just become another DR-other since there is already a
> >>in the network.
> >>Does the result depend on whether R4 is connected to the network when it
> >>still in the WAIT state, or the result is the same nevertheless.
> > __________________________________
> > riwcisco.com CCIE <>< Grace Alone