-
Notifications
You must be signed in to change notification settings - Fork 1.2k
Update and rename SONiC-SAI-POST.md #2083
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?
Update and rename SONiC-SAI-POST.md #2083
Conversation
- include Control Plane POST. - CLI to fetch the POST status.
|
/azp run |
|
No pipelines are associated with this pull request. |
|
@vikram-nexthop Can you share more details on "Control Plane POST" ? I understand the SAI POST to check the ASIC/SecY -- but no so clear on the requirements on control plane POST |
|
@judyjoseph Control plane POST validates the cryptographic module used by wpa_supplicant for MKA operations, which is separate from the SAI/ASIC crypto engines, and requires independent FIPS validation too. |
- Added sample MACsec POST status output for single and multi ASIC scenarios. - Added CLI to ToC.
|
/azp run |
|
No pipelines are associated with this pull request. |
|
|
||
| ### Enabling Control Plane POST in MACSecMgr init | ||
|
|
||
| MACSecMgr performs POST status query during process init and publishes the status in the _FIPS_MACSEC_POST_TABLE|crypto_ table. Any w. A failure will result in MACSecMgr not processing any configuration beyond this. |
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.
some typo? "Any w. A failure"
|
|
||
| The design must meet the following requirements: | ||
| - In order to accommodate different forwarding ASIC architecture or SAI implementation, the design should support enabling POST at either switch level (during switch init) or at MACSec engine level (during MACSec engine init). | ||
| - Should enable control plane POST at the MACSec level. |
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.
Is this a must for FIPS compliance?
Implementation PRs:
sonic-net/sonic-buildimage#24067
sonic-net/sonic-swss#3907
sonic-net/sonic-wpa-supplicant#99