Re: OSPFv3 BadLSReq

[Sina Mirtorabi <[e-mail]>]

Taisuke

-> The point is below:
-> 1) R1 told R2 that R1 had an Intra-Area-Prefix-LSA associated
->    with a Router-LSA in Database Description packets.
->    So, R2 will request the Intra-Area-Prefix-LSA.
->
-> nevertheless,
->
-> 2) When R1 receives a LS-Request packet from R2,
->    it is possible that R2's neighbor state is already full,

I guess you meant to say "R1's neighbor state is already Full"

->    and there is no router in exchange or loading state,
->    and an Intra-Area-Prefix-LSA associated with a Router-LSA
->    is already flushed in R1's link state database.
->    So, BadLSReq event will happen.

The point that you missed is that when R1 maxage its LSA it is expecting
to get an Ack and when R2 receive the Maxage LSA it will remove it from
its link state request list ( a part from sending an Ack )

--

From 2328

(b) Else, if the adjacency is not yet full (neighbor state
                is Exchange or Loading), examine the Link state request
                list associated with this adjacency.  If there is an
                instance of the new LSA on the list, it indicates that
                the neighboring router has an instance of the LSA
                already.  Compare the new LSA to the neighbor's copy:

                o   If the new LSA is less recent, then examine the next
                    neighbor.

                o   If the two copies are the same instance, then delete
                    the LSA from the Link state request list, and
                    examine the next neighbor.[20]

                o   Else, the new LSA is more recent.  Delete the LSA
                    from the Link state request list.
--


Sina


->
-> ---
-> taisuke sasaki
->