[action] [PR:22508] 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#1144
Merged
mssonicbld merged 1 commit intoAzure:202412from May 21, 2025
Conversation
…t back to back Paladin ports up with Arista-7060X6-16PE-384C-O128S2
<!--
Please make sure you've read and understood our contributing guidelines:
https://github.com/Azure/SONiC/blob/gh-pages/CONTRIBUTING.md
** Make sure all your commits include a signature generated with `git commit -s` **
If this is a bug fix, make sure your description includes "fixes #xxxx", or
"closes #xxxx" or "resolves #xxxx"
Please provide the following information:
-->
#### Why I did it
Currently when we loaded HWSKU `Arista-7060X6-16PE-384C-O128S2` on 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
- Microsoft ADO **(number only)**:
#### How I did it
Created a new `FANOUT` HWSKU containing special lanemap and polarity configs so that we can load `Arista-7060X6-16PE-384C-O128S2` on one Moby and `Arista-7060X6-16PE-384C-O128S2-FANOUT` and get Paladin ports up when connecting them back to back with the following setup:
```
Moby1 Moby2
HWSKU: Arista-7060X6-16PE-384C-O128S2 HWSKU: Arista-7060X6-16PE-384C-O128S2-FANOUT
Azure#17 <-> Azure#18
Azure#19 <-> Azure#20
Azure#21 <-> Azure#22
Azure#23 <-> Azure#24
Azure#18 <-> Azure#17
Azure#20 <-> Azure#19
Azure#22 <-> Azure#21
Azure#24 <-> Azure#23
```
#### How to verify it
Verified that all the Paladin ports can link up with the above setup.
<!--
If PR needs to be backported, then the PR must be tested against the base branch and the earliest backport release branch and provide tested image version on these two branches. For example, if the PR is requested for master, 202211 and 202012, then the requester needs to provide test results on master and 202012.
-->
#### Which release branch to backport (provide reason below if selected)
<!--
- Note we only backport fixes to a release branch, *not* features!
- Please also provide a reason for the backporting below.
- e.g.
- [x] 202006
-->
- [ ] 201811
- [ ] 201911
- [ ] 202006
- [ ] 202012
- [ ] 202106
- [ ] 202111
- [ ] 202205
- [ ] 202211
- [ ] 202305
- [x] msft-202412
#### Tested branch (Please provide the tested image version)
<!--
- Please provide tested image version
- e.g.
- [x] 20201231.100
-->
- [ ] <!-- image version 1 -->
- [ ] <!-- image version 2 -->
- [x] msft-202412
#### Description for the changelog
<!--
Write a short (one line) summary that describes the changes in this
pull request for inclusion in the changelog:
-->
Created `Arista-7060X6-16PE-384C-O128S2-FANOUT` based on `Arista-7060X6-16PE-384C-O128S2` and only update lanemap and polarity settings in bcm config.
<!--
Ensure to add label/tag for the feature raised. example - PR#2174 under sonic-utilities repo. where, Generic Config and Update feature has been labelled as GCU.
-->
#### Link to config_db schema for YANG module changes
<!--
Provide a link to config_db schema for the table for which YANG model
is defined
Link should point to correct section on https://github.com/Azure/sonic-buildimage/blob/master/src/sonic-yang-models/doc/Configuration.md
-->
#### A picture of a cute animal (not mandatory but encouraged)
Collaborator
Author
|
Original PR: sonic-net/sonic-buildimage#22508 |
Collaborator
Author
|
/azp run |
|
Azure Pipelines successfully started running 1 pipeline(s). |
mssonicbld
added a commit
to mssonicbld/sonic-buildimage-msft
that referenced
this pull request
Feb 5, 2026
…omatically (#25248) #### Why I did it src/sonic-swss-common ``` * d811e56 - (HEAD -> 202511, origin/202511) [ci] Update docker slave image referrence (Azure#1141) (Azure#1144) (8 days ago) [Tejaswini Chadaga] ``` #### How I did it #### How to verify it #### Description for the changelog
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
1 participant
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)