Help us improve your experience.

Let us know what you think.

Do you have time for a two-minute survey?

Navigation

Supported Platforms

Configuring a PTP Master Boundary Clock

On an ACX Series router, a Precision Time Protocol (PTP) master boundary clock sends PTP messages to the clients (ordinary and boundary) so that they can establish their relative time offset from this master’s clock or clock reference. You cannot configure an ordinary master clock on an ACX Series Router. The master boundary clock synchronizes time through a boundary slave port. To configure a master boundary clock, you must include the boundary statement at the [edit protocols ptp clock-mode] hierarchy level and at least one master with the master statement and at least one slave with the slave statement at the [edit protocols ptp] hierarchy level.

To configure a PTP master boundary clock, complete the following tasks:

Configuring the PTP Master Boundary Clock Parameters

To configure the parameters of a PTP master boundary clock:

  1. Configure the clock mode.
    [edit protocols ptp]user@host# set clock-mode boundary
  2. Configure the master clock.
    [edit protocols ptp]user@host# edit master
  3. (Optional) Specify the log mean interval between announce messages—from 0 through 4. By default, one announce message is sent every two seconds. This configuration is used for manual clock clients. The master boundary clock sends announce messages to manual clock clients as specified in the announce-interval value.
    [edit protocols ptp master]user@host# set announce-interval announce-interval-value
  4. Configure the interface on which to respond to downstream PTP clients and slaves.
    [edit protocols ptp master]user@host# edit interface interface-name

    For details about configuring the parameters for the master boundary clock interface, see Configuring a PTP Master Boundary Clock Interface

  5. (Optional) Specify the maximum log mean interval between announce messages—from 0 through 4. The default value is 4.
    [edit protocols ptp master]user@host# set max-announce-interval max-announce-interval-value
  6. (Optional) Specify the maximum log mean interval between delay-response messages—from –7 through 4. The default value is 4.
    [edit protocols ptp master]user@host# set max-delay-response-interval max-delay-response-interval-value
  7. (Optional) Specify the maximum log mean interval between synchronization messages—from –7 through 4. The default value is 4.
    [edit protocols ptp master]user@host# set max-sync-interval max-sync-interval-value
  8. (Optional) Specify the minimum log mean interval between announce messages—from –0 through 4. The default value is 0.
    [edit protocols ptp master]user@host# set min-announce-interval min-announce-interval
  9. (Optional) Specify the minimum log mean interval between delay-response messages—from –7 through 4. The default value is –7.
    [edit protocols ptp master]user@host# set min-delay-response-interval min-delay-response-interval
  10. (Optional) Specify the minimum log mean interval between synchronization messages—from –7 through 4. The default value is –7.
    [edit protocols ptp master]user@host# set min-sync-interval min-sync-interval-value
  11. (Optional) Specify the log mean interval between synchronization messages—from –7 through 4. The default value is –6. This configuration is used for manual clock clients. The master boundary clock sends synchronization messages to manual clock clients as specified in the syn-interval-value statement.
    [edit protocols ptp master]user@host# set sync-interval sync-interval-value

After you have configured the PTP master boundary clock parameters, enter the commit command from configuration mode. To complete the configuration of the master boundary clock, complete Configuring a PTP Master Boundary Clock Interface.

Configuring a PTP Master Boundary Clock Interface

After you have configured the master boundary clock parameters, complete the configuration of the master boundary clock by configuring an interface to act in the role of the master clock.

To configure a PTP master boundary clock interface:

  1. Configure the interface on which to respond to downstream PTP slaves or clients.
    [edit protocols ptp master]user@host# edit interface interface-name

    Note: For the configuration to work, the interface you specify must be configured at the [edit interfaces interface-name] hierarchy level.

  2. On this interface, configure downstream PTP clients.
    [edit protocols ptp master interface interface-name]user@host# edit unicast-mode
  3. Configure the IP address of the remote PTP host, or configure a subnet mask so that any host belonging to that subnet can join the master clock. You can configure up to 512 clients for each master boundary clock.
    [edit protocols ptp master interface interface-name unicast-mode]user@host# edit clock-client ip-address

    Note: You can configure the maximum number of clients (512 ) in the following combination:

    • Automatic clients 256.
    • Manual and secure clients 256—Any combination of manual and secure clients is allowed as long as the combined total amounts to 256.
  4. Configure the IP address of the interface acting as the local PTP master.
    [edit protocols ptp master interface interface-name unicast-mode clock-client ip-address]user@host# set local-ip-address local-ip-address
  5. (Optional) When the unicast-negotiation statement is configured at the [edit protocols ptp] hierarchy level, configure a clock client to immediately receive announce and synchronization messages from the master boundary clock without unicast negotiation.
    [edit protocols ptp master interface interface-name unicast-mode clock-client ip-address local-ip-address local-ip-address]user@host# set manual
  6. Specify the encapsulation type for PTP packet transport—IPv4. This statement is mandatory.
    [edit protocols ptp master interface interface-name unicast-mode]user@host# set transport ipv4

After you have configured the PTP master clock interface, enter the commit command from configuration mode.

Published: 2013-07-23

Supported Platforms

Published: 2013-07-23