Re: DB Synchronization
Rikki Nguyen <rikki@REDBACK.COM> Fri, 29 August 2003 17:56 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 NAA18344 for <ospf-archive@LISTS.IETF.ORG>; Fri, 29 Aug 2003 13:56:30 -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 <23.00B172DF@cherry.ease.lsoft.com>; Fri, 29 Aug 2003 13:55:18 -0400
Received: from PEACH.EASE.LSOFT.COM by PEACH.EASE.LSOFT.COM (LISTSERV-TCP/IP release 1.8e) with spool id 53180985 for OSPF@PEACH.EASE.LSOFT.COM; Fri, 29 Aug 2003 13:54:46 -0400
Received: from 155.53.12.9 by WALNUT.EASE.LSOFT.COM (SMTPL release 1.0i) with TCP; Fri, 29 Aug 2003 13:54:46 -0400
Received: from redback.com (montreal.redback.com [155.53.42.143]) by prattle.redback.com (Postfix) with ESMTP id 404044B2C8D for <OSPF@PEACH.EASE.LSOFT.COM>; Fri, 29 Aug 2003 10:53:21 -0700 (PDT)
User-Agent: Mozilla/5.0 (X11; U; NetBSD i386; en-US; rv:1.1) Gecko/20020829
X-Accept-Language: en-us, en
MIME-Version: 1.0
References: <LISTSERV%2003082313022444@PEACH.EASE.LSOFT.COM> <3F47A2B0.6020808@redback.com> <001301c36e50$d2949de0$cbc8c8c8@sdksoft.com>
Content-Type: text/plain; charset="us-ascii"; format="flowed"
Content-Transfer-Encoding: 7bit
Message-ID: <3F4F9310.7000300@redback.com>
Date: Fri, 29 Aug 2003 10:53:20 -0700
Reply-To: Mailing List <OSPF@PEACH.EASE.LSOFT.COM>
Sender: Mailing List <OSPF@PEACH.EASE.LSOFT.COM>
From: Rikki Nguyen <rikki@REDBACK.COM>
Subject: Re: DB Synchronization
To: OSPF@PEACH.EASE.LSOFT.COM
Precedence: list
Content-Transfer-Encoding: 7bit
Parag Deshpande wrote: > 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. The checksum is computed over the entire LSA body, this includes the netmask. Since the netmasks are different, it would be difficult for the checksum to be the same. > > I was wondering whether this can be resolved faster. > > Thanks > Parag >
- Action on SeqNumberMismatch Igor Miroshnik
- Re: Action on SeqNumberMismatch Acee Lindem
- DB Synchronization Parag Deshpande
- Re: DB Synchronization Rikki Nguyen
- Re: DB Synchronization Parag Deshpande
- Re: DB Synchronization Rikki Nguyen
- Re: DB Synchronization Acee Lindem