Skip to content
New issue

Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? # to your account

[Nokia Device] Set the clock for both Ramon and J2C+ #21764

Merged
merged 1 commit into from
Feb 21, 2025

Conversation

saksarav-nokia
Copy link
Contributor

Why I did it

Changed the clock frequency as per BCM's recommendation

Work item tracking
  • Microsoft ADO (number only):

How I did it

Changed the clock frequency to 1.6GHZ for both Ramons and J2C+

How to verify it

Verified in our Nokia system testbed that the system is up and passing the traffic without any issues.

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

  • 201811
  • 201911
  • 202006
  • 202012
  • 202106
  • 202111
  • 202205
  • 202211
  • 202305

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)

Signed-off-by: saksarav <sakthivadivu.saravanaraj@nokia.com>
@mssonicbld
Copy link
Collaborator

/azp run Azure.sonic-buildimage

Copy link

Azure Pipelines successfully started running 1 pipeline(s).

@saksarav-nokia
Copy link
Contributor Author

@vmittal-msft for viz

@@ -1477,6 +1477,7 @@ protocol_traps_mode.BCM8885X=IN_LIF
rate_ext_mdio_divisor=16
schan_intr_enable.BCM8885X=0
schan_timeout_usec.BCM8885X=900000
system_ref_core_clock_khz.BCM8885X=1600000
Copy link
Contributor

Choose a reason for hiding this comment

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

i think we only need to update on fabric side ?

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 think we only need to update on fabric side ?

@vmittal-msft , We were using default value which is 1.6GHZ and we are explicitly setting the same value for J2C+ now.

Copy link
Contributor

Choose a reason for hiding this comment

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

Thanks. @saksarav-nokia Could you run whole test suite as well as some level of ixia testing to make sure this is not causing any new issues ?

@arlakshm arlakshm removed the request for review from kenneth-arista February 20, 2025 18:09
@vmittal-msft vmittal-msft added the P0 Priority of the issue label Feb 20, 2025
@rlhui
Copy link
Contributor

rlhui commented Feb 21, 2025

@vmittal-msft is there a msft ado for this? thanks.

Copy link
Contributor

@arlakshm arlakshm left a comment

Choose a reason for hiding this comment

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

lgtm

@vmittal-msft
Copy link
Contributor

MSFT ADO # 31413977

@mssonicbld
Copy link
Collaborator

Cherry-pick PR to msft-202405: Azure/sonic-buildimage-msft#670

ram25794 pushed a commit to ram25794/sonic-buildimage that referenced this pull request Feb 21, 2025
Why I did it
Changed the clock frequency as per BCM's recommendation

Work item tracking
Microsoft ADO (number only):
How I did it
Changed the clock frequency to 1.6GHZ for both Ramons and J2C+

How to verify it
Verified in our Nokia system testbed that the system is up and passing the traffic without any issues.
# for free to join this conversation on GitHub. Already have an account? # to comment
Projects
Status: Done
Development

Successfully merging this pull request may close these issues.

6 participants