From: CCIEin2006 (ciscocciein2006@gmail.com)
Date: Mon Jul 31 2006 - 08:10:40 ART
Thanks Alex - Unfortuantely my rack time is over so I cannot show any
outputs.
But what is wrong with having a "connected" route towards the forwarding
address? Is that documented somewhere?
On 7/31/06, Alex <alex.arseniev@gmail.com> wrote:
>
> I wonder if it might be a same problem as with "regular" OSPF default
> routes: the OSPF router must have an internal OSPF route to the forwarding
> address.
> That means, if R3 has a "connected" route towards forwarding address of
> R1-originated default and R3 is configured with "network <blah> 0.0.0.0"
> statement
> then R3 won't pass default to own routing table.
> Need to see Your configs and "show ip ospf database nssa" printout from
> R3.
> HTH
> Cheers
> Alex
>
> ----- Original Message -----
> From: "CCIEin2006" <ciscocciein2006@gmail.com>
> To: <swm@emanon.com>
> Cc: "Cisco certification" <ccielab@groupstudy.com>
> Sent: Monday, July 31, 2006 11:38 AM
> Subject: Re: Tricky One - Can Backbone router learn default route from
> NSSA?
>
>
> > Basically the setup looks like this:
> >
> > (R1)--Area100--(R3)--Area0
> > |
> > Area100
> > |
> > (R2)
> >
> > R1, R2, and R3 are connected to Area100 which is a NSSA. R3 is also
> > connected to Area0.
> > R1 is configured with Area 100 nssa default-information-originate.
> >
> > Both R2 and R3 see the 0.0.0.0 route in their OSPF database but only R2
> > actually enters the route in its routing table. R3 is not entering the
> > route
> > in its routing table.
> >
> > Can you explain why that is? I figured it might have something to do
> with
> > R3
> > being connected to Area0 but I'm not sure....
> >
> > Thanks
This archive was generated by hypermail 2.1.4 : Tue Aug 01 2006 - 07:13:49 ART