From: Vikas Gupta (vicky_gupta1803@xxxxxxxxx)
Date: Fri Oct 13 2000 - 14:38:12 GMT-3
Hi,
By default NSSA ABR would not inject default into
NSSA.
If you want to inject a default route along with type
3 summary routes into NSSA, you would have to use
"area <id> nssa default-information originate"
command. It will inject a default and IA routes from
your OSPF backbone domain into your NSSA. If you want
to block IA routes to go into NSSA and want all NSSA
routers to follow default to destinations outside the
area, you have to use this command
area <id> nssa no-summary default
information-originate
This will stop all type-3 to go into nssa with the
exception of single type-3 default into the nssa area.
When you do "sh ip route" on any NSSA router you
should see IA* 0/0 route in there.
Hope this makes sense.
Vikas
--- Tony Olzak <aolzak@buckeye-express.com> wrote:
> Adding "no-summary" does turn a stub area into a
> totally stubby area.
>
>
> Tony
>
> ----- Original Message -----
> From: "Erick B." <erickbe@yahoo.com>
> To: "Derek Buelna" <dameon@aracnet.com>;
> "'Granofsky, Aaron'"
> <AGranofsky@bns.nec.com>; <ccielab@groupstudy.com>
> Sent: Friday, October 13, 2000 1:39 AM
> Subject: RE: default route into NSSA
>
>
> > 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