Hold time expired error

[Jonathan Stewart]

If you cannot ping across your IX, you need to look lower than BIRD to
figure out the problem.

I would try to answer questions like: Is ARP resolving IPs to MACs?  Is the
problem isolated to a single BIRD server only?  Is it only IPv4 problem
only, or IPv6 as well?

If you can answer some of these questions, you'll get closer to finding the
root cause, I expect.

Cheers,
Jonathan



On Thu, Aug 3, 2017 at 2:25 AM, Ajai Kumar <joinajay1 at gmail.com> wrote:

> Dear All,
>
> We are facing problem with few peers in our IX.   Frequently they get Hold
> Timer Expired Error and they are not able to ping our route server IP.
> After shut no shut this problem resolves for sometime.  One log message
> appended
>
> bgp_hold_timeout:4690: NOTIFICATION sent to X.X.X.X (External AS 132953):
> code 4 (Hold Timer Expired Error), Reason: holdtime expired for X.X.X.X
> (External AS 132953), socket buffer sndcc: 57 rcvcc: 0 TCP state: 4,
> snd_una: 728368567 snd_nxt: 728368624 snd_wnd: 15744 rcv_nxt: 429172199
> rcv_adv: 429188583, hold timer out 90s, hold timer remain 0s
>
> Requesting for help pls.
> Regards,
> Ajai Kumar
> --
>
> (M) +91-9868477444 <+91%2098684%2077444>
> Skype ID:erajay
> P-mail: joinajay1 at gmail.com
> .................................
> Please don't print this email unless you really need to. This will
> preserve trees on our planet.
>



-- 
     Jonathan
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://trubka.network.cz/pipermail/bird-users/attachments/20170803/7fa7de00/attachment.html>