[ntp:questions] Remaining synced on an unsynchronised peer?

michael.buetow at comsoft.de michael.buetow at comsoft.de
Tue Dec 1 10:44:56 UTC 2009


On 1 Dez., 11:10, Dave Hart <daveh... at gmail.com> wrote:
> In another message you mentioned seeing reach alternate between 376
> and 377 on the symmetric ("peer") association.  That is normal for
> symmetric mode and does not indicate a reachability issue.  Anything
> other than 376 or 377 indicates at least one missing packet, once
> primed.

Thanks for that explanation.

> ntpd which has reached 0 reachability for all its sources should be
> responding with a root dispersion well over the 1s threshold and be
> distrusted by downstream ntpds.  Assuming no orphan-mode
> configuration, it is not clear to me if the stratum is supposed to go
> the maximum and the synchronization (leap bits) to 11, or if they are
> expected to remain at the last values with only the root dispersion to
> indicate the problem.

As soon as I have the test resource I will double-check what I get.

> I pick a nit about calling a ntpd unsynchronized as soon as its
> sources are severed.  

Good point, I just used it for my lack of knowledge of a better
expression.
"Freewheeling" captures it well.




More information about the questions mailing list