starlingx/docs
Code Issues Proposed changes
Files
460a9b159cdbe5cfd455fc80cdc8ff09f99d5b56
docs/doc/source/system_configuration/kubernetes/configuring-ptp-service-using-horizon.rst
Stone ecae991cca System Configuration reorg 
Organized SysConf Kubernetes and OpenStack content into subdirs and modified
index along lines of Planning layout.

Signed-off-by: Stone <ronald.stone@windriver.com>
Change-Id: Ia17c015b2083a39fcae4ac545fa10cb5445b4cb2
2021-01-29 09:41:28 -05:00

3.7 KiB
Raw Blame History

Configure PTP Service Using Horizon

The is a protocol used to synchronize clocks in a network. You can use the Horizon Web interface to configure these services on the host.

provides more accurate time synchronization than . typically provides time synchronization accuracy on the order of milliseconds, while provides time synchronization accuracy on the order of microseconds.

A master must be present on the Network, broadcasting time messages.

Note

and are configured per host. Lock/unlock the host when updating clock_synchronization for the host.

Review the Fault Management page and ensure that any existing system alarms are cleared.

  1. In the Horizon, open the System Configuration page.

    The System Configuration page is available from Admin > Platform > System Configuration in the left-hand pane.

  2. Select the tab.

    The page appears.

  3. Click Edit PTP. Update the configuration of the service.

    • PTP Time Stamping Mode: Hardware time stamping is the default option, and achieves best time syncing.

    • PTP Network Transport: Switch between IEEE 802.3 network transport (L2) or IPv4/v6 network transport for messaging.

      Note

      L2 is the default option.

      If you use for transport, each interface must have an IP assigned. This is enforced during host unlock, and when switching transport to .

    • PTP Delay Mechanism

      Set the delay mechanism, the options are:

      • E2E: default delay request-response
      • P2P: peer delay

  4. Click Save.

    This raises 250.001 Configuration out-of-date alarms against the controllers, workers, and storages nodes. You can view the alarms on the Fault Management page.

  5. Lock and unlock the controllers, workers, and storage nodes to apply the configuration and clear the Configuration out-of-date alarms.

    Open the Host Inventory page, available from Admin > Platform > Host Inventory in the left-hand pane, and then select the Hosts tab. Hosts requiring attention are shown with the status Config out-of-date.

    To lock or unlock a host, click the Action Menu down arrow for the host and then use the menu selections.

    1. Lock the standby controller.

      Wait for the lock operation to be completed.

    2. Unlock the standby controller.

      Wait for the host to become available. Its configuration is updated, and its error message is cleared.

    3. Perform a swact on the active controller.

      Click Action Menu (down arrow) > Swact Host > for the active controller.

      Horizon Web interface access is interrupted, and the login screen appears. Wait briefly for the Web service to stabilize, and then log in again.

    4. Lock the original controller (now in standby mode).

      Wait for the lock operation to be completed.

    5. Unlock the original controller.

      Wait for it to become available. Its configuration is updated, and its error message is cleared.

  6. Ensure that the Configuration out-of-date alarms are cleared for both controllers.