Re: Question about the default route in NSSA

"Pat Murphy - (650)329-4044" <pmurphy@omega7.wr.usgs.gov> Fri, 13 September 2002 17:34 UTC

Received: from cherry.ease.lsoft.com (cherry.ease.lsoft.com [209.119.0.109]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA13193 for <ospf-archive@LISTS.IETF.ORG>; Fri, 13 Sep 2002 13:34:03 -0400 (EDT)
Received: from walnut (209.119.0.61) by cherry.ease.lsoft.com (LSMTP for Digital Unix v1.1b) with SMTP id <16.0071B8B9@cherry.ease.lsoft.com>; Fri, 13 Sep 2002 13:35:44 -0400
Received: from DISCUSS.MICROSOFT.COM by DISCUSS.MICROSOFT.COM (LISTSERV-TCP/IP release 1.8e) with spool id 190697 for OSPF@DISCUSS.MICROSOFT.COM; Fri, 13 Sep 2002 13:35:44 -0400
Received: from 130.118.4.3 by WALNUT.EASE.LSOFT.COM (SMTPL release 1.0f) with TCP; Fri, 13 Sep 2002 13:35:44 -0400
Received: from omega7.wr.usgs.gov by omega7.wr.usgs.gov (PMDF V6.0-24 #41392) id <01KMG6FP0H348WZH2D@omega7.wr.usgs.gov> for OSPF@DISCUSS.MICROSOFT.COM; Fri, 13 Sep 2002 10:35:39 -0700 (PDT)
X-VMS-To: OSPF@DISCUSS.MICROSOFT.COM
X-VMS-Cc: PMURPHY,mani_devarajan@net.com
MIME-version: 1.0
Content-type: TEXT/PLAIN; CHARSET="us-ascii"
Message-ID: <01KMG6FP0IZ68WZH2D@omega7.wr.usgs.gov>
Date: Fri, 13 Sep 2002 10:35:39 -0700
Reply-To: Mailing List <OSPF@DISCUSS.MICROSOFT.COM>
Sender: Mailing List <OSPF@DISCUSS.MICROSOFT.COM>
From: "Pat Murphy - (650)329-4044" <pmurphy@omega7.wr.usgs.gov>
Subject: Re: Question about the default route in NSSA
Comments: cc: MANI_DEVARAJAN@NET.COM
To: OSPF@DISCUSS.MICROSOFT.COM
Precedence: list

Mani,

>So my question is, does NSSA ABR(R4) must inject type7 default
>route in to AREA2 or we need manually configure default route
>on R4 for the RIP I destination network.

A default route is not necessary on R4 for it to reach the RIP-I
destinations since R4 can compute their next hops from their Type 5
LSAs. However if R4 originates a default Type 7 LSA into NSSA 2 that R5
prefers, then R5 could reach the RIP-I destinations through R4 via its
default..

By default, all of an NSSA ABRs, such as R4, are expected to originate a
type 7 LSA for default when none of the NSSA's internal routers, such as
R5, orignate a Type 7 LSA for default, even when they don't possess an
installed default path. I am not sure about RFC 1587, but this
requirement is explicitly described in the lastest NSSA draft.

Compliments of a suggestion of Alex Zinin's, I posted a draft titled

        Type 5 to Type 7 Translation

which is still available. It would allow the partial import of Type 5
LSAs, such as your RIP I routes, with aggregation. You can also find it
at

        ftp://noc.usgs.net/ietf/draft-ietf-ospf-5to7-01.txt

Quite frankly it seems logical that an NSSA should be able to import a
subset of an OSPF domain's Type 5 external LSAs complete with
aggregation, given that it can import external routes to networks
outside the AS via its external links. While I hope to repost this draft
soon, its current content is fairly clean.

Pat