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.
NOTE: When you toggle from a secure slave to an automatic slave or vice
versa in the PTP configuration of a boundary clock, you need to delete the
existing PTP configuration and issue the commit command, and then you
add a new PTP configuration and issue the commit command.
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
247Copyright © 2017, Juniper Networks, Inc.
Chapter 9: Configuring Timing and Synchronization