-
Notifications
You must be signed in to change notification settings - Fork 741
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
chore: bump BFD toggle wait timeout #15939
Merged
Merged
Conversation
This file contains 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
we have 2 Cisco chassis, one can stably pass with 300 limitation. |
mssonicbld
pushed a commit
to mssonicbld/sonic-mgmt
that referenced
this pull request
Dec 11, 2024
Description of PR Bump the BFD toggle wait timeout to 450 seconds to give BFD session enough time to go up/down. Summary: Fixes # (issue) Microsoft ADO 30112171 Approach What is the motivation for this PR? We noticed that 300 seconds is not enough for BFD session to go up/down, so Cisco suggested us to bump it to 450 seconds.
Cherry-pick PR to 202405: #15989 |
8 tasks
mssonicbld
pushed a commit
that referenced
this pull request
Dec 11, 2024
Description of PR Bump the BFD toggle wait timeout to 450 seconds to give BFD session enough time to go up/down. Summary: Fixes # (issue) Microsoft ADO 30112171 Approach What is the motivation for this PR? We noticed that 300 seconds is not enough for BFD session to go up/down, so Cisco suggested us to bump it to 450 seconds.
mssonicbld
added
Included in 202405 branch
and removed
Created PR to 202405 branch
labels
Dec 11, 2024
mssonicbld
pushed a commit
to mssonicbld/sonic-mgmt
that referenced
this pull request
Jan 3, 2025
Description of PR Bump the BFD toggle wait timeout to 450 seconds to give BFD session enough time to go up/down. Summary: Fixes # (issue) Microsoft ADO 30112171 Approach What is the motivation for this PR? We noticed that 300 seconds is not enough for BFD session to go up/down, so Cisco suggested us to bump it to 450 seconds.
Cherry-pick PR to 202411: #16318 |
8 tasks
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Description of PR
Bump the BFD toggle wait timeout to 450 seconds to give BFD session enough time to go up/down.
Summary:
Fixes # (issue) Microsoft ADO 30112171
Type of change
Back port request
Approach
What is the motivation for this PR?
We noticed that 300 seconds is not enough for BFD session to go up/down, so Cisco suggested us to bump it to 450 seconds.
How did you do it?
How did you verify/test it?
Any platform specific information?
Supported testbed topology if it's a new test case?
Documentation