-
Notifications
You must be signed in to change notification settings - Fork 62
BFD support #4852
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
BFD support #4852
Conversation
|
This PR now comes with database plumbing and an RPW that manages BFD on the rack switches. |
|
Testing notes. On Set up BFD via Omicron APIQuery BFDTesting BFD link detectionFrom the host machine running the falcon topology note that a BFD session is now down restore the link everyone should be back up |
internet-diglett
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks good to me, verified functionality in a4x2. Really cool seeing all of this come together!
| impl From<BfdSession> for BfdSessionKey { | ||
| fn from(value: BfdSession) -> Self { | ||
| Self { | ||
| switch: value.switch.parse().unwrap(), //TODO unwrap |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Are we handling this in a follow up issue?
This is a staging PR and should most likely be pulled into
Here we simply pass through BFD commands to the underlying
mgddaemons on the switches. No attempt is made to add BFD to the database schema or persist BFD information. As that would likely conflict with #4822.The purpose of the RFD is to set up the scaffolding and API interfaces for BFD to work end-to-end, and to do some interim testing without the benefit of persistence.
Depends on