Re: DB Synchronization
Parag Deshpande <paragdeshpande@SDKSOFT.COM> Fri, 29 August 2003 19:37 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 PAA28135 for <ospf-archive@LISTS.IETF.ORG>; Fri, 29 Aug 2003 15:37:55 -0400 (EDT)
Received: from PEAR.EASE.LSOFT.COM (209.119.0.19) by cherry.ease.lsoft.com (LSMTP for Digital Unix v1.1b) with SMTP id <8.00B17865@cherry.ease.lsoft.com>; Fri, 29 Aug 2003 15:37:13 -0400
Received: from PEACH.EASE.LSOFT.COM by PEACH.EASE.LSOFT.COM (LISTSERV-TCP/IP release 1.8e) with spool id 53190834 for OSPF@PEACH.EASE.LSOFT.COM; Fri, 29 Aug 2003 15:37:08 -0400
Received: from 63.231.195.112 by WALNUT.EASE.LSOFT.COM (SMTPL release 1.0i) with TCP; Fri, 29 Aug 2003 15:36:44 -0400
Received: (qmail 29480 invoked by uid 0); 29 Aug 2003 19:36:31 -0000
Received: from unknown (63.231.195.1) by mpls-qmqp-01.inet.qwest.net with QMQP; 29 Aug 2003 19:36:31 -0000
Received: from 0-2pool146-97.nas9.minneapolis1.mn.us.da.qwest.net (HELO charita) (67.4.146.97) by mpls-pop-01.inet.qwest.net with SMTP; 29 Aug 2003 19:36:31 -0000
References: <D40034183F893A478D5FDEBBE34295B70151DDAF@claven.luminous.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 5.00.2615.200
X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2615.200
Message-ID: <004901c36e64$8c601d40$cbc8c8c8@sdksoft.com>
Date: Fri, 29 Aug 2003 14:34:19 -0500
Reply-To: Mailing List <OSPF@PEACH.EASE.LSOFT.COM>
Sender: Mailing List <OSPF@PEACH.EASE.LSOFT.COM>
From: Parag Deshpande <paragdeshpande@SDKSOFT.COM>
Subject: Re: DB Synchronization
To: OSPF@PEACH.EASE.LSOFT.COM
Precedence: list
Content-Transfer-Encoding: 7bit
I will be more clear here --
- Router A originates the LSA with seq no = 80000001 (Say mask is /8)
- Router B receives it.
- Now Router A goes down and comes up again.
- Originates LSA (with different mask - /16 but same lsid) with Seq no. =
80000001
(This always results in same checksum assuming other parameters such as
cost etc. are same!!)
Now during DB exchange
- Router A receives a DD packet with its own LSA listed - however when it
compares
DB LSA with one in DD packet the Seq number and Checksum would be same
(and age difference < MAXAGE_DIFF)
so it would assume that its the same LSA and not request it.
- Same thing happens at Router B.
- Untill Router A reoriginates the LSA Router B would still keep the Old LSA
(mask = /8).
As I understand this is a very rare case - but I was thinking if OSPF rfcs
provide any mechanism to resolve this faster - though I didn't find any such
references.
Thanks
Parag
----- Original Message -----
From: Shanthi Pendyala <spendyala@LUMINOUS.COM>
To: <OSPF@PEACH.EASE.LSOFT.COM>
Sent: Friday, August 29, 2003 12:40 PM
Subject: Re: DB Synchronization
hi,
Router A will request a copy of the stale LSA from B even though it has the
more upto-date LSA.
It will then immediately flood the updated LSA after
increasing the seq no.
so the DB exchange will complete..
shanthi kiran
-----Original Message-----
From: Parag Deshpande [mailto:paragdeshpande@SDKSOFT.COM]
Sent: Friday, August 29, 2003 10:13 AM
To: OSPF@PEACH.EASE.LSOFT.COM
Subject: DB Synchronization
Hi,
I had a doubt ->
2 routers A and B have an ospf adjacency.
Router A sends an ASExt lsa for network N1/m1 with LSID = N1.
Then Router A goes down & comes up again & reoriginates
ASExt lsa for network N1/m2 with LSID = N1 and then
gets adjacent with Router B.
**where m1 != m2 & they are multiple of 8. (/8, /16..)
also assuming that all other parameters are same.
However in this case the DB Exchange will fail to
synchronize these LSAs bcoz they appear
to be similar- LSID, SeqNum, Checksums being equal**
and thus will have to wait for the LSA to get refreshed.
I was wondering whether this can be resolved faster.
Thanks
Parag
- Re: DB Synchronization Shanthi Pendyala
- Re: DB Synchronization Parag Deshpande