From: George Hansen (HansenG@xxxxxxxxxxxxxxxx)
Date: Fri Nov 02 2001 - 20:45:56 GMT-3
I have noticed that if you use the 'ip ospf priority 0' interface command on th
e spoke router, any 'neighbor ....' statements you also have on the spoke route
r will not be shown in the running config.
It seems as if the 'ip ospf priority' interface command (default 1) is the best
to use. There must be a situation that the 'neighbor .... priority' (default 0
) command is more appropriate, but I don't know what that situation is (other t
han "you may not use 'ip ospf priority'").
My $.02.
George Hansen
>>> "Keith Leonard" <kleonard@aapt.com.au> 11/02/01 02:50PM >>>
Ron,
Firstly, from the Doco CD...........
"priority number (Optional) ----- 8-bit number indicating the router prior
ity value of the nonbroadcast neighbor associated with the IP address specified
. The default is 0. This keyword does not apply to point-to-multipoint interfac
es."
Note that this does not work for point-to-multipoint subinterfaces.
If you specify a priority on the neighbor statements on the spokes to say '2',
and you add the 'ip ospf priority 10' to the subinterface on the hub, then the
config on the spokes will be changed to reflect the priority that the hub is ad
vertising (Default of 1), ie; 'neighbor 134.5.20.1 priority 10'
Also, you only need one neighbor statement for each spoke on the hub, and NONE
on the spokes themselves. Just make sure to either set the spoke priorities to
'0', or set the hub priority to a value greater than '1' on the interfaces.
Cheers,
Keith
This archive was generated by hypermail 2.1.4 : Fri Jun 21 2002 - 06:45:02 GMT-3