[quagga-dev 12808] Re: Quagga/BIRD incompatibility in OSPF loading phase

Paul Jakma paul at jakma.org
Tue Jun 23 11:42:23 BST 2015


On Tue, 23 Jun 2015, Andrew wrote:

> 93 isn't too busy, and 66 - too. Their CPU usage is some %, and traffic on 
> them isn't big.
>
> Dumps from 72 and 66 are in attach.

Thanks!

So, this is 66's view of the flooding activity on one LSA (tcpdump 
filtering to print only packets from 66,93 and 72):

    10.255.192.4 #   91.226.58.218 :
req: 192.168.255.72  -->  192.168.255.66        104.427212
upd: 192.168.255.93  -->       224.0.0.5        104.427932 seq 0x8000008e
upd: 192.168.255.66  -->       224.0.0.5        104.428292 seq 0x8000008e
ack: 192.168.255.93  -->  192.168.255.66        104.428865 seq 0x8000008e
ack: 192.168.255.66  -->  192.168.255.93        104.429577 seq 0x8000008e
req: 192.168.255.72  -->  192.168.255.66        109.427399
upd: 192.168.255.93  -->       224.0.0.5        109.427877 seq 0x8000008e
upd: 192.168.255.66  -->       224.0.0.5        109.427908 seq 0x8000008e
ack: 192.168.255.93  -->  192.168.255.66        109.428556 seq 0x8000008e
ack: 192.168.255.66  -->  192.168.255.93        109.428745 seq 0x8000008e
ack: 192.168.255.72  -->       224.0.0.6        111.006949 seq 0x8000008e
upd: 192.168.255.66  -->       224.0.0.5        141.317991 seq 0x8000008f
ack: 192.168.255.93  -->       224.0.0.5        141.769032 seq 0x8000008f
upd: 192.168.255.66  -->  192.168.255.72        149.429340 seq 0x8000008f
ack: 192.168.255.72  -->       224.0.0.6        150.775713 seq 0x8000008f

and here's 72's of the same:

    10.255.192.4 #   91.226.58.218 :
req: 192.168.255.72  -->  192.168.255.66        108.483854
req: 192.168.255.72  -->  192.168.255.93        108.483892
req: 192.168.255.72  -->  192.168.255.93        113.483927
req: 192.168.255.72  -->  192.168.255.66        113.483952
upd: 192.168.255.93  -->       224.0.0.5        113.485406 seq 0x8000008e
upd: 192.168.255.66  -->       224.0.0.5        113.485526 seq 0x8000008e
ack: 192.168.255.72  -->       224.0.0.6        113.485674 seq 0x8000008e
ack: 192.168.255.72  -->       224.0.0.6        115.063762 seq 0x8000008e
ack: 192.168.255.93  -->       224.0.0.5        145.826180 seq 0x8000008f
upd: 192.168.255.93  -->  192.168.255.72        153.486071 seq 0x8000008f
upd: 192.168.255.66  -->  192.168.255.72        153.486542 seq 0x8000008f
ack: 192.168.255.72  -->       224.0.0.6        154.832719 seq 0x8000008f

The initial timestamp in each dump is 4.069868 apart, so, assuming the 
clocks aren't too far off, it looks like the first req in each is the same 
one, as 104.427212+4.069868 = 108.497080.

Router 72 is sending LS-reqs for this LSA, but not getting a reply. 
However, 66 is sending LS-Updates for each request, as is 93. Neither of 
which are making it to 72.

Could this be a case of regular bursts of packet loss affecting packets 
being sent by 93 and 66 to 72?

regards,
-- 
Paul Jakma	paul at jakma.org	@pjakma	Key ID: 64A2FF6A
Fortune:
Real wealth can only increase.
 		-- R. Buckminster Fuller




More information about the Quagga-dev mailing list