From: Tony Olzak (aolzak@xxxxxxxxxxxxxxxxxxx)
Date: Fri Oct 13 2000 - 13:03:22 GMT-3
Title: RE: default route into NSSA
It all depends on how you are sending this default route. If you have
a static route to 0.0.0.0, then it will be an external (type 5) LSA
and will not pass into the the NSSA. An NSSA is just a stub area that
allows an ASBR to exist within the area by utilizing type 7 LSAs.
Being a stub area, it will not allow external LSAs to enter.
If, on the other hand, you are using "default-information originate"
on the router in your backbone, this route will not pass into another
area by design. This command is supposed to be used to send default
routes into stub and totally stubby areas. Since you did this on your
backbone router, the ABRs will all see this route (they are in the
same area), but will not pass it into their own areas.
Tony
----- Original Message -----
From: Granofsky, Aaron
To: Derek Buelna ; 'Erick B.' ; Granofsky, Aaron ;
ccielab@groupstudy.com
Sent: Friday, October 13, 2000 1:36 AM
Subject: RE: default route into NSSA
Derek,
You got it on the nose. I tried adding *no-summary* and this is
what I ended up with:
Gateway of last resort is 11.1.0.5 to network 0.0.0.0
D 172.17.0.0/16 [90/2297856] via 172.16.0.7, 00:06:41, Serial0
C 172.16.0.0/16 is directly connected, Serial0
D 172.18.0.0/16 [90/2297856] via 172.16.0.7, 00:06:41, Serial0
11.0.0.0/16 is subnetted, 1 subnets
C 11.1.0.0 is directly connected, FastEthernet0
O*IA 0.0.0.0/0 [110/21] via 11.1.0.5, 00:01:38, FastEthernet0
O 172.16.0.0/12 is a summary, 00:06:33, Null0
BUT, My original question is still out there... R1 was generating
a default that r3 was picking up. R4 never got the default route
because it is in a NSSA. Is that by design? Is there something
that I can do to pass the default into the NSSA, or do I have to
add *area 9 nssa default-information-originate*
Regards,
Aaron
-----Original Message-----
From: Derek Buelna [mailto:dameon@aracnet.com]
Sent: Thursday, October 12, 2000 10:28 PM
To: 'Erick B.'; 'Granofsky, Aaron'; ccielab@groupstudy.com
Subject: RE: default route into NSSA
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-----
From: nobody@groupstudy.com [mailto:nobody@groupstudy.com] On
Behalf Of
Erick B.
Sent: Thursday, October 12, 2000 10:07 PM
To: Granofsky, Aaron; ccielab@groupstudy.com
Subject: Re: default route into NSSA
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