[action] [PR:13044] Added new t1 topo t1-32-lag#13636
Merged
mssonicbld merged 1 commit intosonic-net:202311from Jul 11, 2024
Merged
[action] [PR:13044] Added new t1 topo t1-32-lag#13636mssonicbld merged 1 commit intosonic-net:202311from
mssonicbld merged 1 commit intosonic-net:202311from
Conversation
8 tasks
Collaborator
Author
|
Original PR: #13044 |
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:
Added new t1 topo for 202311: topo_t1-32-lag
4 uplinks/portchannels
20 downlinks/channels
4 admin down ports
Fixes # (issue)
Type of change
Back port request
Approach
What is the motivation for this PR?
To support new t1 topo for mlnx 4700 device.
How did you do it?
Added in some new config file, and edit some script file make sure the new config can be used.
How did you verify/test it?
Deployed it on hardware and verified with running link flip test on it.
Any platform specific information?
Supported testbed topology if it's a new test case?
Documentation