[FROG] ospf6d LSA's disappearing, probably stuck MaxAge LSA

Leon Meßner l.messner at physik.tu-berlin.de
Sun Feb 24 14:40:06 EST 2019


Hi,

On Mon, 11 Feb 2019 11:18:39 +0100
Leon Meßner <l.messner at physik.tu-berlin.de> wrote:

> What i see in debugging on some other Router (R2):
> 
> OSPF6: LSUpdate received on bond0.84
<snip>
> OSPF6:     Age:    1 SeqNum: 0x800002b4 Cksum: 2e43 Len: 88 
> OSPF6: ospf6_install_lsa Install LSA: [Router Id:0.0.0.0 Adv:192.109.82.2] age 1 seqnum 800002b4 in LSDB.
snip>
> OSPF6: LSUpdate received on tun0
> OSPF6:     Age: 3600 SeqNum: 0x8000040c Cksum: 580c Len: 88 
> OSPF6: ospf6_install_lsa Install LSA: [Router Id:0.0.0.0 Adv:192.109.82.2] age  268139 3600 seqnum 8000040c in LSDB.
> OSPF6: LSA disappearing: [Router Id:0.0.0.0 Adv:192.109.82.2]
> OSPF6: Schedule SPF Calculation for 0.0.0.0
> OSPF6: SPF: Scheduled in 0 msec 
> OSPF6: LSA disappearing: [Router Id:0.0.0.0 Adv:192.109.82.2]
> ... flooding of that LSA ...
> 
> So there is a MaxAge LSA that has a "higher" SequenceNumber.
> Probably from a prior boot. Should FRR on R1 raise its SequenceNumber
> for this LSA to 0x8000040d? Is this likely a problem on R1?

we got rid of the problem by unsticking the SeqNum: 0x8000040c LSA. Now
the question ramains if this is a bug in FRRouting or not. If
interested i can open an issue on github and try to replicate it.

Regards,
Leon



More information about the frog mailing list