RE: [OSPF] Functionally equivalent as-external lsa
"Chitra Lakshmi Namadevan" <Chitra_Namadevan@infosys.com> Mon, 17 July 2006 13:30 UTC
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1G2TAg-0001TH-AF; Mon, 17 Jul 2006 09:30:02 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1G2TAf-0001Po-3N for ospf@ietf.org; Mon, 17 Jul 2006 09:30:01 -0400
Received: from kecgate06.infosys.com ([61.95.162.82]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1G2TAe-0007OS-9O for ospf@ietf.org; Mon, 17 Jul 2006 09:30:01 -0400
Received: from indhubbhs03.ad.infosys.com ([192.168.200.83]) by Kecgate06.infosys.com with InterScan Messaging Security Suite; Mon, 17 Jul 2006 18:58:59 +0530
Received: from CHNSHLMSG02.ad.infosys.com ([172.21.73.102]) by indhubbhs03.ad.infosys.com with Microsoft SMTPSVC(6.0.3790.1830); Mon, 17 Jul 2006 18:58:51 +0530
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Subject: RE: [OSPF] Functionally equivalent as-external lsa
Date: Mon, 17 Jul 2006 18:58:49 +0530
Message-ID: <AB7361D23462024A83E88223FA4CA086B82BDA@CHNSHLMSG02.ad.infosys.com>
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
Thread-Topic: [OSPF] Functionally equivalent as-external lsa
Thread-Index: AcanQGCg7tncxDYmRVybX+Ro7pM+jgCZIUOQ
From: Chitra Lakshmi Namadevan <Chitra_Namadevan@infosys.com>
To: Vishwas Manral <vishwas.ietf@gmail.com>
X-OriginalArrivalTime: 17 Jul 2006 13:28:51.0440 (UTC) FILETIME=[F1480F00:01C6A9A4]
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 36b1f8810cb91289d885dc8ab4fc8172
Cc: ospf@ietf.org
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
Thanks Viswas!!! -----Original Message----- From: Vishwas Manral [mailto:vishwas.ietf@gmail.com] Sent: Friday, July 14, 2006 5:55 PM To: Chitra Lakshmi Namadevan Cc: ospf@ietf.org Subject: Re: [OSPF] Functionally equivalent as-external lsa Hi Chitra, > Problem 1: Your analysis is correct, the LSA should not be removed if it is in any of the neighbor lists. If an Acknowledgement is not got the LSA needs to be retransmitted to the neighbor. > Problem 2: If two routers, both reachable from one another, originate functionally equivalent AS-external-LSAs (i.e., same destination, cost and non-zero forwarding address), then the LSA originated by the router having the highest OSPF Router ID is used. The router having the lower OSPF Router ID can then flush its LSA. Also note that any router with lower Router-ID CAN flush it s LSA, it is an optimization to reduce the size of the OSPF DB. Thanks, Vishwas On 7/14/06, Chitra Lakshmi Namadevan <Chitra_Namadevan@infosys.com> wrote: > > > > > > Hi, > > > > Functionally equivalent AS-external lsas are originated. Therefore the lsa with higher advertising router id is installed and the other lsa is flushed. > > > > Topology: > > dummy dummy > > SW(*) SW(*) > > | | > > +-----+ | | +-----+ > > | | | | | | > > | +---+ +---+ | > > | | | | > > |PSS9 +------ X ------|PSS11| > > +-----+ +-----+ > > 10.81.156.72 10.81.156.74 > > 3.3.3.0/24 > > (*)dummy SW: only for up the Link of PSS9/PSS11. > > Problem 1: > > ============ > > But the database of PSS11 has the AS-external lsa whose advertising router is 10.81.156.72 along with the lsa advertised by 10.81.156.74. This is the problem. > > PSS9 sends a maxage lsa. When PSS11 receives this maxage lsa it should flush the external lsa with advertising router 10.81.156.72. But it is not flushed. > > It is due to the following explanation found in RFC2328: > > "If there is already a database copy, and if the database copy was received via flooding and installed less than MinLSArrival seconds ago, discard the new LSA (without acknowledging it) and examine the next LSA (if any) listed in the Link State Update packet." > > Therefore it discards the maxage lsa and so the lsa is not flushed and it still remains. > > Analysis: > > PSS-11 discards the maxage lsa without any ls-ack. PSS-9 should not flush the lsa and should send again a maxage lsa since it did not receive a LS-ACK for the maxage lsa. > > Kindly let me know if my analysis is correct. > > Problem 2: > > ========== > > Disconnect the cable and make the link up. Then the router with the lower router id (10.81.156.72 - PSS9) has the as-external lsa advertised by the higher router id (10.81.156.74 - PSS11). But it should have the as-external lsa advertised by lower router id i.e. self lsa. > > This is happening because the as-external lsa with higher router id is not flushed. Therefore when PSS 9 originates the self as-external lsa, it finds that functionally equivalent as-external lsa is still present so it discards its self lsa. > > Kindly let me know what mechanism can be followed to flush the as-external lsa with higher router id when the neighbor is deleted. > > Regards, > Chitra > **************** CAUTION - Disclaimer ***************** This e-mail contains PRIVILEGED AND CONFIDENTIAL INFORMATION intended solely for the use of the addressee(s). If you are not the intended recipient, please notify the sender by e-mail and delete the original message. Further, you are not to copy, disclose, or distribute this e-mail or its contents to any other person and any such actions are unlawful. This e-mail may contain viruses. Infosys has taken every reasonable precaution to minimize this risk, but is not liable for any damage you may sustain as a result of any virus in this e-mail. You should carry out your own virus checks before opening the e-mail or attachment. Infosys reserves the right to monitor and review the content of all messages sent to or from this e-mail address. Messages sent to or from this e-mail address may be stored on the Infosys e-mail system. ***INFOSYS******** End of Disclaimer ********INFOSYS*** _______________________________________________ OSPF mailing list OSPF@ietf.org https://www1.ietf.org/mailman/listinfo/ospf
- [OSPF] Functionally equivalent as-external lsa Chitra Lakshmi Namadevan
- Re: [OSPF] Functionally equivalent as-external lsa Vishwas Manral
- Re: [OSPF] Functionally equivalent as-external lsa Pat Murphy - (650)329-4044
- RE: [OSPF] Functionally equivalent as-external lsa Chitra Lakshmi Namadevan
- RE: [OSPF] Functionally equivalent as-external lsa Chitra Lakshmi Namadevan