What is the problem with shorter hold timers? Shorter hold timers allow BGP failures to be detected more quickly, reducing time to find an alternate, functional route. 60 second hold timers with 20 second keepalives are fine in the real world in my experience. Jonathan Jonathan Stewart Network Engineer LES.NET - AS18451 Desk: 1-204-666-6191 Mobile: 1-204-990-2120 130 Portage Avenue E Winnipeg, MB R3C 0A1 CANADA On Fri, 2025-10-17 4:21 p.m., Richard Laager wrote:
On 2025-10-15 16:32, Richard Laager wrote:
What do you have for hold timers? And is it the same for both route servers?
rs2 is proposing 240 seconds, if I'm reading this packet capture correctly.
I can set a "min hold time" value in BIRD. If we find that raising the hold timer fixes the issues, I will probably set a minimum. If I set that, it will break the sessions with lower values immediately, so this would need some transition. That would probably look something like: 1) See who it would affect and email them. 2) Enable it on one route server. 3) After a bit, enable it on the other route server. -- Richard
_______________________________________________ mice-discuss mailing list -- mice-discuss@lists.micemn.net To unsubscribe send an email to mice-discuss-leave@lists.micemn.net