-
Notifications
You must be signed in to change notification settings - Fork 1.4k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[Tunnel PFC] Add property for tunnel PFC #10962
Conversation
72fb63f
to
2fdd213
Compare
device/arista/x86_64-arista_7050cx3_32s/Arista-7050CX3-32S-C32/sai.profile
Show resolved
Hide resolved
src/sonic-config-engine/tests/sample_output/py3/config.arista7260-dualtor.bcm
Outdated
Show resolved
Hide resolved
device/arista/x86_64-arista_7260cx3_64/Arista-7260CX3-Q64/config.bcm.j2
Outdated
Show resolved
Hide resolved
device/arista/x86_64-arista_7050cx3_32s/Arista-7050CX3-32S-D48C8/config.bcm.j2
Show resolved
Hide resolved
f6183b3
to
45808fb
Compare
device/arista/x86_64-arista_7260cx3_64/Arista-7260CX3-Q64/config.bcm.j2
Outdated
Show resolved
Hide resolved
Replace the config.bcm file with j2 template file - Add 'sai_remap_prio_on_tnl_egress=1' property when device metadata local - Host subtype is 'dualtor' - Change sai.profile foe the new config.bcm.j2 - Add tests Test done: Unit test.
45808fb
to
ae9b69e
Compare
device/arista/x86_64-arista_7260cx3_64/Arista-7260CX3-C64/config.bcm.j2
Outdated
Show resolved
Hide resolved
/azp run |
You have several pipelines (over 10) configured to build pull requests in this repository. Specify which pipelines you would like to run by using /azp run [pipelines] command. You can specify multiple pipelines using a comma separated list. |
/azp run Azure.sonic-buildimage |
Azure Pipelines successfully started running 1 pipeline(s). |
/azp run Azure.sonic-buildimage |
Azure Pipelines successfully started running 1 pipeline(s). |
Signed-off-by: Ying Xie <[email protected]>
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@richardyu-ms you changed config.bcm for 5 hardware skus. but only updated sai.profile for 2 of them. you need to update all 5 sai.profiles.
ah, never mind. 7260 has right contents in sai.profiles already. |
* [Tunnel PFC] Add property for tunnel PFC Replace the config.bcm file with j2 template file - Add 'sai_remap_prio_on_tnl_egress=1' property when device metadata local - Host subtype is 'dualtor' - Change sai.profile foe the new config.bcm.j2
*[Cherry-pick] [Tunnel PFC] Add property for tunnel PFC Replace the config.bcm file with j2 template file - Add 'sai_remap_prio_on_tnl_egress=1' property when device metadata local - Host subtype is 'dualtor' - Change sai.profile foe the new config.bcm.j2
Per PR sonic-net#10962, add a new property sai_remap_prio_on_tnl_egress. Follow the rule, need to add the property into the permitted list file. Signed-off-by: richardyu-ms <[email protected]>
Per PR sonic-net#10962, added a new property sai_remap_prio_on_tnl_egress. Follow the rule, need to add the property into the permitted list file. Signed-off-by: richardyu-ms <[email protected]>
* [Tunnel PFC] Add property for tunnel PFC Replace the config.bcm file with j2 template file - Add 'sai_remap_prio_on_tnl_egress=1' property when device metadata local - Host subtype is 'dualtor' - Change sai.profile foe the new config.bcm.j2
**The hotfix is no longer required after PR sonic-net/sonic-buildimage#10962 is merged** Add a hotfix for BCM SAI 7.1.0 We are seeing Mux tunnel creation failure after BCM SAI is upgrated to `7.1.0` in PR sonic-net/sonic-buildimage#10583. This PR is to patch the `bcm.config` for `dualtor` deployment to workaround this issue until the issue is fixed in image. This PR will add `sai_remap_prio_on_tnl_egress=1` into `bcm.config` if the device is running `master` image, and deployment is `dualtor`, and the SKU contains `arista`. The change is validated by manually running `./testbed-cli.sh deploy-mg vms24-dual-t0-7050-2 str2 password.txt ` Signed-off-by: bingwang <[email protected]> Reverts !577
Why I did it
Add property sai_remap_prio_on_tnl_egress, which is dependent by tunnel PFC.
How I did it
Add property sai_remap_prio_on_tnl_egress, which is dependent by tunnel PFC.
This property should only be available in dual tor environment.
How to verify it
Test done:
Run test test_j2files.py
in another PR #11027
Which release branch to backport (provide reason below if selected)
Description for the changelog
Link to config_db schema for YANG module changes
A picture of a cute animal (not mandatory but encouraged)