-
Notifications
You must be signed in to change notification settings - Fork 1.7k
[Nokia][Device] Change the BCM SOC config to use PTCH header instead of PTCH2 for the CPU/KNET originated packets #24415
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
base: master
Are you sure you want to change the base?
Conversation
…of PTCH2 for the CPU/KNET originated packets Signed-off-by: saksarav <[email protected]>
|
/azp run Azure.sonic-buildimage |
|
Azure Pipelines successfully started running 1 pipeline(s). |
|
@vmittal-msft @rlhui @arlakshm for your VIZ. |
|
The corresponding BCM csp is CS00012432808 |
|
/azpw run |
|
/AzurePipelines run |
|
Azure Pipelines successfully started running 1 pipeline(s). |
|
The code changes in this PR is limited to Nokia BCM DNX platform and shouldn't be causing the PR checker failures. |
|
/azpw run |
|
Create msft-202405 PR also. |
|
Created #24518 for 202405 |
Why I did it
BCM fixed the KNET packet issue reported in CS00012426701 by using the PTCH with system port instead of PTCH2 with PP_PORT. This change was done to support the dynamic port speed change by removing the port and creating a port in SAI.
Work item tracking
How I did it
Updated the BCM config files to use PTCH header instead of PTCH2 for Nokia DNX platforms.
How to verify it
Verified all the control protocols are up with BCM config change and the BCM SAI fix provided for CS00012426701.
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)