update full isolated topo for C512S2 and C448O16#19211
Merged
StormLiangMS merged 2 commits intosonic-net:masterfrom Jun 30, 2025
Merged
update full isolated topo for C512S2 and C448O16#19211StormLiangMS 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). |
Collaborator
|
/azp run |
|
Azure Pipelines successfully started running 1 pipeline(s). |
Collaborator
|
/azp run |
|
Azure Pipelines successfully started running 1 pipeline(s). |
Contributor
Author
|
Note: This generate_topo.py in this PR has dependencies on #19202 to generate correct files. |
r12f
approved these changes
Jun 26, 2025
ansible/veos
Outdated
| - t1-isolated-d448u8-lag | ||
| - t1-isolated-d56u2 | ||
| - t1-isolated-v6-d448u16 | ||
| - t1-isolated-v6-d448u8-lag |
Collaborator
There was a problem hiding this comment.
Only the first port is having lag, do you mind to update to u15-lag?
Contributor
Author
There was a problem hiding this comment.
updated the topo to use the lag on the first physical port: PortList(LagPort(12), 13, 16, 17, 44, 45, 48, 49)
Merged
11 tasks
Collaborator
|
/azp run |
|
Azure Pipelines successfully started running 1 pipeline(s). |
Janetxxx
approved these changes
Jun 27, 2025
yejianquan
added
Cherry Pick Conflict_202505
Approved for 202505 branch
and removed
Cherry Pick Conflict_202505
labels
Collaborator
|
@sdszhang PR conflicts with 202505 branch |
sdszhang
added
Request for 202505 branch
Approved for 202505 branch
and removed
Approved for 202505 branch
labels
mssonicbld
pushed a commit
to mssonicbld/sonic-mgmt
that referenced
this pull request
Jul 1, 2025
What is the motivation for this PR? Update the t0-isolated-xx and t1-isolated-xx full topo How did you do it? generated the topo again.
Collaborator
|
Cherry-pick PR to 202505: #19314 |
11 tasks
r12f
added
Approved for msft-202412 Branch
and removed
Cherry Pick Conflict_msft-202412
labels
Contributor
Author
|
manual 202412 cherry-pick PR: Azure/sonic-mgmt.msft#459 |
yejianquan
pushed a commit
that referenced
this pull request
Jul 3, 2025
What is the motivation for this PR? Update the t0-isolated-xx and t1-isolated-xx full topo How did you do it? generated the topo again. Co-authored-by: Dashuai Zhang <[email protected]>
mssonicbld
added
Included in 202505 branch
and removed
Created PR to 202505 branch
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? Update the t0-isolated-xx and t1-isolated-xx full topo How did you do it? generated the topo again.
ashutosh-agrawal
pushed a commit
to ashutosh-agrawal/sonic-mgmt
that referenced
this pull request
Aug 14, 2025
What is the motivation for this PR? Update the t0-isolated-xx and t1-isolated-xx full topo How did you do it? generated the topo again.
vidyac86
pushed a commit
to vidyac86/sonic-mgmt
that referenced
this pull request
Oct 23, 2025
What is the motivation for this PR? Update the t0-isolated-xx and t1-isolated-xx full topo How did you do it? generated the topo again.
opcoder0
pushed a commit
to opcoder0/sonic-mgmt
that referenced
this pull request
Dec 8, 2025
What is the motivation for this PR? Update the t0-isolated-xx and t1-isolated-xx full topo How did you do it? generated the topo again. Signed-off-by: opcoder0 <[email protected]>
gshemesh2
pushed a commit
to gshemesh2/sonic-mgmt
that referenced
this pull request
Dec 16, 2025
What is the motivation for this PR? Update the t0-isolated-xx and t1-isolated-xx full topo How did you do it? generated the topo again. Signed-off-by: Guy Shemesh <[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? Update the t0-isolated-xx and t1-isolated-xx full topo How did you do it? generated the topo again. 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? Update the t0-isolated-xx and t1-isolated-xx full topo How did you do it? generated the topo again. 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? Update the t0-isolated-xx and t1-isolated-xx full topo How did you do it? generated the topo again.
gshemesh2
pushed a commit
to gshemesh2/sonic-mgmt
that referenced
this pull request
Jan 26, 2026
What is the motivation for this PR? Update the t0-isolated-xx and t1-isolated-xx full topo How did you do it? generated the topo again. 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? Update the t0-isolated-xx and t1-isolated-xx full topo How did you do it? generated the topo again. 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
6 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:
Update full topology for both C512S2 and C448O16 hwsku.
Type of change
Back port request
Approach
What is the motivation for this PR?
Update the t0-isolated-xx and t1-isolated-xx full topo
How did you do it?
generated the topo again.
How did you verify/test it?
Any platform specific information?
Supported testbed topology if it's a new test case?
Documentation