Re: DR election
Erblichs <erblichs@EARTHLINK.NET> Mon, 02 May 2005 16:42 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 MAA02514 for <ospf-archive@LISTS.IETF.ORG>; Mon, 2 May 2005 12:42:11 -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 <16.0102FF8B@cherry.ease.lsoft.com>; Mon, 2 May 2005 12:42:12 -0400
Received: by PEACH.EASE.LSOFT.COM (LISTSERV-TCP/IP release 14.3) with spool id 68990814 for OSPF@PEACH.EASE.LSOFT.COM; Mon, 2 May 2005 12:42:09 -0400
Received: from 207.217.121.253 by WALNUT.EASE.LSOFT.COM (SMTPL release 1.0l) with TCP; Mon, 2 May 2005 12:41:31 -0400
Received: from h-68-164-88-190.snvacaid.dynamic.covad.net ([68.164.88.190] helo=earthlink.net) by pop-a065d19.pas.sa.earthlink.net with esmtp (Exim 3.36 #10) id 1DSdz9-000430-00 for OSPF@PEACH.EASE.LSOFT.COM; Mon, 02 May 2005 09:41:31 -0700
X-Sender: "Erblichs" <@smtp.earthlink.net> (Unverified)
X-Mailer: Mozilla 4.72 [en]C-gatewaynet (Win98; I)
X-Accept-Language: en
MIME-Version: 1.0
References: <313680C9A886D511A06000204840E1CF06DAD22A@whq-msgusr-02.pit.comms.marconi.com>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Message-ID: <42765745.9502E874@earthlink.net>
Date: Mon, 02 May 2005 09:37:25 -0700
Reply-To: Mailing List <OSPF@PEACH.EASE.LSOFT.COM>
Sender: Mailing List <OSPF@PEACH.EASE.LSOFT.COM>
From: Erblichs <erblichs@EARTHLINK.NET>
Subject: Re: DR election
To: OSPF@PEACH.EASE.LSOFT.COM
Precedence: list
Content-Transfer-Encoding: 7bit
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