[Xorp-users] Partial fix found for : OSPF routes are lost/missing after a few hours

[Mellen, Ivan]

Hi Ben,
Thanks for your reply.
I haven't got chance to check top-of-tree xorp version yet.
Is there any fix (or is it planed) that enables more than one route in
an LSA packet?

Thanks,

Ivan

-----Original Message-----
From: Ben Greear [mailto:greearb at candelatech.com] 
Sent: Friday, January 18, 2013 10:41 AM
To: Mellen, Ivan
Cc: xorp-users at xorp.org
Subject: Re: [Xorp-users] Partial fix found for : OSPF routes are
lost/missing after a few hours

On 01/18/2013 09:25 AM, Mellen, Ivan wrote:
> Hi,
>
> In XORP 1.8.5,  OSPF routes are being dropped when there are more than
100 OSPF routes. Once dropped these routes do not recover.
>
> Depending on the processing power  of the PC, this bug can be 
> reproduced anywhere from 100 to 700 routes and the time when routes
are lost can be as low as one hour to several days.
>
>                  After examining Wireshark logs and looking through 
> the XORP code the problem seems to be the way XORP packages route
updates. There is only one route per LSA and when an OSPF refresh
starts(after one hour) OSPF receivers can be overloaded with packets.
>
>                  A simple fix is to apply the below patch which adds a

> small delay between transmitting LSA packets. Of course the proper fix
is to put more than one route in an LSA packet but this is a lengthy
change to OSPF.
>
> *** peer.cc    19 Jan 2012 20:28:20 -0000    1.1
> --- peer.cc    11 Dec 2012 00:20:14 -0000    1.2
> ***************
> *** 4112,4117 ****
> --- 4112,4119 ----
>
>        _peer.transmit(tr);
>
> +     usleep(50000);
>        return true;
>    }

I fixed some OSPF convergence issues related to bad OSPF retry timers
(or something like that) some time back...I wonder if that is what you
are hitting.

Can you try top-of-tree xorp (without the hack above) and see if that
works better?

Either way, I'm reluctant to apply this sort of patch upstream...

Thanks,
Ben

>
> Cheers,
>
> Ivan
>
> The information contained in this e-mail message is PRIVATE. It may 
> contain confidential information and may be legally privileged. It is 
> intended for the exclusive use of the addressee(s). If you are not the

> intended recipient, you are hereby notified that any dissemination,
distribution or reproduction of this communication is strictly
prohibited. If the intended recipient(s) cannot be reached or if a
transmission problem has occurred, please notify the sender immediately
by return e-mail and destroy all copies of this message.
> Thank you.
>
> <#>
>
>
> _______________________________________________
> Xorp-users mailing list
> Xorp-users at xorp.org
> http://mailman.ICSI.Berkeley.EDU/mailman/listinfo/xorp-users
>


--
Ben Greear <greearb at candelatech.com>
Candela Technologies Inc  http://www.candelatech.com