[action] [PR:20125] Handle Multi-port portchannel member case in ECMP member flap TC#20362
Merged
mssonicbld merged 1 commit intosonic-net:202505from Aug 22, 2025
Merged
Conversation
…ic-net#20125) This fixes issue mentioned in sonic-net#17887. For pizza box DUTs, multi-port portchannel scenario was not handled, which caused issue on certain specific topologies. How did you do it? Add all members of PORT_CHANNEL (if the port being shutdown is part of PORT_CHANNEL) to the filtered ports list, so that during fib_test, these ports are not randomly picked as src port.
11 tasks
Collaborator
Author
|
Original PR: #20125 |
Collaborator
Author
|
/azp run |
|
Azure Pipelines successfully started running 1 pipeline(s). |
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
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 #17887
Type of change
Back port request
Approach
What is the motivation for this PR?
This fixes issue mentioned in #17887.
For pizza box DUTs, multi-port portchannel scenario was not handled, which caused issue on certain specific topologies.
How did you do it?
Add all members of PORT_CHANNEL (if the port being shutdown is part of PORT_CHANNEL) to the filtered ports list, so that during fib_test, these ports are not randomly picked as src port.
How did you verify/test it?
Verified on t1-lag topology. the testcase passes.
Logs:
Any platform specific information?
NA
Supported testbed topology if it's a new test case?
NA
Documentation