Add t1-isolated-d56u1-lag into support list.#18826
Merged
StormLiangMS merged 2 commits intosonic-net:masterfrom Jun 10, 2025
Merged
Add t1-isolated-d56u1-lag into support list.#18826StormLiangMS merged 2 commits intosonic-net:masterfrom
StormLiangMS merged 2 commits intosonic-net:masterfrom
Conversation
Collaborator
|
/azp run |
|
Azure Pipelines successfully started running 1 pipeline(s). |
Contributor
Author
|
@r12f for review. |
Collaborator
|
Cherry-pick PR to msft-202412: Azure/sonic-mgmt.msft#377 |
mssonicbld
added
Included in msft-202412 Branch
and removed
Created PR to msft-202412 Branch
labels
Collaborator
|
@sdszhang PR conflicts with 202505 branch |
sdszhang
added a commit
to sdszhang/sonic-mgmt
that referenced
this pull request
Jun 30, 2025
What is the motivation for this PR? Add t1-isolated-d56u1-lag into support list How did you do it? How did you verify/test it? Run on physical testbed. (cherry picked from commit 460e375)
11 tasks
yejianquan
pushed a commit
that referenced
this pull request
Jul 1, 2025
…changes (#19254) * update t1-isolated-d56u2 topo with port-channel (#18152) Description of PR Summary: update t1-isolated-d56u2 to use port-channel for upstream neighbor. (cherry picked from commit b288741) * revert topo change in #18152 and add t1-isolated-lag topo (#18683) What is the motivation for this PR? use new name for t1-isolated topo with upstream port-channel. (cherry picked from commit af6a539) * support t1-isolated-d56u2 in test_acl.py, test_stress_acl.py and test_qos_sai (#18444) What is the motivation for this PR? Add t1-isolated-d56u2 topo support into test_acl.py, test_stress_acl.py and test_qos_sai How did you do it? Add t1-isolated-d56u2 topo support into test_acl.py, test_stress_acl.py and test_qos_sai How did you verify/test it? Ran on physical testbed. (cherry picked from commit 33b6673) * Add t1-isolated-d56u1-lag into support list. (#18826) What is the motivation for this PR? Add t1-isolated-d56u1-lag into support list How did you do it? How did you verify/test it? Run on physical testbed. (cherry picked from commit 460e375) * copy generate_topo.py over.
yejianquan
added
Included in 202505 branch
and removed
Cherry Pick Conflict_202505
labels
nissampa
pushed a commit
to nissampa/sonic-mgmt_dpu_test
that referenced
this pull request
Aug 7, 2025
What is the motivation for this PR? Add t1-isolated-d56u1-lag into support list How did you do it? How did you verify/test it? Run on physical testbed.
opcoder0
pushed a commit
to opcoder0/sonic-mgmt
that referenced
this pull request
Dec 8, 2025
What is the motivation for this PR? Add t1-isolated-d56u1-lag into support list How did you do it? How did you verify/test it? Run on physical testbed. Signed-off-by: opcoder0 <[email protected]>
AharonMalkin
pushed a commit
to AharonMalkin/sonic-mgmt
that referenced
this pull request
Dec 16, 2025
What is the motivation for this PR? Add t1-isolated-d56u1-lag into support list How did you do it? How did you verify/test it? Run on physical testbed. Signed-off-by: Aharon Malkin <[email protected]>
gshemesh2
pushed a commit
to gshemesh2/sonic-mgmt
that referenced
this pull request
Dec 21, 2025
What is the motivation for this PR? Add t1-isolated-d56u1-lag into support list How did you do it? How did you verify/test it? Run on physical testbed. Signed-off-by: Guy Shemesh <[email protected]>
venu-nexthop
pushed a commit
to venu-nexthop/sonic-mgmt
that referenced
this pull request
Jan 13, 2026
What is the motivation for this PR? Add t1-isolated-d56u1-lag into support list How did you do it? How did you verify/test it? Run on physical testbed.
gshemesh2
pushed a commit
to gshemesh2/sonic-mgmt
that referenced
this pull request
Jan 26, 2026
What is the motivation for this PR? Add t1-isolated-d56u1-lag into support list How did you do it? How did you verify/test it? Run on physical testbed. Signed-off-by: Guy Shemesh <[email protected]>
ytzur1
pushed a commit
to ytzur1/sonic-mgmt
that referenced
this pull request
Feb 2, 2026
What is the motivation for this PR? Add t1-isolated-d56u1-lag into support list How did you do it? How did you verify/test it? Run on physical testbed. Signed-off-by: Yael Tzur <[email protected]>
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
5 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 # (issue)
Type of change
Back port request
Approach
What is the motivation for this PR?
Add t1-isolated-d56u1-lag into support list
How did you do it?
How did you verify/test it?
Run on physical testbed.
Any platform specific information?
Supported testbed topology if it's a new test case?
Documentation