Re: [OSPF] LSA Data Base Exchange Between the Master and the Slave

Acee Lindem <> Wed, 03 July 2013 13:30 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id EA30F11E8145 for <>; Wed, 3 Jul 2013 06:30:41 -0700 (PDT)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -2.383
X-Spam-Status: No, score=-2.383 tagged_above=-999 required=5 tests=[AWL=0.215, BAYES_00=-2.599, HTML_MESSAGE=0.001]
Received: from ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id sDqNYuQb9dQw for <>; Wed, 3 Jul 2013 06:30:36 -0700 (PDT)
Received: from ( []) by (Postfix) with ESMTP id BFADF11E81AC for <>; Wed, 3 Jul 2013 06:30:29 -0700 (PDT)
X-AuditID: c618062d-b7fc36d0000032ea-53-51d42773ec6e
Received: from (Unknown_Domain []) by (Symantec Mail Security) with SMTP id 0E.43.13034.37724D15; Wed, 3 Jul 2013 15:30:28 +0200 (CEST)
Received: from ([]) by ([]) with mapi id 14.02.0328.009; Wed, 3 Jul 2013 09:30:26 -0400
From: Acee Lindem <>
To: Biswajit Sadhu <>
Thread-Topic: [OSPF] LSA Data Base Exchange Between the Master and the Slave
Thread-Index: AQHOd9karRb6vRJcC0qJrnLf1haLMJlTNlAA
Date: Wed, 03 Jul 2013 13:30:26 +0000
Message-ID: <>
References: <>
In-Reply-To: <>
Accept-Language: en-US
Content-Language: en-US
x-originating-ip: []
Content-Type: multipart/alternative; boundary="_000_94A203EA12AECE4BA92D42DBFFE0AE471945CEeusaamb101ericsso_"
MIME-Version: 1.0
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFnrHLMWRmVeSWpSXmKPExsUyuXRPuG6J+pVAg8tzmC3eXZ/DZtFy7x67 A5PHzll32T2WLPnJFMAUxWWTkpqTWZZapG+XwJXx/QdLwfPAitk7prA3MH517GLk5JAQMJHY 39zHCmGLSVy4t56ti5GLQ0jgKKPE0V2boZxljBILp35jBqliE9CReP7oH5gtIqArsXPxI5Yu Rg4OZgFVicdH2UDCwgLeEj//b2UGCYsI+EjsWhwIUW0kMe3xRHaQMIuAisTPa2DVvEDV3952 MoHYQgIBEs/vnWYHsTkFAiXO3t/BAmIzAp32/dQasBpmAXGJW0/mM0GcLCCxZM95ZghbVOLl 439QryhLfJ/ziAWiPl9idcMkRohdghInZz5hmcAoOgvJqFlIymYhKYOI60gs2P2JDcLWlli2 8DUzjH3mwGOoXmuJU0ePMSKrWcDIsYqRo7Q4tSw33chgEyMwzo5JsOnuYNzz0vIQozQHi5I4 7yq9M4FCAumJJanZqakFqUXxRaU5qcWHGJk4OKUaGNmyY71jvW7FGvjHCCwQnzeDTTvdymTp 2anKa8wvK1jtXFq76wBzhgh3QDC/Sv3GELu1+XvelBZeejRDQktv7tKKOgdW9zkc3kkGF7le ZazqUufYMZ3zvU2MbDxPn39X0aqJi0o2P/tX+5rb6d3Sm/X3fPjmX4tyVo3c2nyxYcMSw7t7 hL4eVmIpzkg01GIuKk4EAJ332giBAgAA
Cc: "<>" <>
Subject: Re: [OSPF] LSA Data Base Exchange Between the Master and the Slave
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: The Official IETF OSPG WG Mailing List <>
List-Unsubscribe: <>, <>
List-Archive: <>
List-Post: <>
List-Help: <>
List-Subscribe: <>, <>
X-List-Received-Date: Wed, 03 Jul 2013 13:30:42 -0000

Hi Biswajit,

On Jul 3, 2013, at 6:35 AM, Biswajit Sadhu wrote:

Hi All,

I have a query in the OSPF Design of LSA Data Base Exchange.

In data base exchange process if the master has smaller database the the slave and the master sends the More bit as zero in its DB packet  then the slave should also set the M bit to 0 in reply to the master's DB packet with the same sequence number ?

No. The slave should continue to set the M bit until it has sent its entire database. The master should continue to poll the slave with increasing sequence numbers until the slave has completed exchanging its entire database and cleared the M bit. Excerpt from RFC 2328:

        This sending and receiving of Database Description packets is
        called the "Database Exchange Process".  During this process,
        the two routers form a master/slave relationship.  Each Database
        Description Packet has a sequence number.  Database Description
        Packets sent by the master (polls) are acknowledged by the slave
        through echoing of the sequence number.  Both polls and their
        responses contain summaries of link state data.  The master is
        the only one allowed to retransmit Database Description Packets.
        It does so only at fixed intervals, the length of which is the
        configured per-interface constant RxmtInterval.

Each Database Description contains an indication that there are
more packets to follow --- the M-bit. The Database Exchange
Process is over when a router has received and sent Database
Description Packets with the M-bit off.

Read RFC 2328 sections 10.6 and 10.8 and it should be clear. The actions of the database exchange master and slave are described in detail.

Hope this Helps,

 Should the data base exchange stop after that. what if the slave had more lsa's to send to the Master?

What about the vice-versa case where Master has a large Data base to exchange then the Slave  ?

   As per page 101 .rfc 2328 i am quoting few lines for the same RFC

            Increments the DD sequence number in the neighbor data
            structure.  If the router has already sent its entire
            sequence of Database Description Packets, and the just
            accepted packet has the more bit (M) set to 0, the neighbor
            event ExchangeDone is generated.  Otherwise, it should send
            a new Database Description to the slave.

            Sets the DD sequence number in the neighbor data structure
            to the DD sequence number appearing in the received packet.
            The slave must send a Database Description Packet in reply.
            If the received packet has the more bit (M) set to 0, and
            the packet to be sent by the slave will also have the M-bit
            set to 0, the neighbor event ExchangeDone is generated.
            Note that the slave always generates this event before the

 Best Regards,

Biswajit Sadhu

OSPF mailing list<>