On Fri, Aug 14, 2015 at 06:01:49PM +0000, Harold Lapprich wrote: > > Mlichvar, > > Working through the configuration issues needed for a PTP configuration to > auto-negotiate the GrandMaster at power-up that is receiving/suppling system > clock to a NTP/chronyd server. Want to create a configuration that is > autonomous and will recovery if the GrandMaster is ever taken out of service > (2 diagrams follow to provide clarity).
I'm not sure what issues are you having with the PTP master selection. The Best Master Clock algorithm, which selects the master, is always running in ptp4l. When the currently selected master disappears, a new master should be selected automatically. > It appears that the linuxptp applications (phc2sys, ptp4l, pmc, and > timemaster) can be configured to create an autonomous system, can you please > provide insight on how 'timemaster' and perhaps 'phc2sys' would need to be > configured? When using timemaster, you need just one configuration file and timemaster will generate configuration for all other programs involved (chrony/ntpd, ptp4l, phc2sys) and start them automatically. The timemaster man page has some examples. Assuming you want the system clock to be synchronized by chronyd, using a PTP domain as the only time source and serving time over NTP to clients, the timemaster configuration file could be: [ptp_domain 0] interfaces eth0 [chrony.conf] makestep 1 3 rtcsync allow driftfile /var/lib/chrony/drift -- Miroslav Lichvar ------------------------------------------------------------------------------ _______________________________________________ Linuxptp-users mailing list Linuxptp-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/linuxptp-users
