Interpreting NTP status

[Matthew Seaman]

On 2017/07/09 15:39, Carmel NY wrote:
> NTP status:
>      remote           refid      st t when poll reach   delay   offset  jitter
> ==============================================================================
> +198.55.111.50   133.157.29.35    3 u  760 1024  377   87.913    5.793  18.418
> *192.155.90.13   142.66.101.13    2 u  264 1024  377   45.449   -2.235   2.925
>  2607:fa18::2407 .STEP.          16 u    - 1024    0    0.000    0.000   0.000
> 
> I am hoping someone can tell me exactly what this means. I cannot find
> any documentation on how to interpret this.

This is the output from 'ntpq -p'  It's described under the 'peers'
command in ntpq(8) for using ntpq interactively.

It shows what NTP servers you are synch'd to, how frequently you are
polling those servers, how well you are managing to communicate with
them, how long it takes an NTP query to do a round-trip to the servers
and how close your local clock is to your time sources.  The 'offset'
column is measured in milliseconds, so you are fairly well synched.

However, you only have two working servers -- you are unable to reach
the 3rd server possibly because you don't have IPv6 yet.  This means you
can't use the 'majority consensus' algorithm -- so if one of your
timesources drifted off, you have no way of knowing which is right and
which is wrong.

	Cheers,

	Matthew


-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 972 bytes
Desc: OpenPGP digital signature
URL: <http://lists.freebsd.org/pipermail/freebsd-questions/attachments/20170710/89c3fd1a/attachment.sig>