Skip to content

TELCODOCS-2259: Add TP support for ARM dual-port OC #96925

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.

Sign up for GitHub

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

Merged
merged 1 commit into from
Sep 3, 2025
Merged

TELCODOCS-2259: Add TP support for ARM dual-port OC #96925

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion modules/nw-ptp-configuring-linuxptp-services-dual-port-oc.adoc
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -17,7 +17,7 @@ include::snippets/technology-preview.adoc[leveloffset=+1]
* Install the OpenShift CLI (`oc`).
* Log in as a user with `cluster-admin` privileges.
* Install the PTP Operator.
* The node uses an x86_64 architecture with a dual-port NIC.
* Check the hardware requirements for using your dual-port NIC as an ordinary clock with added redundancy. For further information, see "Using dual-port NICs to improve redundancy for PTP ordinary clocks".

.Procedure

Expand Down
22 changes: 18 additions & 4 deletions modules/ptp-dual-ports-oc.adoc
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -21,7 +21,21 @@ In this configuration, the ports in a dual-port NIC operate as follows:

* If both ports become faulty, the clock state moves to the `HOLDOVER` state, then the `FREERUN` state when the holdover timeout expires, before resyncing to a leader clock.

[NOTE]
====
You can configure PTP ordinary clocks with added redundancy on `x86` architecture nodes with dual-port NICs only.
====
[id="hardware-requirements_{context}"]
== Hardware requirements

You can configure PTP ordinary clocks with added redundancy on x86_64 or AArch64 architecture nodes.

For x86_64 architecture nodes, the nodes must feature dual-port NICs that support PTP and expose a single PTP hardware clock (PHC) per NIC, such as the Intel E810.

For AArch64 architecture nodes, you can use the following dual-port NICs only:

* NVIDIA ConnectX-7 series

* NVIDIA BlueField-3 series, in NIC mode

** You must configure the NVIDIA BlueField-3 series DPU in NIC mode before configuring the interface as an ordinary clock with improved redundancy. For further information about configuring NIC mode, see link:https://docs.nvidia.com/networking/display/bluefielddpubspv422/modes+of+operation#src-141856548_ModesofOperation-NICModeforBlueField-3[NIC Mode for BlueField-3] (NVIDIA documentation), link:https://docs.nvidia.com/networking/display/bluefieldbmcv2504/bluefield+managementink[BlueField Management] (NVIDIA documentation), and link:https://docs.nvidia.com/networking/display/bluefielddpuosv470/modes+of+operation#src-2821766680_ModesofOperation-ConfiguringNICModeonBlueField-3fromHostHIIUEFI[Configuring NIC Mode on BlueField-3 from Host BIOS HII UEFI Menu] (NVIDIA documentation).

** You must restart the card after changing to NIC mode. For more information about restarting the card, see link:https://docs.nvidia.com/doca/sdk/nvidia+bluefield+reset+and+reboot+procedures/index.html[NVIDIA BlueField Reset and Reboot Procedures] (NVIDIA documentation).

* Use the latest supported NVIDIA drivers and firmware to ensure proper PTP support and to expose a single PHC per NIC.