[test_gap, LACP]verify no IO loss during pc member add/removal#4871
Merged
yejianquan merged 2 commits intosonic-net:masterfrom Dec 30, 2021
Merged
[test_gap, LACP]verify no IO loss during pc member add/removal#4871yejianquan merged 2 commits intosonic-net:masterfrom
yejianquan merged 2 commits intosonic-net:masterfrom
Conversation
yxieca
reviewed
Dec 27, 2021
yxieca
reviewed
Dec 27, 2021
yxieca
reviewed
Dec 27, 2021
yxieca
approved these changes
Dec 29, 2021
AntonHryshchuk
pushed a commit
to AntonHryshchuk/sonic-mgmt
that referenced
this pull request
Jan 4, 2022
…-net#4871) * [test_gap]verify no IO loss during member add/removal Approach What is the motivation for this PR? Mitigate test gap(LACP scope), verify no IO loss during pc member add/removal How did you do it? GIVEN a lag topology, keep sending packets between 2 port channels WHEN delete/add different members of a port channel THEN no packets shall loss How did you verify/test it? Run new test case on KVM testbed, it's executed as expected and passed. Any platform specific information? Supported testbed topology if it's a new test case? lag topology Signed-off-by: Jianquan Ye <jianquanye@microsoft.com>
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
2 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.
Description of PR
Summary:
Fixes #3606
Type of change
Back port request
Approach
What is the motivation for this PR?
Mitigate test gap(LACP scope), verify no IO loss during pc member add/removal
How did you do it?
GIVEN a lag topology, keep sending packets between 2 port channels
WHEN delete/add different members of a port channel
THEN no packets shall loss
How did you verify/test it?
Run new test case on KVM testbed, it's executed as expected and passed.
Any platform specific information?
Supported testbed topology if it's a new test case?
lag topology
Documentation