[Arista] Copy QoS from LT2 to T1 for Arista-7060X6-64PE-B-P32O64#24748
[Arista] Copy QoS from LT2 to T1 for Arista-7060X6-64PE-B-P32O64#24748yxieca merged 1 commit intosonic-net:masterfrom
Conversation
|
/azp run Azure.sonic-buildimage |
|
Azure Pipelines successfully started running 1 pipeline(s). |
Using a symlink to point to the buffer and pool values for LT2 role QoS. This will make sure any fixes for LT2 will be carried over. The same bcm config file with applied QoSO settings is already being used. Signed-off-by: Dakota Crozier <dakotac@arista.com>
f20e6f4 to
d85b13a
Compare
|
/azp run Azure.sonic-buildimage |
|
Azure Pipelines successfully started running 1 pipeline(s). |
|
@kperumalbfn can you help to review this one? @yxieca for viz. |
| @@ -1 +1 @@ | |||
| ../../../common/profiles/th5/gen/BALANCED/buffers_defaults_t1.j2 No newline at end of file | |||
| buffers_defaults_lt2.j2 No newline at end of file | |||
There was a problem hiding this comment.
could you check for cable-lengths for T1?
There was a problem hiding this comment.
pls check if cable-length/speed are included in pg_profile_lookup.ini
There was a problem hiding this comment.
I was not aware there are new cable-length/speed for the hwsku. Which ones need to be added?
Here are the existing ones: https://github.com/sonic-net/sonic-buildimage/blob/master/device/arista/x86_64-arista_7060x6_64pe_b/Arista-7060X6-64PE-B-P32O64/pg_profile_lookup.ini
There was a problem hiding this comment.
@dakotac-arista I believe we need to add 300m cable length for the T1 hwsku. We can handle it in another PR later.
|
Cherry-pick PR to msft-202503: Azure/sonic-buildimage-msft#1898 |
Using a symlink to point to the buffer and pool values for LT2 role QoS. This will make sure any fixes for LT2 will be carried over. The same bcm config file with applied QoSO settings is already being used. Signed-off-by: Dakota Crozier <dakotac@arista.com> Signed-off-by: Dawei Huang <daweihuang@microsoft.com>
Using a symlink to point to the buffer and pool values for LT2 role QoS. This will make sure any fixes for LT2 will be carried over. The same bcm config file with applied QoSO settings is already being used. Signed-off-by: Dakota Crozier <dakotac@arista.com> Signed-off-by: xiaweijiang <xiaweijiang@microsoft.com>
Using a symlink to point to the buffer and pool values for LT2 role QoS. This will make sure any fixes for LT2 will be carried over. The same bcm config file with applied QoSO settings is already being used. Signed-off-by: Dakota Crozier <dakotac@arista.com>
Using a symlink to point to the buffer and pool values for LT2 role QoS. This will make sure any fixes for LT2 will be carried over. The same bcm config file with applied QoSO settings is already being used. Signed-off-by: Dakota Crozier <dakotac@arista.com> Signed-off-by: Feng Pan <fenpan@microsoft.com>
Using a symlink to point to the buffer and pool values for LT2 role QoS. This will make sure any fixes for LT2 will be carried over. The same bcm config file with applied QoSO settings is already being used. Signed-off-by: Dakota Crozier <dakotac@arista.com> Signed-off-by: dprital <drorp@nvidia.com>
Why I did it
Arista-7060X6-64PE-B-P32O64 will also be used for a T1 role and they wanted to reuse the QoS settings.
Work item tracking
How I did it
Using a symlink to point to the buffer default values values for the LT2 role.
This will make sure any fixes for LT2 will be carried over.
The same bcm config file with applied QoS settings is already being used.
How to verify it
ls -alshowsbuffers_defaults_t1.j2 -> buffers_defaults_lt2.j2Tested on DUT and confirmed the buffer pools/profiles were populated and no issues during sanitize.
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)