| 1 |
On 25/04/13 23:07, Nick Khamis wrote: |
| 2 |
>> Ummm... *all* servers are critically time-sensitive. |
| 3 |
>> |
| 4 |
> |
| 5 |
> Yeah... I concur ;) |
| 6 |
> |
| 7 |
|
| 8 |
Define critical! - to my mind if its critical you should be running your |
| 9 |
own atomic clock, and something like a pps system to distribute it ... |
| 10 |
|
| 11 |
or somewhere in the middle a local gps receiver for time lock. |
| 12 |
|
| 13 |
Or do you mean reasonably accurate, but closely synced local systems? |
| 14 |
|
| 15 |
My interest after having a stable ntp based hierarchy for years is in |
| 16 |
trying to get the same using a cisco router and VMs' - not easy so far! |
| 17 |
When I used an ancient netgear adsl, and a linux firewall/ntp server it |
| 18 |
was very good, now ... |
| 19 |
|
| 20 |
Does anyone know a good guide to using time sync in VM's, for both |
| 21 |
windows and linux (gentoo) guests using libvirt? Especially for guests |
| 22 |
that are resumed, or the whole virtualisation system is hibernated? (ntp |
| 23 |
refuses to resync after guest pause/save/restore/resume (known problem), |
| 24 |
even with "tinker panic 0" |
| 25 |
|
| 26 |
My current setup is complicated by using a cisco router (adsl) as the |
| 27 |
localnet master via local (ISP/University) time servers - its rather |
| 28 |
inaccurate so while the machines are often "locked", its in rather |
| 29 |
relative terms :) |
| 30 |
|
| 31 |
|
| 32 |
|
| 33 |
ghost#sh ntp ass |
| 34 |
|
| 35 |
address ref clock st when poll reach delay offset |
| 36 |
disp |
| 37 |
+~130.95.128.36 210.9.192.50 2 44 64 377 11.9 -844.4 |
| 38 |
213.6 |
| 39 |
+~116.66.162.4 130.234.255.83 2 8 64 377 48.7 -907.5 |
| 40 |
213.3 |
| 41 |
+~203.0.178.191 43.128.117.84 2 23 64 377 12.2 -891.0 |
| 42 |
213.3 |
| 43 |
~192.168.48.1 134.115.4.33 3 9h39 64 0 17.3 -616.8 |
| 44 |
16000. |
| 45 |
*~27.54.95.11 218.100.43.70 2 42 64 377 12.7 -846.7 |
| 46 |
221.4 |
| 47 |
+~202.127.210.36 223.255.185.2 2 31 64 377 62.2 -845.3 |
| 48 |
211.2 |
| 49 |
+~130.102.128.23 132.163.4.101 2 38 64 377 77.3 -850.4 |
| 50 |
212.4 |
| 51 |
* master (synced), # master (unsynced), + selected, - candidate, ~ |
| 52 |
configured |
| 53 |
ghost# |
| 54 |
|
| 55 |
asterisk ~ # ntpq -p |
| 56 |
remote refid st t when poll reach delay offset |
| 57 |
jitter |
| 58 |
============================================================================== |
| 59 |
ghost.lan.local 27.54.95.11 3 u 64 64 377 1.386 2838.19 |
| 60 |
513.843 |
| 61 |
asterisk |
Archives