Re: Action on SeqNumberMismatch

Acee Lindem <acee@REDBACK.COM> Sat, 23 August 2003 17:22 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 NAA18122 for <ospf-archive@LISTS.IETF.ORG>; Sat, 23 Aug 2003 13:22:26 -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 <16.00AFF41B@cherry.ease.lsoft.com>; Sat, 23 Aug 2003 13:22:27 -0400
Received: from PEACH.EASE.LSOFT.COM by PEACH.EASE.LSOFT.COM (LISTSERV-TCP/IP release 1.8e) with spool id 52307169 for OSPF@PEACH.EASE.LSOFT.COM; Sat, 23 Aug 2003 13:22:25 -0400
Received: from 155.53.12.9 by WALNUT.EASE.LSOFT.COM (SMTPL release 1.0i) with TCP; Sat, 23 Aug 2003 13:22:25 -0400
Received: from redback.com (pptp-6-148.redback.com [155.53.6.148]) by prattle.redback.com (Postfix) with ESMTP id D9AE222BE6A for <OSPF@PEACH.EASE.LSOFT.COM>; Sat, 23 Aug 2003 10:22:24 -0700 (PDT)
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.4) Gecko/20030624 Netscape/7.1 (ax)
X-Accept-Language: en-us, en
MIME-Version: 1.0
References: <LISTSERV%2003082313022444@PEACH.EASE.LSOFT.COM>
Content-Type: text/plain; charset="ISO-8859-1"; format="flowed"
Content-Transfer-Encoding: 7bit
Message-ID: <3F47A2B0.6020808@redback.com>
Date: Sat, 23 Aug 2003 13:21:52 -0400
Reply-To: Mailing List <OSPF@PEACH.EASE.LSOFT.COM>
Sender: Mailing List <OSPF@PEACH.EASE.LSOFT.COM>
From: Acee Lindem <acee@REDBACK.COM>
Subject: Re: Action on SeqNumberMismatch
To: OSPF@PEACH.EASE.LSOFT.COM
In-Reply-To: <LISTSERV%2003082313022444@PEACH.EASE.LSOFT.COM>
Precedence: list
Content-Transfer-Encoding: 7bit

Hi  Igor,

Igor Miroshnik wrote:

>All,
>
>RFC 2328 says:
>
>"  State(s):  Exchange or greater
>
>     Event:  SeqNumberMismatch
>
> New state:  ExStart
>
>    Action:  The (possibly partially formed) adjacency is torn
>      down, and then an attempt is made at
>      reestablishment.  The neighbor state first
>      transitions to ExStart.  The Link state
>      retransmission list, Database summary list and Link
>      state request list are cleared of LSAs.  Then the
>      router increments the DD sequence number in the
>      neighbor data structure, declares itself master
>      (sets the master/slave bit to master), and starts
>      sending Database Description Packets, with the
>      initialize (I), more (M) and master (MS) bits set.
>      This Database Description Packet should be otherwise
>      empty (see Section 10.8)."
>
>Questions:
>
>1) Is the Database Description Packet sent empty?
>
Yes.

>2) If so, what is the meaning of the word "otherwise" in the end of the
>quotaton?
>
It means that the DD packet only contains the OSPF header and the fixed
portion of the DD
packet (i.e., interface mtu, options,  DD bits, and DD sequence number).


>
>Thanks,
>Igor
>
>
>