[ntp:questions] NTP.log interpretation

Jason Rabel jason at extremeoverclocking.com
Sat Apr 19 18:30:20 UTC 2014

> Orphan Mode is an automatic server discovery scheme. Nothing more.
> Orphan Mode does not make it possible for the members of a "time island"
> to determine the correct time in the absence of reference sources.
> Symmetric Active/Passive Mode (aka Peer Associations) allows the
> creation of a bidirectional link between two ntpd instances.
> In my experience, the ntpds in a peer association will ignore each other
> when they have the same sys_peer (i.e. when they are "synchronised" to
> the same source).
> And the Mitigation Rules do not provide special Peer Classification for
> Symmetric Active/Passive Mode.

Steve, the way I read it is that the tos ophan settings is a replacement for the local clock driver, so I tried to follow the image
of the peer network as shown on the page you linked.

Each of my S2s are synced to a different S1 (using the server line). But also each S2 has a peer line for the other two S2s and the
"tos orphan 5" line.

As a test I disconnected all S1s from the network and let things sit for a while to see what would happen. It has been a while but
if I recall correctly, the S2s dropped down to S5. I do not recall if each S2 chose another S2 as its primary source or what. But
they all continued to distribute time.

If that is configured wrong, then please tell me the correct way and I will happily fix it.

More information about the questions mailing list