RE: default route into NSSA

From: Erick B. (erickbe@xxxxxxxxx)
Date: Fri Oct 13 2000 - 02:39:42 GMT-3


   
You're right (I should have said more - had a long
day). From his message, he wants to supply a
default-route and the area command with the 'nssa'
option wasn't doing it and adding
'default-information-originate' did what he expected,
which is how to supply a default route plus other
routes.

I thought he was asking for other methods, and
no-summary would supply a default-route and that's it
but I don't believe it makes the area totally stubby.
It's a area I need to do more playing in to completely
understand in detail.

Aaron, are we intrepreting your message correctly or ?

--- Derek Buelna <dameon@aracnet.com> wrote:
> I believe that configuring that command on the abr
> would make the area
> totally stubby which makes it so type 3's are also
> blocked. No IA routes
> other than a default out I think would be present
> inside the area.
>
> I guess I don't think this would allow a default
> into the nssa area.
>
> I believe that if the abr in injecting a default
> into the nssa area would be
> fine. I would think that if the backbone knows about
> the default you
> generated on some router and then once the abr
> receives the traffic, he
> would forward it to his default.
>
> Thoughts?
>
> -Derek
>
> -----Original Message-----
>
> You need to add 'no-summary' to the area command you
> have.
>
> --- "Granofsky, Aaron" <AGranofsky@bns.nec.com>
> wrote:
> > I have what's probably a stupid question, but I
> > can't seem to find the
> > answer.
> >
> > I have the following setup.
> >
> > r1 -----------r3---------------r4--------r5
> > area0 area9 (nssa) eigrp
> >
> >
> > Router 1 is generating a default route which all
> > ospf routers are receiving
> > except for r4.
> >
> > So, do I assume that a default route won't be
> > carried into a NSSA.
> >
> > BTW, If I replace *area 9 nssa* with *area 9 nssa
> > default-information-originate* than r4 receives a
> > default pointing to r3.
> > (But I don't think that's the issue)



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