From: Edwards, Andrew M (andrew.m.edwards@boeing.com)
Date: Wed Sep 21 2005 - 18:05:00 GMT-3
Blake,
Not sure of 'exactly' what you are doing, you might want to post your
configs for more detailed information....
Generally though, this sounds like the classic problem where you are
using OSPF over partial mesh hub-and-spoke with DR/BDR elections not
forming correctly.
You can get some strange instances when you don't do this right. What
you will notice is that the hub (for some odd reason - was that
planned?) tends to become the DR and one spoke becomes the BDR. One
quick reboot later and your routes are hosed with perfect adjacencies
over the frame-relay cloud. This is usually right after one spoke picks
up the DR role.
Make sure for ospf network types NBMA and broadcast you set the spokes
to never become the DR and hub to always become the DR.
HTH
Andy
-----Original Message-----
From: Blake Silvester [mailto:Blake.Silvester@telecom.co.nz]
Sent: Tuesday, September 20, 2005 10:26 PM
To: ccielab@groupstudy.com
Subject: OSPF routes not appearing in routing table.
Greetings all,
I am having some issues with OSPF over frame-relay. I have only begun
studying this topic, so I am sure someone can point me in the direction
of a probably quite simple answer.
I have a frame-relay topology with 4 routers connected through a frame
switch, the hub device has a point-to-point link to another device, and
a point to multipoint link to the other two devices.
All the links are pingable and the routers are all forming adjacencies
are in in full state, however, no routes are being accepted into the
route table. I can see advertised routes in a 'show ip ospf database'
however.
Nothing too fancy configured on the devices, so it's not an access-list
or route-map issue, but somehow routes aren't making it into the routing
table.
I wont bother pasting in config's just yet, but if someone has an
interest and would like to see them, that can certainly be managed,
other than that.... Any suggestions appreciated.
Cheers,
Blake S.
"This communication, including any attachments, is confidential.
If you are not the intended recipient, you should not read
it - please contact me immediately, destroy it, and do not
copy or use any part of this communication or disclose
anything about it. Thank you. Please note that this
communication does not designate an information system for
the purposes of the Electronic Transactions Act 2002."
This archive was generated by hypermail 2.1.4 : Sun Oct 02 2005 - 14:40:16 GMT-3