From: Ajaz Nawaz (anawaz@xxxxxxxxx)
Date: Sat Nov 03 2001 - 04:26:15 GMT-3
Here's such a situation:
If the hub router is under single management administration and spokes are
being managed by another party for example.
More simply put.... beccause you administer the hub and not the spokes.
jaz
-----Original Message-----
From: nobody@groupstudy.com [mailto:nobody@groupstudy.com]On Behalf Of
George Hansen
Sent: 02 November 2001 23:46
To: ccielab@groupstudy.com
Subject: RE: OSPF over NBMA
I have noticed that if you use the 'ip ospf priority 0' interface command on
the spoke router, any 'neighbor ....' statements you also have on the spoke
router 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 than "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
priority value of the nonbroadcast neighbor associated with the IP address
specified. The default is 0. This keyword does not apply to
point-to-multipoint interfaces."
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 advertising (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