From: Ajay Prakash (ajay.prakash@networkpeople.co.in)
Date: Mon Nov 05 2007 - 14:47:51 ART
I believe in your example you can set the priority of R2 and R3 from R1
using the neighbor statement. But the problem that you say would still exist
as there is no pre-emption of DR status once it is elected.
However in this example if the network is hub and spoke, both R2 and R3
would peer with R1 and not with each other. If R2 or R3 comes up before R1,
there would be no neighbor-ship and R2 or R3 would not take the DR status.
Pl. correct if I missed something.
Ajay
-----Original Message-----
From: nobody@groupstudy.com [mailto:nobody@groupstudy.com] On Behalf Of Eric
Phillips
Sent: Monday, November 05, 2007 10:35 PM
To: ccielab@groupstudy.com
Subject: Any way to force OSPF DR other than "priority 0"?
Hey all,
I have done quite a bit of Googling and DOC-CD reading, and have not found
anyone offering any clever ways to force the election of a certain router as
the DR besides setting the priority to 0 on all other routers.
For example, if I had a question that asked me to ensure Router1 was always
the DR on a certain segment without touching the configuration of Router2
and Router3 I can set the priority very high on Router1, but if Router1
boots a few seconds later than Router2, Router2 will be the DR even if it
has it's default priority of 1. The only way I can think to completely
guarantee Router1 is always the DR is to make the priority 0 on all other
routers.
Am I missing something obvious, or am I over thinking this too much? I have
not seen this asked in any practice labs, just theorizing what could happen.
-Eric
This archive was generated by hypermail 2.1.4 : Sat Dec 01 2007 - 06:37:28 ART