 |
 |
On 4/27/21 12:01 AM, Doug McIntyre wrote: > So, you're looking to lower it from 500ms down to 50ms when most of > the recomendations are a bottom limit of 150ms? That raises a good point. BFD negotiates the /higher/ of the two configured timeouts. So even if Frank has his set crazy low, if the route servers have a minimum of 500 ms, that's what they'll end up using. Frank, can you check "show bfd neighbor detail" or similar on your router? Are you negotiating 500 ms timeouts with the route servers? That would make the detection time 1500 ms (1.5s), which might suggest we're on the wrong track with the low timeouts causing the bouncing. (Or, maybe it still is that, meaning the disruption lasted long enough?) -- Richard