From: P729 (p729@cox.net)
Date: Wed Feb 12 2003 - 20:27:46 GMT-3
I don't believe you would. I believe the former just documents the
neighbor's priority in the configuration after they become neighbors, while
the latter is how you actually set the priority on that neighbor'l link
facing you (the two examples would exist on opposite ends of an OSPF link).
I realize that the documentation probably still implies that one can set a
neighbor's priority in the 'neighbor' routing process command, but if you
look at the RFC (2328), I think you'll find that there is no mechanism for
setting (forcing) your neighbor's priority. The neighbor can tell you what
he is is set to, but you can't tell him what he should be.
Try a series of experiments:
-Try forcing the DR using only the 'neighbor priority' routing process
command (does it really work or is a normal election taking place?)
Then try:
-Force the DR using the 'ip ospf priority' interface commands on the others
-Look at the running config on the DR--does 'priority' show up on the
'neighbor' statements?
-Save the config
-Break the links between the DR and the others
-Reboot the DR
-Does 'priority' still show up on the 'neighbor' statements?
Regards,
Mas Kato
https://ecardfile.com/id/mkato
----- Original Message -----
From: "Sanfilippo, Ted" <Ted.Sanfilippo@PaeTec.com>
To: <ccielab@groupstudy.com>
Sent: Wednesday, February 12, 2003 9:30 AM
Subject: OSPF Neighbor Priority
In a Non-broadcast network with OSPF why would you use the following:
Router ospf 100
neighber 1.1.1.1 priority 10
OVER
interface serial0/0.1 multipoint
ip ospf priority 10
Ted Sanfilippo
Manager of Backbone Network Engineering
PaeTec Communications
One PaeTec Plaza
600 Willowbrook Office Park
Fairport, NY 14450
Tel: 585-340-2722
Fax: 585-340-2786
Email: ted.sanfilippo@paetec.com
.
.
This archive was generated by hypermail 2.1.4 : Sat Mar 01 2003 - 11:06:20 GMT-3