1 |
Hello Everyone, |
2 |
|
3 |
A while back I was inquiring about the best way to have computers on |
4 |
the network synched. Long story short, we opted to go with an NTP |
5 |
server installed on one machine, and synching the rest of the machines |
6 |
against it. |
7 |
|
8 |
However, I am not sure if the NTP server is properly synched with the |
9 |
public stratum 2 server furthermore, it does not seem like the clients |
10 |
are synced with the base server: |
11 |
|
12 |
ntpq -p |
13 |
remote refid st t when poll reach delay offset jitter |
14 |
======================================================== |
15 |
*tick.nrc.com .GPS. 1 u 52h 36h 2 56.036 8.131 0.445 |
16 |
tock.nrc.com .INIT. 16 u - 36h 0 0.000 0.000 0.000 |
17 |
192.168.2.255 .BCST. 16 u - 1024 0 0.000 0.000 0.000 |
18 |
|
19 |
|
20 |
And one of the clients: |
21 |
|
22 |
ntpq -p |
23 |
remote refid st t when poll reach delay offset jitter |
24 |
======================================================== |
25 |
time.server 128.233.154.245 2 u 32 64 377 0.168 25539.9 40.427 |
26 |
|
27 |
I have to be honest, not sure what those fields mean, but when I manually check |
28 |
the machines using the date command, i see that clients are ~20 sec behind. |
29 |
|
30 |
Was wondering how to best manipulate sync given our reliance on an outside ntp |
31 |
server. We are not looking for nanosecond synching, but at least down |
32 |
to the second |
33 |
would be efficient. |
34 |
|
35 |
Finally, is "refid 128.233.154.245" on client's pointing to the |
36 |
outside stratum server normal |
37 |
behaviour? Shoild "refid" not be pointing to our NTP server? |
38 |
|
39 |
|
40 |
Your help is greatly appreciated, |
41 |
|
42 |
Nick. |