[202012]Support different DSCP_TO_TC_MAP for T1 in dualtor deployment#11580
Merged
neethajohn merged 2 commits intosonic-net:202012from Aug 1, 2022
Merged
[202012]Support different DSCP_TO_TC_MAP for T1 in dualtor deployment#11580neethajohn merged 2 commits intosonic-net:202012from
DSCP_TO_TC_MAP for T1 in dualtor deployment#11580neethajohn merged 2 commits intosonic-net:202012from
Conversation
neethajohn
approved these changes
Aug 1, 2022
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
2 participants
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
This PR is to backport #11569 into
202012branch.This PR is to apply different
DSCP_TO_TC_MAPto downlink and uplink ports on T1 in dualtor deployment.The
DSCP_TO_TC_MAPis not changed.DSCP2andDSCP6are mapped toTC2andTC6respectively.A new
DSCP_TO_TC_MAP|AZURE_UPLINKis defined and applied.DSCP2andDSCP6are mapped toTC1to avoid mixing up lossy and lossless traffic from T2.The extra lossy
PG2andPG6added in PR #11157 is reverted as well because no traffic from T2 is mapped toPG2orPG6now.How I did it
Define a new map
DSCP_TO_TC_MAP|AZURE_UPLINKfor 7260 T1.How to verify it
Verified by test case in
test_j2files.py.Which release branch to backport (provide reason below if selected)
Description for the changelog
Support different
DSCP_TO_TC_MAPfor T1 in dualtor deploymentLink to config_db schema for YANG module changes
A picture of a cute animal (not mandatory but encouraged)