Re: [OSPF] issue for default route originate in NSSA

"Pat Murphy - (650)329-4044" <pmurphy@noc.usgs.net> Thu, 17 May 2007 14:36 UTC

Return-path: <ospf-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1Hoh5r-0000nk-4a; Thu, 17 May 2007 10:36:39 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1Hoh5p-0000jg-BM for OSPF@IETF.ORG; Thu, 17 May 2007 10:36:37 -0400
Received: from omega7.wr.usgs.gov ([130.118.4.3] helo=ns0.wr.usgs.gov) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1Hoh5n-0003tb-VM for OSPF@IETF.ORG; Thu, 17 May 2007 10:36:37 -0400
Received: from omega7.wr.usgs.gov by omega7.wr.usgs.gov (PMDF V6.0-23 #41392) id <01MGON61ZOE800AFTL@omega7.wr.usgs.gov> for OSPF@IETF.ORG; Thu, 17 May 2007 07:23:32 -0700 (PDT)
Date: Thu, 17 May 2007 07:23:32 -0700
From: "Pat Murphy - (650)329-4044" <pmurphy@noc.usgs.net>
Subject: Re: [OSPF] issue for default route originate in NSSA
To: OSPF@IETF.ORG
Message-id: <01MGON61ZPC200AFTL@omega7.wr.usgs.gov>
X-VMS-To: ospf@ietf.org
X-VMS-Cc: PMURPHY
MIME-version: 1.0
Content-type: TEXT/PLAIN; CHARSET="us-ascii"
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 4adaf050708fb13be3316a9eee889caa
Cc:
X-BeenThere: ospf@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: The Official IETF OSPG WG Mailing List <ospf.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ospf>, <mailto:ospf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/ospf>
List-Post: <mailto:ospf@ietf.org>
List-Help: <mailto:ospf-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ospf>, <mailto:ospf-request@ietf.org?subject=subscribe>
Errors-To: ospf-bounces@ietf.org

Jin,

Sorry there was an omission in my previous post regarding

>RFC3101 2.5 Calculating type-7 as external routes (3) states:

>Else if the destination is a Type-7 default route (destination
>          ID = DefaultDestination) and one of the following is true,
>          then do nothing with this LSA and consider the next in the
>          list:

>            o  The calculating router is a border router and the LSA has
>               its P-bit clear.  Appendix E describes a technique
>               whereby an NSSA border router installs a Type-7 default
>               LSA without propagating it.
>
>            o  The calculating router is a border router and is
>               suppressing the import of summary routes as Type-3
>               summary-LSAs.
>            [NSSA]
>Suppose user perform following steps in scenario(there is one ABR and ASBR 
>in NSSA area):
>1)ASBR generate type-7 default route LSA to redistribute default route 
>from static route source.
>2)In ABR,Create type 7 default route LSA via command like 
>"default-route-originate" for this NSSA area.

>After step 2),the ABR calculation also should not consider type-7 default 
>route LSA redistribted by ASBRs?
>Am I missing something?please correct me.

The answer is still yes as stated in the previous post; but also all Type 7
default LSAs are ignored by NSSA ABRs when the no-summary option is
configured. Whenever an NSSA ABR has no-summary configured, its default LSA
has Type 3 so that it is preferred, in OSPF, by every one of the NSSA's non-ABR
routers. The NSSA's ABR type 3 default LSA insures that the NSSA's non-ABRs
must follow a summary default path through one of its ABRs when forwarding
traffic to inter-area destinations.

However, if one of the NSSA's non-ABRs has an installed non-OSPF default
route, like a static default route, enabling no-summary on the NSSA border
could adversely impact this non-ABR's ability to forward traffic to OSPF
inter-area destinations.

Pat


_______________________________________________
OSPF mailing list
OSPF@ietf.org
https://www1.ietf.org/mailman/listinfo/ospf