From: Peter van Oene (pvo@xxxxxxxxxxxx)
Date: Sun Jan 13 2002 - 19:39:55 GMT-3
In additional, hitting cisco.com and entering nssa default information
brings up this as the first hit.
http://www.cisco.com/warp/public/104/nssa.html#3
This is a pretty decent page describing some NSSA config
elements. Although the Cisco search engine is not the best thing in the
world, it definitely doesn't hurt to try it.
pete
ps, since I unicast my first post, the answer is adding area 1 nssa
default-information-originate on R2, the NSSA ABR.
At 03:27 PM 1/13/2002 -0600, Troy Rader wrote:
>I've searched the archives and I'm not finding an answer that clears this
>issue up for me.
>
>Here's my diagram: (I guess proportional font matters here)
>
>R10---R8---R3---R6---R2---R9---R11---R14---R4
> |
> |
> R5
>
>R10-R8 is RIP
>R8-R3-R6 is Area 2
>R6-R2 is Area 0
>R6-R5 is Area 3
>R2-R9-R11 is Area 1
>R11-R14 is IGRP
>R14-R4 is RIP
>
>Area 3 was the stub and then totally stubby area. I did okay with that.
>
>Area 1 is where I have my NSSA. I understand that my external routes from
>R10 are not learned in the NSSA, and that the redist'd routes from R11 and
>IGRP are N1 or N2 OSPF NSSA Ext and are propogated throughout OSPF.
>However, I'm lost on how to allow R9 and R11 to get to R10 RIP networks
>since they are External and not visible in the NSSA. I tried to originate
>a default from R2. R6 ended up with a default, but R9 did not.
>
>What's the trick, solution, answer?
>
>TIA,
>Troy
This archive was generated by hypermail 2.1.4 : Thu Jun 13 2002 - 10:56:27 GMT-3