- play_arrow Overview
- play_arrow Precision Time Protocol
- play_arrow Precision Time Protocol Overview
- play_arrow Precision Time Protocol Clocks
- PTP Boundary Clock Overview
- Example: Configure PTP Boundary Clock
- Example: Configure PTP Boundary Clock With Unicast Negotiation
- Configure PTP TimeTransmitter Clock
- Configure PTP TimeReceiver Clock
- Example: Configure Ordinary TimeReceiver Clock With Unicast-Negotiation
- Example: Configure Ordinary TimeReceiver Clock Without Unicast-Negotiation
- PTP Transparent Clocks
- Configure PTP Transparent Clock
- play_arrow Precision Time Protocol Profiles
- play_arrow PHY Timestamping
- play_arrow Precision Time Protocol over Ethernet
- PTP over Ethernet Overview
- Guidelines to Configure PTP over Ethernet
- Configure PTP Dynamic Ports for Ethernet Encapsulation
- Configure PTP Multicast TimeTransmitter and TimeReceiver Ports for Ethernet Encapsulation
- Example: Configure PTP over Ethernet for Multicast TimeTransmitter, TimeReceiver, and Dynamic Ports
- play_arrow Precision Time Protocol Additional Features
- Precision Time Protocol (PTP) over Link Aggregation Group (LAG)
- Precision Time Protocol (PTP) Trace Overview
- Line Card Redundancy for PTP
- Timing Defects and Event Management on Routing Platforms
- SNMP MIB for Timing on Routing Platforms
- PTP Passive Port Performance Monitoring on PTX10004 and PTX10008 Devices
-
- play_arrow Global Navigation Satellite System (GNSS)
- play_arrow GPS Systems on Routing Platforms
- play_arrow Integrated GNSS on Routing Platforms
- play_arrow GNSS Configuration for Routers Using External GNSS Receiver
- play_arrow Assisted Partial Timing Support (APTS) on Routing Platforms
-
- play_arrow Network Time Protocol
- play_arrow NTP Concepts
- play_arrow NTP Configuration Examples
-
- play_arrow Synchronous Ethernet
- play_arrow Synchronous Ethernet Overview
- play_arrow Synchronous Ethernet on 10-Gigabit Ethernet MIC
-
- play_arrow Clock Synchronization
- play_arrow Clock Synchronization Concepts
- play_arrow Clock Synchronization for ACX Series Routers
- play_arrow Clock Synchronization for MX Series Routers
- play_arrow Clock Synchronization for PTX Series Routers
- play_arrow Centralized Clocking
-
- play_arrow Hybrid Mode
- play_arrow Hybrid Mode Overview
- play_arrow Hybrid Mode and ESMC Quality-Level Mapping
- Configure Hybrid Mode and ESMC Quality-Level Mapping Overview
- Configure Hybrid Mode with Mapping of the PTP Clock Class to the ESMC Quality-Level
- Configure Hybrid Mode with a User-Defined Mapping of the PTP Clock Class to the ESMC Quality-Level
- Example: Configure Hybrid Mode and ESMC Quality-Level Mapping on ACX Series Router
- Example: Configure Hybrid Mode and ESMC Quality-Level Mapping on MX240 Router
-
- play_arrow Configuration Statements and Operational Commands
- play_arrow Appendix
Understanding Transparent Clocks in Precision Time Protocol
The Precision Time Protocol (PTP) standardized by IEEE 1588 improves the current methods of synchronization used within a distributed network. You can use PTP across packet-based networks including, but not limited to, Ethernet networks. Queuing and buffering delays in the switch can cause variable delay to packets, which affects path delay measurements. Queuing delays vary based on the network load and also depend on the architecture of the switch or the router.
Transparent clocks measure and adjust for packet delay. The transparent clock computes the variable delay as the PTP packets pass through the switch or the router.
The QFX5100, EX4600, ACX5048, ACX5096, ACX6360-OR, and PTX10001-20C devices act as transparent clocks only and operate between the primary and client clocks in a distributed network. Transparent clocks improve synchronization between the primary and client clocks and ensure that the primary and client clocks are not impacted by the effects of packet delay variation. The transparent clock measures the residence time (the time that the packet spends passing through the switch or the router), and adds the residence time into the correction field of the PTP packet. The client clock accounts for the packet delay by using both the timestamp of when it started and the information in the correction field.
ACX5048 , ACX5096, ACX6360-OR, and PTX10001-20C devices support end-to-end transparent clocks. With an end-to-end transparent clock, only the residence time is included in the correction field of the PTP packets. The residence timestamps are sent in one packet as a one-step process. In a two-step process, which is not supported on ACX6360-OR, and PTX10001-20C devices, estimated timestamps are sent in one packet, and additional packets contain updated timestamps.
ACX5048 , ACX5096, ACX6360-OR, and PTX10001-20C devices support only the one-step process, which means that the timestamps are sent in one packet.
You can enable or disable a transparent clock globally for the switch or router. With a global configuration, the same configuration is applied to each interface. If the transparent clock is disabled, PTP packet correction fields are not updated. If the transparent clock is enabled, the PTP packet correction fields are updated.
On QFX5100, EX4600, and EX4400 switches, PTP over Ethernet, IPv4, IPv6, unicast, and multicast for transparent clocks are supported. EX4400 switches also support IRB and LAG.
ACX5048 and ACX5096 routers do not support PTP over IPv6 for transparent clocks.
ACX6360-OR, PTX10001-20C, and PTX10001-36MR devices support PTP over IPv6 for transparent clocks.
ACX5048 and ACX5096 routers do not support the following:
Boundary clock
Ordinary clock
Transparent clock over MPLS switched path
Transparent clock with more than two VLAN tags
ACX6360-OR and PTX10001-20C devices do not support the following:
Boundary, ordinary, primary, and client clocks
Transparent clock over MPLS switched path
Transparent clock with more than two VLAN tags
PTP over Ethernet
PTP over IPv4
PTP multicast mode
Configuration of unicast and broadcast modes.
Unicast mode is enabled by default.
Transparent clock in transponder mode
PTP while MACSec is enabled
Two-step process
You might notice higher latency when you use copper SFP ports instead of fiber SFP ports. In this case, you must compensate the latency introduced by the copper SFP ports for the accurate CF (correction factor) measurement.