ospf not accepting default route throu NSSA ?

From: George Harizanov (georgehar@xxxxxxxxxxx)
Date: Thu Aug 19 1999 - 14:25:28 GMT-3


   
Hi Garrin....
I experienced the same problem today while playing with OSPF.
As you said if the area is normal (not NSSA ) it injects the default from Rip.
If it is
NSSA it doesn't. I searched here and there but nothing so far.
I definitaley would like to clear this up..
Anybody any suggestions ?
Tnanks
George

Has anyone had experience with or seen the following:

Area 0 is connected to Area 10 which is configured as an NSSA. There is an
ASBR inside area 10 running RIP on the other side. We want to take a RIP
default route, bring it into OSPF area 10, and then redistribute it into
Area 0.

We have seen the following:
When Area 10 is configured as an NSSA, non-default RIP originated routes
redistribute fine as OSPF type N2 routes into Area 10, and eventually as
type E2 into the backbone
Default RIP originated routes will not propagate into Area 0 as OSPF routes

When Area 10 is configured as just a normal non-backbone area the default
route from RIP propagates just fine into Area 0.

So, the question is.... Making an area an NSSA is meant to restrict what
enters that Area, but does it also affect what leaves that area into area 0,
specifically default routes.

We have searched Doyle's and Moy's book and no mention of this issue.

Anyone have any similar experiences or comments?

Thanks
Garrin



This archive was generated by hypermail 2.1.4 : Thu Jun 13 2002 - 08:21:47 GMT-3