[Arista]: Add HWSKU Arista-7060X6-64PE-B-O128S2

[dakotac-arista]

Why I did it

Added HWSKU Arista-7060X6-64PE-B-O128S2 for new deployment of 128 x 400g, 2 x 10g ports on TH-512.

Work item tracking

• Microsoft ADO (number only):

How I did it

How to verify it

Tested hwsku on dut and all interfaces worked.
ls -al shows expected path for symlink and also files within original and symlink directory.

Which release branch to backport (provide reason below if selected)

• 201811
• 201911
• 202006
• 202012
• 202106
• 202111
• 202205
• 202211
• 202305
• msft-202503

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)

[mssonicbld]

/azp run Azure.sonic-buildimage

[azure-pipelines]

Azure Pipelines successfully started running 1 pipeline(s).

[StormLiangMS]

hi @r12f @sdszhang could you help to take a look?

[sdszhang]

is buffer configuration going to be included in this PR?

[dakotac-arista]

is buffer configuration going to be included in this PR?

We are currently waiting on information from Broadcom. The qos and buffer files will be added in a follow up PR.

[dakotac-arista]

Hi @bingwang-ms, Should I make symlinks for non S2 variants or should I make new HWSKUs?

[bingwang-ms]

Buffer configuration is missing from the HWSKU. Is that expected?

[mssonicbld]

/azp run Azure.sonic-buildimage

[azure-pipelines]

Azure Pipelines successfully started running 1 pipeline(s).

[mssonicbld]

/azp run Azure.sonic-buildimage

[azure-pipelines]

Azure Pipelines successfully started running 1 pipeline(s).

[bingwang-ms]

Hi @bingwang-ms, Should I make symlinks for non S2 variants or should I make new HWSKUs?

There is another PR for same HWSKU but w/o S2 https://github.com/sonic-net/sonic-buildimage/pull/22672/files

[dakotac-arista]

Hi @bingwang-ms, Should I make symlinks for non S2 variants or should I make new HWSKUs?

There is another PR for same HWSKU but w/o S2 https://github.com/sonic-net/sonic-buildimage/pull/22672/files

Yes, I removed the symlink for O128 because it will be handled in that PR. This PR will only be for the S2 version.

I added default buffer configurations for LT2. From my understanding this HWSKU will be used as a fanout and doesn't need QoS. Do I need to add anything else or make any changes?

[bingwang-ms]

Hi @bingwang-ms, Should I make symlinks for non S2 variants or should I make new HWSKUs?

There is another PR for same HWSKU but w/o S2 https://github.com/sonic-net/sonic-buildimage/pull/22672/files

Yes, I removed the symlink for O128 because it will be handled in that PR. This PR will only be for the S2 version.

I added default buffer configurations for LT2. From my understanding this HWSKU will be used as a fanout and doesn't need QoS. Do I need to add anything else or make any changes?

For Arista-7060X6-64PE-B-O128S2, I would like @r12f to comment.
For Arista-7060X6-64PE-O128 in PR #22672, it will be used in prod. So QoS is a must.

[sdszhang]

pls include the change in #22825 for this hwsku too.

[kewei-arista]

pls include the change in #22825 for this hwsku too.

I'll update my RP after this PR merges.

[dakotac-arista]

@sdszhang I've added the fix so #22825 isn't blocked. I'm waiting on a comment from @r12f for next steps on this HWSKU.

[r12f]

/azp run Azure.sonic-buidlimage

[azure-pipelines]

Commenter does not have sufficient privileges for PR 22610 in repo sonic-net/sonic-buildimage

[r12f]

/azp run Azure.sonic-buildimage

[azure-pipelines]

Commenter does not have sufficient privileges for PR 22610 in repo sonic-net/sonic-buildimage

[StormLiangMS]

/azp run

[azure-pipelines]

Azure Pipelines successfully started running 1 pipeline(s).

[mssonicbld]

Cherry-pick PR to 202505: #22966

[mssonicbld]

Cherry-pick PR to msft-202412: Azure/sonic-buildimage-msft#1240