Hello
* It's not possible to use timemaster to run a PTP master. The PTP clock will not be synchronized to the system clock. The NTPSHM servo can work only in one direction. With timemaster and ntpd/chrony it's always PHC->system clock. That much I almost deducted 😊 Timemaster seems too rigid. * My suggestion would be to dedicate a node in the cluster to work as a PTP master for the other nodes, configured manually with phc2sys and ptp4l. The PTP clock on the master node can be synchronized to the system clock using a weak PI servo, which can be synchronized with NTP That’s the plan! I would run that on server3. However, even after my manual configuration, the PHC clocls are like 90 seconds off. I need to be roughly within absolute time, but timestamps 90s off may be too much. Could you please suggest the syntax of the phc2sys and ptp4l commands to run on server3 (time master) and server1? I will edit my systemd services to match. Server3 talks to server1 via eth1, which is called eth3 on the other end, on server1. Because weak PI servo, or the constants I should use are not exactly self evident for a PTP beginner – and likewise for which algorithms will give the most accuracy. Based on my readings, I assume a stable jitter around 50 ns should be possible. Thanks
_______________________________________________ Linuxptp-users mailing list Linuxptp-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/linuxptp-users
