From: C. Warren (ccie2000@xxxxxxxx)
Date: Sat Dec 08 2001 - 17:55:58 GMT-3
Do you have neighbor statements on the hub to each spoke? Do you have
the "broadcast" parameter on your map statements?
-----Original Message-----
From: nobody@groupstudy.com [mailto:nobody@groupstudy.com] On Behalf Of
Fernando Arias
Sent: Saturday, December 08, 2001 2:16 PM
To: 'Ajaz Nawaz'; 'George Hansen'; ccielab@groupstudy.com
Subject: RE: OSPF over NBMA
Hey Guys,
I have a somewhat similar situation, where I had successfully completed
lab 4. In my ospf set up I had the hub(r1)Multipoint and the spokes (r2)
and (r5)Physical interfaces. My hub was configured with ospf priority
200 and the spokes had ospf priority zero. The ospf network type for all
routers was Non-broadcast.
Everything was working fine until I power cycled the routers. Now the
routers won't form adjacencies. The frame cloud is fully mesh with map
stamens and I can ping across to all serial interfaces on the cloud.
I do not get any output from any of the ospf debug commands. However,
the sh ip ospf command does show the message "Area BACBONE(0) (Inactive)
on all 3 routers. I can't seem to get pass this condition.
any feedback will be appreciated.
Thanks,
Fernando
-----Original Message-----
From: nobody@groupstudy.com [mailto:nobody@groupstudy.com]On Behalf Of
Ajaz Nawaz
Sent: Saturday, November 03, 2001 2:26 AM
To: George Hansen; ccielab@groupstudy.com
Subject: RE: OSPF over NBMA
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,
This archive was generated by hypermail 2.1.4 : Thu Jun 13 2002 - 10:32:40 GMT-3