From: Joseph Brunner (joe@affirmedsystems.com)
Date: Mon Nov 05 2007 - 15:00:49 ART
As you know the DR is not preempt-able
I could do this with EEM;
Basically script up an applet that restarts the ospf process on a router
that receives a new neighbor adj = router 1. If router 2 and 3 are running
this applet, and they clear their neighbor adjacency, 1 will be the dr on
the wire when the restart.
That touches the config on R2 & R3, but does not touch priority from default
of 1. OF course I would demand 5 points from the proctor's for being a
little hacker and doing this... LOL
Would you like to see it?
-Joe
-----Original Message-----
From: nobody@groupstudy.com [mailto:nobody@groupstudy.com] On Behalf Of Eric
Phillips
Sent: Monday, November 05, 2007 12:05 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