On 8/13/11 12:54 PM, Shohrukh Shoyoqubov wrote:
On 08/14/2011 12:19 AM, Dag Richards wrote:
Shot in the dark here new to OSPF myself
Have you tried adding vlan208 interface on R1 to OSPF config on R1?
R1 has no vlan208 interface configured. R1 uses trunk0 to connect to
access mode switch ports in VLAN 208. R2 and R3 have vlan208 interfaces
connected to the trunk ports of the same switch with VLAN 208 allowed on
it.
Adjacencies are up. It is the default route that is not ending up in the
kernel routing table. What else except the existing static routes can
prevent it to get into the routing table?
OK I see, so vr2 is what faces the ISP on R1.
Whose netstat -nr did you print? Is that R 3?
I see that "192.168.60.252/30 10.10.10.9 UG 0 0 - 32 vlan208 "
made it to the route table.
i you were on CISCO I would suggest you try redistribute static in your
OSPF conf.
I see in the man page for ospfd.conf you can redist static and connected
I think you need to redist static and default. the man page seems to
indicate that redist default will cause " a default route pointing
to this router will be announced over OSPF."
in the CISCO land
--
IS-IS sleeps.
BGP peers are quiet.
Something must be wrong.
