[ssw][ha][202511] cherry-pick custom_bfd changes#4114
Merged
vmittal-msft merged 2 commits intosonic-net:202511from Jan 9, 2026
Merged
[ssw][ha][202511] cherry-pick custom_bfd changes#4114vmittal-msft merged 2 commits intosonic-net:202511from
custom_bfd changes#4114vmittal-msft merged 2 commits intosonic-net:202511from
Conversation
Collaborator
|
/azp run |
|
Azure Pipelines successfully started running 1 pipeline(s). |
![github-advanced-security[bot]](https://avatars.githubusercontent.com/in/57789?s=60&v=4){kind=small}
| update_bfd_session_state(dvs, '9.1.0.3', 'Up') | ||
| update_bfd_session_state(dvs, '9.1.0.4', 'Up') | ||
| time.sleep(2) | ||
| route1 = vnet_obj.check_priority_vnet_ecmp_routes(dvs, vnet_name, ['9.1.0.1','9.1.0.2'], tunnel_name, route_ids=route1) |
Check notice
Code scanning / CodeQL
Unused local variable Note test
zjswhhh
changed the title
custom_bfd changes
…on (sonic-net#3878) What I did Adding rx_monitor_timer and tx_monitor_timer handling per HLD: https://github.com/sonic-net/SONiC/blob/master/doc/vxlan/Overlay%20ECMP%20ehancements.md sign-off: Jing Zhang zhangjing@microsoft.com Why I did it It's needed for SSW HA scenario as DPU side bfd is a software solution, interval must be set to a reasonable value. Signed-off-by: Jing Zhang <zhangjing@microsoft.com>
…ary/secondary NHG switchover (sonic-net#3922) What I did Today vnetorch only supports: custom monitoring sessions with primary & secondary NHG. bfd monitoring with primary NHG only. To make HA work we need bfd monitoring to support primary+secondary. This PR is to introduce a new monitoring type custom_bfd for that purpose. It will: create bfd sessions for both primary & secondary endpoints listen on state db for bfd session state update ignore update call from bfdorch switch and update nhg based on bfd session state It's not an elegant design to introduce a new bfd monitoring type. But the intention is to not break current functionality of vnetorch. Refactor of the code will be needed in future. Signed-off-by: Jing Zhang <zhangjing@microsoft.com>
Collaborator
|
/azp run |
|
Azure Pipelines successfully started running 1 pipeline(s). |
yue-fred-gao
approved these changes
Jan 9, 2026
Contributor
Author
|
Hi @vmittal-msft - can you help merge this? |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
4 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Cherry-pick:
What I did
Today vnetorch only supports:
custom monitoring sessions with primary & secondary NHG. bfd monitoring with primary NHG only.
To make HA work we need bfd monitoring to support primary+secondary. This PR is to introduce a new monitoring type custom_bfd for that purpose. It will:
create bfd sessions for both primary & secondary endpoints listen on state db for bfd session state update
ignore update call from bfdorch
switch and update nhg based on bfd session state
It's not an elegant design to introduce a new bfd monitoring type. But the intention is to not break current functionality of vnetorch. Refactor of the code will be needed in future.
What I did
Why I did it
How I verified it
Details if related