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

Take non-CMIS xcvrs out of lpmode in SFF Manager #565

Merged
merged 1 commit into from
Dec 14, 2024

Conversation

peterbailey-arista
Copy link
Contributor

@peterbailey-arista peterbailey-arista commented Nov 21, 2024

Description

Fix non-CMIS transceivers in down state by bringing them out of low power mode in the SFF Manager Task.
This is intended to work together with the change in sonic-net/sonic-buildimage#20886.

Motivation and Context

Non-CMIS transceivers were not functioning correctly when put into Low Power mode. So XCVRD now brings them out of lpmode.

How Has This Been Tested?

Loaded an image containing this change alongside the change from sonic-net/sonic-buildimage#20886 on an Arista chassis containing a Clearwater2 linecard.
Verified that without this image some interfaces were in a down state but with the image all interfaces came up as expected.

Additional Information (Optional)

Copy link

linux-foundation-easycla bot commented Nov 21, 2024

CLA Signed

The committers listed above are authorized under a signed CLA.

  • ✅ login: peterbailey-arista / name: Peter Bailey (94b96b6)

@kenneth-arista
Copy link

@arlakshm @wenyiz2021 for awareness

Copy link

@wenyiz2021 wenyiz2021 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

@kenneth-arista
Copy link

kenneth-arista commented Nov 22, 2024 via email

@prgeor
Copy link
Collaborator

prgeor commented Dec 1, 2024

@mihirpat1 can you please review

@prgeor prgeor requested a review from mihirpat1 December 1, 2024 14:26
@@ -435,6 +435,8 @@ def task_worker(self):
# Skip if these essential routines are not available
continue

sfp.set_lpmode(False)
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@peterbailey-arista I would suggest to use sfp.set_lpmode() only for SFPs that follow SFF8472. All other transceivers like QSFP+, QSFP28 can support lpmode via EEPROM write. The above code expects each platform to implement set_lpmode() even thought that is NOT required for QSFP based modules.

if (SFP type module) {
    sfp.set_lpmode(False)
} else {
    api = set_lpmode(False)
}

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

After discussing with @byu343 I ended up wrapping api.set_lpmode in a try except instead. Please let me know if this update works for you. Thanks!

@@ -435,6 +435,12 @@ def task_worker(self):
# Skip if these essential routines are not available
continue

try:
api = sfp.get_xcvr_api()
api.set_lpmode(False)
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@peterbailey-arista Per the below implementation, an exception will not be returned for SFF-8472 modules. Can you please handle this accordingly.
https://github.com/sonic-net/sonic-platform-common/blob/0f2e22faccd093a1e5d18235fe119a860be7855e/sonic_platform_base/sonic_xcvr/api/public/sff8472.py#L308

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I've now updated it to use sfp.set_lpmode() for only SFPs implementing SFF8472 as was originally suggested

@@ -435,6 +435,12 @@ def task_worker(self):
# Skip if these essential routines are not available
continue

try:
api = sfp.get_xcvr_api()
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

api has been already obtained at the code before:

api = sfp.get_xcvr_api()

@@ -435,6 +436,11 @@ def task_worker(self):
# Skip if these essential routines are not available
continue

if isinstance(api, Sff8472Api):
sfp.set_lpmode(False)
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@peterbailey-arista Can we check for the return value in both the cases and log error if it returns False?
Also, can you please help in fixing the built failure?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I added the check with the new error log. But am not sure how to resolve the build failure, it does not seem to be related to my change. Do you have any suggestions?

@kenneth-arista
Copy link

/azpw run Azure.sonic-platform-daemons

@kenneth-arista
Copy link

Above build failure is unrelated to the change in this PR. The failure is caused by:

dpkg: error: cannot access archive 'libnl-3-200_*.deb': No such file or directory

@peterbailey-arista
Copy link
Contributor Author

/azpw run Azure.sonic-platform-daemons

@mssonicbld
Copy link
Collaborator

/AzurePipelines run Azure.sonic-platform-daemons

Copy link

Azure Pipelines successfully started running 1 pipeline(s).

@@ -435,6 +436,17 @@ def task_worker(self):
# Skip if these essential routines are not available
continue

set_lp_success = (
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I assume lpmode handling is only needed at module insertion event, right?

Just some minor suggestion:
Maybe adding below condition check can avoid unnecessary lpmode handling in other cases (e.g. the case of admin_status/host_tx_ready getting changed by config interface shutdown/startup)

if xcvr_inserted:
    <lpmode logic>

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The described scenario unfortunately still requires lpmode set False. If you shutdown then startup the interface without bringing it out of lpmode the interface remains down even if it was up before shutdown

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I thought lpmode can get reset after module reset (sfputil reset), but interface shut/start (i.e. NPU/PHY/laser tx ON/OFF) wouldn't impact the module on lpmode/etc unless user/platform/vendor explicitly triggers something additional for module as part of the interface shut/start. Is that not the case here?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

My mistake, I believe you are correct. I'll add that change, thanks

@peterbailey-arista
Copy link
Contributor Author

/azpw run Azure.sonic-platform-daemons

@mssonicbld
Copy link
Collaborator

/AzurePipelines run Azure.sonic-platform-daemons

Copy link

Azure Pipelines successfully started running 1 pipeline(s).

@arlakshm
Copy link
Contributor

arlakshm commented Dec 6, 2024

/Azp Azure.sonic-platform-daemons

Copy link

Command 'Azure.sonic-platform-daemons' is not supported by Azure Pipelines.

Supported commands
  • help:
    • Get descriptions, examples and documentation about supported commands
    • Example: help "command_name"
  • list:
    • List all pipelines for this repository using a comment.
    • Example: "list"
  • run:
    • Run all pipelines or specific pipelines for this repository using a comment. Use this command by itself to trigger all related pipelines, or specify specific pipelines to run.
    • Example: "run" or "run pipeline_name, pipeline_name, pipeline_name"
  • where:
    • Report back the Azure DevOps orgs that are related to this repository and org
    • Example: "where"

See additional documentation.

Fix non-CMIS transceivers in down state by bringing them out of
lpmode in the SFF Manager Task.
@peterbailey-arista
Copy link
Contributor Author

/azpw run Azure.sonic-platform-daemons

@mssonicbld
Copy link
Collaborator

/AzurePipelines run Azure.sonic-platform-daemons

Copy link

Azure Pipelines successfully started running 1 pipeline(s).

@arlakshm
Copy link
Contributor

@longhuan-cisco @mihirpat1, Can you please approve this change if all the comments are addressed.

Copy link
Contributor

@mihirpat1 mihirpat1 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@peterbailey-arista The changes look good to me. Can you please help in resolving the build failure?

@arlakshm
Copy link
Contributor

/Azp run Azure.sonic-platform-daemons

Copy link

Azure Pipelines successfully started running 1 pipeline(s).

@arlakshm arlakshm merged commit 88d0dd7 into sonic-net:master Dec 14, 2024
5 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

10 participants