Skip to content

Conversation

@wumiaont
Copy link
Contributor

Why I did it

FIPS lab requires SONiC to have cli support to display MACSEC FIPS module. The output will be in the coming FIPS certificate to indicate the MACSEC module been certified.

Data center security officer will use this CLI command to check the FIPS module output and compare with what is in the certificate to make sure the MACsec module is the certified one.

Work item tracking
  • Microsoft ADO (number only):

How I did it

Add cli support "show macsec --fips-module". Output is vendor specific. Each vendor should update their platform.json to have fips_module defined there.

How to verify it

Have implemented unit test code to verify the code works.

Which release branch to backport (provide reason below if selected)

  • 202205
  • 202211
  • 202305
  • 202311
  • 202405
  • 202411
  • 202505
  • 202511

Tested branch (Please provide the tested image version)

Test with master.

Description for the changelog

Link to config_db schema for YANG module changes

A picture of a cute animal (not mandatory but encouraged)

@wumiaont wumiaont requested a review from lguohan as a code owner November 11, 2025 20:21
@mssonicbld
Copy link
Collaborator

/azp run Azure.sonic-buildimage

@azure-pipelines
Copy link

Azure Pipelines successfully started running 1 pipeline(s).

@azure-pipelines
Copy link

Commenter does not have sufficient privileges for PR 24493 in repo sonic-net/sonic-buildimage

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

Status: No status

Development

Successfully merging this pull request may close these issues.

2 participants