The clients synchronize their times from the Grand-Master (GM) clock using the IEEE 1588 PTP message exchange. While there are various different stages to synchronize the clock (eg. frequency sync, time jumps, phase lock etc), the effect of these operations can be seen on the local-clock of the client being synchronized.
Essentially, the GM sends periodic Sync messages at a pre-determined and nominal rate eg. 1 packet per second (pps), or 8 pps and timestamps these messages with a T1 timestamp. The accuracy of this timestamp is extremely important so that the client can get its clock as close as possible. When each Sync message arrives at the client, it is timestamped with a T2 timestamp on the local system.
The raw difference between T2 and T1 is the clock-offset between a GM and the client, however, there are other means used to measure, estimate and compensate for the path-delay also. With the path-delay estimation, the client adjusts its local clock and tries to bring T2 as close to T1 as possible.
Here, on this page, if you have the raw-data or logs from which T1 and T2 timestamps are available, you can actually visualize how the clock got synchronized from the beginning of the protocol-exchange or even how it is behaving in a steady state or during network-disturbances.
This tool requires the T1 and T2 in a very simple comma-separated values (csv) format as shown below:
PTP Clock Sync Visualizer
Please choose the CSV data file you’d like to visualize here.