route in datebase, not in routing table

[jafar.tarawneh]

Hi Guys,

I have the following config:

router ospf 201

redistribute static subnets

network 152.159.248.0 0.0.0.255 area 0

network 152.159.3.0 0.0.0.255 area 0

!

no ip classless

ip route 152.159.3.16 255.255.255.255 152.159.3.5

the static route is seen in the db of the neighs, but not the route table ?

I see it being sent out with an ACK from this host,

any thoughts ?

[Harold Ritter]

Jafar,

The issue is clearly that the route to the forward address is learnt via a static route. The route to the forward address should always be learnt via OSPF. Otherwise, the external route will never be installed in the RIB as you are now experiencing.

One way to fix the issue is to get rid of the static and let the ospf route to 152.159.3.5 be installed.

The other option is to get rid of the forward address itself by specifying the network statement for the channel1/0 interface as "network 152.159.3.6 0.0.0.0 area 0". This will get rid of the forward address on the type 5 lsa.

Hope this helps,

[jafar.tarawneh]

there is no static route for 152.159.3.5, but I changed the static route to point to chanell 1/0.

still no go.

this is running an old code 11.2 !!

[Harold Ritter · Accepted solution]

Jafar,

This static route was taken from your second post:

sh ip route 152.159.3.5

Routing entry for 152.159.3.5/32

Known via "static", distance 1, metric 0 (connected)

Redistributing via ospf 201

Advertised by ospf 201 subnets

Routing Descriptor Blocks:

* directly connected, via Channel1/0

Route metric is 0, traffic share count is 1

Is this from the router where you are not seeing the external route being installed.

You should try removing the forward address from the type 5 lsa by using the tip I gave you in my previous posting (ie. network 152.159.3.6 0.0.0.0 area 0)

Hope this helps,

[jafar.tarawneh]

Thanks,

I added auto summary for that unreachable host on the main router, and it worked !!

I think it is a code issue,

Thanks to everyone.

[Harold Ritter]

Jafar,

This is not really a code issue. The rule is that the forward address has to be resolved via an ospf route. All levels of code will behave the same.

Hope this helps,

[littledavewhite]

Hi

I have just experianced the same problem, on my network i had 5 routers on the same lan running ospf. The router priority was set to 1 on all routers. When the dr was elected it was a checkpoint firewall running ospf, this device was allowing full bi directional communication between all routers running ospf on the lan to itself apart from my new cisco box. My box though another router was the DR as i did not have a good neighbor state with the checkpoint box, i belive it was in the init state. It caused all sorts of issues on my box and the rules had to be ammended on the checkpoint.

[tahseen12]

The reason is also because of preference order in OSPF as

network 152.159.3.0 0.0.0.255 area 0

is learned by neighs as Intra area route and host route 152.159.3.16 255.255.255.255 as External type2,so it will only put 152.159.3.0 in the routing table and not 152.159.3.16 learned as LSA-5(part of above less specific subnet)