starlingx/docs
Code Issues Proposed changes
docs/doc/source/system_configuration/kubernetes/gnss-and-synce-support-62004dc97f3e.rst
Ron Stone 3b8299cf2c PTP GNSS and SyncE Support (dsR6*) 
Updates/additions to:
-System Config PTP section
-Guest Integration
-Admin Tasks
-Updates and Upgrades
Additional examples for T-BC
Incorporated patchset 3 review comments.
Added Limitations section.
Integrated patchset 5 comments.
Remove PTP Instance Removal - moved to RNs.

*Do not pick 100.019 alarm update to r6

Story: 2009130

Signed-off-by: Ron Stone <ronald.stone@windriver.com>
Change-Id: Ibdf449fe1d7282302d9be6d90e1c1b6dd70456b4
2022-03-30 17:34:41 +00:00

3.0 KiB
Raw Blame History

SyncE and Introduction

Intel's Westport Channel NICs support a built-in GNSS module and the ability to distribute clock via Synchronous Ethernet (SyncE). This feature allows a PPS signal to be taken in via the GNSS module and redistributed to additional NICs on the same host or on different hosts. This behavior is configured on using the clock instance type in the configuration. Many of the configuration steps in this section are similar to those in the Configuration section - reference this for additional details if required.

Important

Users should reference the user guide for their Westport Channel NIC for additional information on configuring these features. The intent of this section is to explain how these parameters can be set, rather than describing each possible configuration.

Basic 'clock' instance configuration

General 'clock' information

Default global parameters

There are no supported global parameters for the clock type

Default interface parameters

NONE

Required user-supplied parameters

NONE

Other requirements

The clock type instance is a special instance used for configuring the NIC control parameters of the Westport Channel NIC.

Configure a 'clock' instance

  1. Create the instance.

    ~(keystone_admin)]$ system ptp-instance-add myclock1 clock

  2. Create an interface for myclock1.

    ~(keystone_admin)]$ system ptp-interface-add clockint1 myclock1

  3. Add a port to the interface.

    ~(keystone_admin)]$ system host-if-ptp-assign controller-0 oam0 clockint1

  4. Add parameters to the interface.

    ~(keystone_admin)]$ system ptp-interface-parameter-add clockint1 sma1=output

  5. Assign the instance to a host.

    ~(keystone_admin)]$ system host-ptp-instance-assign controller-0 myclock1

  6. Apply the configuration.

    ~(keystone_admin)]$ system ptp-instance-apply

Clock interface parameters

Note

All parameters are scoped to the entire NIC, except for synce_rclka and synce_rclkb. This means that if sma1=input is applied to ens1f0 and sma1=output is applied to ens1f2, they will override each other and the last one processed by the system will be applied. Only the synce_rclka and synce_rclkb parameters can be configured per-interface. See the NIC user guide document for additional details.

Note

The absence of a parameter is treated as disabled.

The following parameters can be applied to the interface of a clock instance.

PTP Parameters:

  • sma1=input
  • sma1=output
  • sma2=input
  • sma2=output
  • u.fl1=output
  • u.fl2=input
  • synce_rclka=enabled
  • synce_rclkb=enabled