Skip to content
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

Fix for handling broadcom DNX ASIC to have ipv4 and ipv6 ACL rules in separate tables. #2178

Merged
merged 1 commit into from
Mar 28, 2022

Conversation

judyjoseph
Copy link
Contributor

@judyjoseph judyjoseph commented Mar 14, 2022

What I did
Fix for handling broadcom DNX ASIC to have ipv4 and ipv6 ACL rules in separate tables.
Related PR : sonic-net/sonic-buildimage#10235

Why I did it
Broadcom DNX ASIC need to have ipv4 and ipv6 ACL rules in separate tables.

How I verified it
Verified the SWSS_VARS is updated and sub_platfom populated with 'broadcom-dnx'

Details if related

@judyjoseph
Copy link
Contributor Author

/azp run

@azure-pipelines
Copy link

Azure Pipelines successfully started running 1 pipeline(s).

@judyjoseph judyjoseph merged commit 20dde0c into sonic-net:master Mar 28, 2022
dprital pushed a commit to dprital/sonic-swss that referenced this pull request May 8, 2022
… separate tables. (sonic-net#2178)

Use the sub_platform env variable which is populated via swss_vars and sonic_version.yml
preetham-singh pushed a commit to preetham-singh/sonic-swss that referenced this pull request Aug 6, 2022
… separate tables. (sonic-net#2178)

Use the sub_platform env variable which is populated via swss_vars and sonic_version.yml
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants