[action] [PR:22496] [Arista] support moby platform with TH5-512#1121
Merged
mssonicbld merged 1 commit intoAzure:202412from May 14, 2025
Merged
[action] [PR:22496] [Arista] support moby platform with TH5-512#1121mssonicbld merged 1 commit intoAzure:202412from
mssonicbld merged 1 commit intoAzure:202412from
Conversation
<!--
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
For Moby with TH5-512, the logical port indices are different. We need to a different machine name differentiate Moby with TH5 and with TH5-512.
##### Work item tracking
- Microsoft ADO **(number only)**:
#### How I did it
In boot0, determine Moby with TH5-512 based on HwApi read from eeprom
Create a new device folder x86_64-arista_7060x6_16pe_384c_b based on existing 86_64-arista_7060x6_16pe_384c
Fix the logical ports indices used by bcm config.
#### How to verify it
<!--
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
#### Tested branch (Please provide the tested image version)
<!--
- Please provide tested image version
- e.g.
- [x] 20201231.100
-->
- [ ] <!-- image version 1 -->
- [ ] <!-- image version 2 -->
#### Description for the changelog
<!--
Write a short (one line) summary that describes the changes in this
pull request for inclusion in the changelog:
-->
<!--
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#22496 |
Collaborator
Author
|
/azp run |
11 tasks
|
Azure Pipelines successfully started running 1 pipeline(s). |
liushilongbuaa
pushed a commit
that referenced
this pull request
Mar 25, 2026
…omatically (#24285) Why I did it src/sonic-swss-common * 7f1b50f - (HEAD -> master, origin/master, origin/HEAD) Revert "[sonic-db-cli] Add flag to make cli calls to container databases (#1070)" and #1111 (#1123) (5 hours ago) [Qi Luo] * 16a8a93 - [ci] Use 1ES agent pool to provide more disk when building swss. (#1121) (2 days ago) [Liu Shilong] * 7682785 - Revert "Fix risky unwrap(), expect(), and casting (#1113)" (#1118) (2 days ago) [Liu Shilong] * cf7c7f6 - Fix issue where namespace would not be read (#1111) (2 days ago) [Connor Roos] * d6ccff7 - Fix risky unwrap(), expect(), and casting (#1113) (4 days ago) [Qi Luo] * e67092c - Add PORT_SERDES_ATTR_ID_LIST to FLEX COUNTER DATABASE (#1099) (9 days ago) [Dhanasekar Rathinavel] * d2c8f2c - [ci] Migrate agent pool from sonicbld-1es to sonicso1ES-amd64 (#1101) (2 weeks ago) [Liu Shilong] * 4b86a77 - [dhcp_relay] sonic dhcp relay agent for IPv4 (#1017) (4 weeks ago) [Akshath TR] * 472a425 - SHlorch changes for EVPN MH feature (#1051) (5 weeks ago) [jayakj] * 7407a2e - Optimize memory usage by replacing the queue's underlying container with a list. (#1083) (7 weeks ago) [Hua Liu] * 130d8b6 - Add chassis db. (#1085) (7 weeks ago) [dypet] * 66e437a - Fix mocktests for buster builds (#1087) (8 weeks ago) [prabhataravind] * 32b14a4 - Update static database_config.json in swsscommon (#1086) (8 weeks ago) [prabhataravind] * c253917 - Add pop batch size support for ZMQ Consumer (#1084) (8 weeks ago) [Vivek] * 4fea06e - [sonic-db-cli] Add flag to make cli calls to container databases (#1070) (8 weeks ago) [Connor Roos]
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
For Moby with TH5-512, the logical port indices are different. We need to a different machine name differentiate Moby with TH5 and with TH5-512.
Work item tracking
How I did it
In boot0, determine Moby with TH5-512 based on HwApi read from eeprom
Create a new device folder x86_64-arista_7060x6_16pe_384c_b based on existing 86_64-arista_7060x6_16pe_384c
Fix the logical ports indices used by bcm config.
How to verify it
Which release branch to backport (provide reason below if selected)
Tested branch (Please provide the tested image version)
Description for the changelog
Link to config_db schema for YANG module changes
A picture of a cute animal (not mandatory but encouraged)