Log in to ask questions, share your expertise, or stay connected to content you value. Don’t have a login? Learn how to become a member.
I have the following :
Assuming you are seeing bfd flapping when you don't think there is an actual link issue, the general source would be a too low test interval for the bfd configuration and increasing the time would get the bfd check settle.
thanks so much !!
But I need to find the proof for the detection interval configured is too low. From the above, the timestamp for the packets in and out is within the the interval configured, why Control Detection time expired ?
Sorry, don't know that specific answer. When we encountered flapping we simply increased the interval by 100 at a time until it settled on what was good for the particular circumstances.
From practical experience I can say that intervals lower than 300 never worked.
And that on a number of links we had to raise the interval to as high as 1000 to prevent flapping. These tended to be long fiber runs in the real world running many km on poles.
thanks so much!The reason why I like to find the root cause is the current time interval used to work. So sth unknown occurs. We need to provide any reason to make any change. As the BFD timer change will affect the failover timing.