BFD Enhancement #383
BFD Enhancement #383
Conversation
|
|
|
|
||
| In current SONiC implementation BFD relies on kernel network stack to switch the BFD packet to next available nexthop when a active nexthop goes down. BFD timers in this case is directly proportional to the time it takes for kernel to get the nexthop down event. Faster the kernel learns active nexthop is down the more aggressive BFD timers can be. In this case it is suggested to configure BFD timer values to have a timeout of atleast 600 msec. | ||
|
|
||
| ## 3.2 CLI |
There was a problem hiding this comment.
Can the user turn off BFD feature for his/her setup? Can it be done through CLI?
There was a problem hiding this comment.
A new change is added in section 8, that should answer your question
* BFD Enhancment HLD * mend
|
Today I couldn't find any BFD usage in sonic-swss. Are any SAI BFD APIs planned to be used or is it all managed in control plane? |
As for now it is managed in control plane. |
| ``` | ||
|
|
||
| # 7 Scalability | ||
| - No of sessions: 64 |
There was a problem hiding this comment.
Is 64 a hard limit? Do you have any test result for the maximum number of sessions?
There was a problem hiding this comment.
No 64 it's not a hard limit. We have tested with 64 session but i do not have log to attach.
This document describes design for a few enhancements to BFD in BGP docker.
Proposes enhancement to Packet Tx.
A few display and debug enhancements.