| Re: [chrony-users] Root delay and Root dispersion values in `chronyc ntpdata' |
[ Thread Index |
Date Index
| More chrony.tuxfamily.org/chrony-users Archives
]
- To: chrony-users@xxxxxxxxxxxxxxxxxxxx
- Subject: Re: [chrony-users] Root delay and Root dispersion values in `chronyc ntpdata'
- From: Horia Muntean <horia.muntean@xxxxxxxxx>
- Date: Mon, 26 Jun 2017 13:18:53 +0300
- Dkim-signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:in-reply-to:references:from:date:message-id:subject:to; bh=jdQqHfnjiHsmjq0JmksoRa9k1L4TkI8tGBkYPP2Aq3I=; b=i6puWK8AkYSzq2/o2nrxnRuhnfLAaVaHUSf77IjrlCUFjNd5XYDHxx99ukdIA+Ru7B HMjHggA9r2HWyCelKk66m+0fANJYVhHDUK/y9+X+wjG09O3kZm2W7x3cVBxCsTpjVDSn 9Z1pLIxnr/Kz7LNA3sXGJS1B4WZGIyeAhK/GgQKZCY7q4dceA/kuX36ysu+7SvNaWcSu QtXS40ySNJrbee2qtOOgDrPyJxFEdXb7cRTu4AedhWmB8haZ9Q/AR4EnPSr0OBHbrPhs XUkh5FpUjak3MbHn4EIyimIsQVtRrtHi8zIF25C6n2xmJy+dJSBPUGROXfeLuc4Xdu+g GW3w==
What are the reported values if you use the PTP hardware clock (PHC)
as a reference clock on the ntp server instead of SHM ? This way you
can get rid of the delays introduced by phc2sys (I suppose you use
ptp4l to synchronize the PHC to PTP grandmaster and then phc2sys to
synchronize the SHM to PHC).
On Mon, Jun 26, 2017 at 11:37 AM, Miroslav Lichvar <mlichvar@xxxxxxxxxx> wrote:
> On Fri, Jun 23, 2017 at 04:49:49PM -0400, Chris Perl wrote:
>> What I'm trying to understand is why on machine_b, I consistently see
>> a "Root delay" and "Root dispersion" of 15us in the output of `chronyc
>> ntpdata'. It doesn't vary, its always 15us.
>>
>> I've verified that the packets themselves flowing from server to
>> client have a "Root Delay" and a "Root dispersion" of 0 (via tcpdump),
>> so I'm guessing this must be getting calculated on the client, but I
>> can't figure out where or how.
>
> The root delay and dispersion fields printed by the ntpdata command
> are the values from the received packet. They should be the same as
> printed by tcpdump. Can you post tcpdump -v -x output?
>
> The reason why they are always 15 microseconds is that the fields have
> a 32-bit fixed-point format with ~15 microsecond resolution and
> chronyd as a server rounds them up. So, if it calculates its delay and
> dispersion as 1 microsecond, they will still be rounded to 15
> microseconds. It's a limitation of the NTPv4 protocol. I'd like to
> improve this in NTPv5 when the NTP WG starts working on a new version.
>
> If you wanted to get a more accurate root distance on the client, you
> could set the delay of the SHM refclock on the server to 0 and add
> half of the delay to the precision instead. I think it might have a
> small effect on the timekeeping performance though.
>
> --
> Miroslav Lichvar
>
> --
> To unsubscribe email chrony-users-request@xxxxxxxxxxxxxxxxxxxx
> with "unsubscribe" in the subject.
> For help email chrony-users-request@xxxxxxxxxxxxxxxxxxxx
> with "help" in the subject.
> Trouble? Email listmaster@xxxxxxxxxxxxxxxxxxxx.
>
--
To unsubscribe email chrony-users-request@xxxxxxxxxxxxxxxxxxxx
with "unsubscribe" in the subject.
For help email chrony-users-request@xxxxxxxxxxxxxxxxxxxx
with "help" in the subject.
Trouble? Email listmaster@xxxxxxxxxxxxxxxxxxxx.