Re: DR election
Naresh Paliwal <naresh.paliwal@NEVISNETWORKS.COM> Tue, 03 May 2005 11:51 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 HAA07434 for <ospf-archive@LISTS.IETF.ORG>; Tue, 3 May 2005 07:51:04 -0400 (EDT)
Received: from vms.dc.lsoft.com (209.119.0.2) by cherry.ease.lsoft.com (LSMTP for Digital Unix v1.1b) with SMTP id <11.01031413@cherry.ease.lsoft.com>; Tue, 3 May 2005 7:51:00 -0400
Received: by PEACH.EASE.LSOFT.COM (LISTSERV-TCP/IP release 14.3) with spool id 69098272 for OSPF@PEACH.EASE.LSOFT.COM; Tue, 3 May 2005 07:50:23 -0400
Received: from 220.225.34.211 by WALNUT.EASE.LSOFT.COM (SMTPL release 1.0l) with TCP; Tue, 3 May 2005 07:50:23 -0400
content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
X-MimeOLE: Produced By Microsoft Exchange V6.0.6603.0
Thread-Topic: DR election
Thread-Index: AcVPNgzq0MRhzGfTSreuUgYATWXcyQAn6dNw
Message-ID: <7F17177AC9AC2F4CB4A1A33C936D038D7E2275@nevismail01.pune.nevisnetworks.com>
Date: Tue, 03 May 2005 17:20:18 +0530
Reply-To: Mailing List <OSPF@PEACH.EASE.LSOFT.COM>
Sender: Mailing List <OSPF@PEACH.EASE.LSOFT.COM>
From: Naresh Paliwal <naresh.paliwal@NEVISNETWORKS.COM>
Subject: Re: DR election
To: OSPF@PEACH.EASE.LSOFT.COM
Precedence: list
Content-Transfer-Encoding: quoted-printable
Erblich, I didn't get your reply, can u please give the references of the idea. I mean to ask, is it possible to enforce DR/BDR-election without changing configuration of existing DR/BDR? Regards -Naresh -----Original Message----- From: Mailing List [mailto:OSPF@PEACH.EASE.LSOFT.COM] On Behalf Of Erblichs Sent: Monday, May 02, 2005 10:07 PM To: OSPF@PEACH.EASE.LSOFT.COM Subject: Re: DR election Yes and no, If a router "really wants to be the DR", the protocol does allow this through a back door. The router must act like it was already also elected as the DR. This can happen in what was a split area. By coming up later, the later router SHOULD know the other's priority and router-id. It can then boost its broadcasted priority and/or its router-id to gurantee re-election. Mitchell Erblich ---------------------- "Krishnan, Vijay G." wrote: > > The first router does not become the DR immediately. It waits for its > configurable "wait timer" to expire, before electing the DR. Others routers > could come up during this time. Once the DR is elected, addition of new > routers would not change the DR. This will reduce the instability due to the > DR changes. > > regards > Vijay > > -----Original Message----- > From: Mailing List [mailto:OSPF@PEACH.EASE.LSOFT.COM]On Behalf Of Ilan > Bercovich > Sent: Monday, May 02, 2005 11:51 AM > To: OSPF@PEACH.EASE.LSOFT.COM > Subject: DR election > > Hello > If all routers accept the DR regardless of their Router Priority, > It means that actually the first active router on the LAN is the DR. > Isn't this makes the Router Priority parameter somewhat irrelevant? > (In RSTP for instance, when priority is changed - network is > re-calculated). > Ilan
- 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