Add new HWSKU Arista-7060X6-16PE-384C-O128S2-FANOUT so that we can get back to back Paladin ports up with Arista-7060X6-16PE-384C-O128S2#22508
Merged
StormLiangMS merged 3 commits intosonic-net:masterfrom May 21, 2025
Conversation
…t back to back Paladin ports up with Arista-7060X6-16PE-384C-O128S2.
Collaborator
|
/azp run Azure.sonic-buildimage |
|
Azure Pipelines successfully started running 1 pipeline(s). |
r12f
reviewed
May 14, 2025
.../x86_64-arista_7060x6_16pe_384c/Arista-7060X6-16PE-384C-O128S2-FANOUT/buffers_defaults_t0.j2
Show resolved
Hide resolved
.../arista/x86_64-arista_7060x6_16pe_384c/Arista-7060X6-16PE-384C-O128S2-FANOUT/buffers.json.j2
Show resolved
Hide resolved
.../arista/x86_64-arista_7060x6_16pe_384c/Arista-7060X6-16PE-384C-O128S2-FANOUT/buffer_ports.j2
Show resolved
Hide resolved
.../x86_64-arista_7060x6_16pe_384c/Arista-7060X6-16PE-384C-O128S2-FANOUT/buffers_defaults_t1.j2
Show resolved
Hide resolved
Collaborator
|
/azp run Azure.sonic-buildimage |
|
Azure Pipelines successfully started running 1 pipeline(s). |
Collaborator
|
/azp run Azure.sonic-buildimage |
|
Azure Pipelines successfully started running 1 pipeline(s). |
r12f
approved these changes
May 15, 2025
Contributor
|
/azpw ms_conflict |
1 similar comment
Contributor
|
/azpw ms_conflict |
Collaborator
|
Cherry-pick PR to msft-202412: Azure/sonic-buildimage-msft#1144 |
r12f
added
Included in msft-202412 Branch
and removed
Created PR to msft-202412 Branch
labels
Collaborator
|
Cherry-pick PR to 202505: #22719 |
liushilongbuaa
added
Included in 202505 Branch
and removed
Created PR to 202505 Branch
labels
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.
Why I did it
Currently when we loaded HWSKU
Arista-7060X6-16PE-384C-O128S2on two moby devices and connect their Paladin ports back to back, we can't get link up. It may help if we can get these links up and run the tests.Work item tracking
How I did it
Created a new
FANOUTHWSKU containing special lanemap and polarity configs so that we can loadArista-7060X6-16PE-384C-O128S2on one Moby andArista-7060X6-16PE-384C-O128S2-FANOUTand get Paladin ports up when connecting them back to back with the following setup:How to verify it
Verified that all the Paladin ports can link up with the above setup.
Which release branch to backport (provide reason below if selected)
Tested branch (Please provide the tested image version)
Description for the changelog
Created
Arista-7060X6-16PE-384C-O128S2-FANOUTbased onArista-7060X6-16PE-384C-O128S2and only update lanemap and polarity settings in bcm config.Link to config_db schema for YANG module changes
A picture of a cute animal (not mandatory but encouraged)