Help us improve your experience.

Let us know what you think.

Do you have time for a two-minute survey?

Example: Configuring an Ordinary Slave Clock Without Unicast-Negotiation


This example shows the base configuration of a Precision Time Protocol (PTP) ordinary client clock without unicast-negotiation on an ACX Series router.


ACX5048 and ACX5096 routers do not support ordinary clock.


This example uses the following hardware and software components:


This example also applies to QFX Series switches. QFX Series switches do not support Gigabit Ethernet interfaces. Instead, configure PTP boundary clock parameters on 10-Gigabit Ethernet interfaces.

  • One ACX Series router

  • Junos OS Release 12.2 or later


In this configuration, unicast-negotiation is not configured, so the PTP client has no control over the rate of the negotiation. The PTP master (a Brilliant Grand Master or an MX Series router) must be configured with the parameters of the PTP client, such as announce, synchronization, and delay-response packets to control the rate of the negotiation.


The values in this example are for illustration purposes only. You can set the values for each parameter according to your requirements.


To configure an ordinary client clock without unicast-negotiation, perform these tasks:


The ipv4-dscp statement is not supported on the QFX10002 switch.

CLI Quick Configuration

Configuring an ordinary client clock without unicast-negotiation

Step-by-Step Procedure

  1. Configure the clock mode:
  2. Configure the Differentiated Services code point (DSCP) value for all PTP IPv4 packets originated by the device:Note

    The ipv4-dscp 46 statement is not supported on QFX Series switches.

  3. Configure the client interface:
  4. Configure the unicast transport mode:
  5. Configure the clock source:
  6. Verify the configuration:

    See the output for the show command in the Results section.


In this example, the PTP client on the local interface ge-0/2/0 is assigned a local IP address of Unicast-negotiation is not configured so the PTP master must be explicitly configured with the details of the PTP client (