Yes, I these on the monitoring system. For all servers/peers.
Denny
> On Nov 14, 2016, at 05:35, Miroslav Lichvar wrote:
>
> Do you see in measurements.log any entries with 'D K' and
> '111 111 ' in the columns with tests results (i.e. were any 'D K'
> measurements used for synchronization
On Sat, Nov 12, 2016 at 10:36:55AM -0800, Denny Page wrote:
> Here is a reasonable visual representation of what I am seeing. The section
> on the left (before 8:00) is with hardware timestamping, while the section on
> the right is with software timestamping. maxdelaydevratio of 4 in both cases.
On Sat, Nov 12, 2016 at 10:36:55AM -0800, Denny Page wrote:
> Here is a reasonable visual representation of what I am seeing. The section
> on the left (before 8:00) is with hardware timestamping, while the section on
> the right is with software timestamping. maxdelaydevratio of 4 in both cases.
On Fri, Nov 11, 2016 at 10:06:25AM -0800, Denny Page wrote:
> Following is output from test 4. Please let me know if this gives you the
> information that you are looking for.
It does. Thanks.
> 2016-11-11T17:45:06Z ntp_io.c:657:(process_message) Received 48 bytes from
> 192.168.230.244:123 to
Here is a reasonable visual representation of what I am seeing. The section on
the left (before 8:00) is with hardware timestamping, while the section on the
right is with software timestamping. maxdelaydevratio of 4 in both cases.
I think I have a kernel/driver problem.
Denny
Miroslav,
These are representative samples of what I am seeing. These are all taken from
my dedicated monitoring system.
192.168.230.240 and 192.168.230.244 are hardware units on the switch.
192.168.230.245 is a locally attached hardware unit.
192.168.230.1 is a FreeBSD system running ntpd.
192.
The average offset is ~300ns. I would not expect there to be so much asymmetry
with the switch, but I suppose anything is possible. If I enable hardware time
stamps the offset jumps to ~2100ns.
Denny
> On Nov 11, 2016, at 02:22, Miroslav Lichvar wrote:
>
> This looks very good and I'm curiou
> On Nov 11, 2016, at 02:17, Miroslav Lichvar wrote:
>
> The mixed results in tests 3, 4 and 8 are not as expected, however.
> Can you please try running one of those tests with 'acquisitionport
> 1' in chrony.conf and post the debug output (after ./configure
> --enable-debug) showing few ex
Turns out that after I run it for longer period while, I see mixed D H and H H
for test 5 as well.
> On Nov 10, 2016, at 13:35, Denny Page wrote:
>
> test 5
> - hw stamps on for igb0
> - ntp servers attached via igb0 enabled, server attached via igb3 disabled
> - result: H H for both servers
On Thu, Nov 10, 2016 at 02:38:04PM -0800, Denny Page wrote:
> Things are working quite well with software timestamping.
>
> This is from my monitoring system:
> 210 Number of sources = 6
> Name/IP AddressNP NR Span Frequency Freq Skew Offset Std Dev
> ===
On Thu, Nov 10, 2016 at 01:35:22PM -0800, Denny Page wrote:
> Here is the test setup: 3 identical hardware NTP units. Two accessible via
> switch on igb0. One accessible vi igb3 as a directly connected IP point to
> point. Here are test results:
Thanks for running the tests, much appreciated. Cu
Things are working quite well with software timestamping.
This is from my monitoring system:
210 Number of sources = 6
MS Name/IP address Stratum Poll Reach LastRx Last sample
===
^? 192.168.230.240
Miroslav,
The kernel is 4.4.26. The problem appears to be hardware timestamping and
multiple interfaces.
Here is the test setup: 3 identical hardware NTP units. Two accessible via
switch on igb0. One accessible vi igb3 as a directly connected IP point to
point. Here are test results:
test 1
-
On Thu, Nov 10, 2016 at 11:25:31AM -0800, Denny Page wrote:
> Miroslav,
>
> And D H?
D means daemon, i.e. no SW or HW timestamp. The first one is for
transmit timestampt, the other one for receive timestamp. If only the
first entry in the log is like that, then it's ok. If not, something
is wrong
Miroslav,
And D H?
Denny
> On Nov 10, 2016, at 06:45, Miroslav Lichvar wrote:
>
> You can see if it's actually working in the measurements log. With SW
> timestamping the last two fields should be K K, with HW timestamping
> they should be H H.
>
101 - 115 of 115 matches
Mail list logo
