[ixpmanager] Issue with BIRD v2 peering, hold timers expiring.

[Nick Hilliard (INEX)]

Nick Zurku wrote on 02/04/2020 18:30:
> 2020-03-26 13:04:43 <RMT> pb_0004_as23738: Error: Hold timer expired
> 2020-03-27 23:04:43 <RMT> pb_0002_as20326: Error: Hold timer expired
> 2020-03-28 07:04:39 <RMT> pb_0013_as54825: Error: Hold timer expired
> 2020-03-28 12:04:25 <RMT> pb_0002_as20326: Error: Hold timer expired
> 2020-03-28 20:04:36 <RMT> pb_0002_as20326: Error: Hold timer expired
> 2020-03-29 20:04:26 <RMT> pb_0005_as5050: Error: Hold timer expired
> 2020-03-31 08:04:42 <RMT> pb_0002_as20326: Error: Hold timer expired
> 2020-03-31 14:04:24 <RMT> pb_0005_as5050: Error: Hold timer expired
> 2020-04-01 09:04:37 <RMT> pb_0013_as54825: Error: Hold timer expired
> 2020-04-01 19:04:24 <RMT> pb_0013_as54825: Error: Hold timer expired
> 2020-04-02 10:06:01 <RMT> pb_0012_as27364: Error: Hold timer expired
> 2020-04-02 13:04:23 <RMT> pb_0002_as20326: Error: Hold timer expired
> 2020-04-02 15:06:00 <RMT> pb_0011_as27364: Error: Hold timer expired

almost all these log messages are at 4 minutes past the hour.  Is there 
a periodic job which runs around then?

The default hold-time/dead-time on the ixp manager bird config is 
30s/90s.  Hold timer expired means that hellos were received / processed 
in 90 seconds, which sounds odd.

How many peers do you have, and how large is your config file?

Nick