[ntp:questions] "ntpd[7602]: synchronized to"

E-Mail Sent to this address will be added to the BlackLists Null at BlackList.Anitech-Systems.invalid
Thu May 26 22:09:21 UTC 2011


Chuck Swiger wrote:
> Florin Andrei wrote:
>> I wish there was a way to "bind" several clients together.
>>  You know, tell them to make "group decisions" when
>>  following / unfollowing any servers - "y'all either
>>  follow the same server(s), or peer with each other when
>>  all servers are offline, but do it _all_together_".
>>  This would be very useful for a cluster.
>
> In which case, you might want to consider using NTP
>  broadcast/multicast for time sync instead:
>
>   http://doc.ntp.org/4.2.6p3/manyopt.html

That does appear to work fine when they can't contact
 any other NTP servers, and they use orphan mode.

 However, when they do have access to higher stratum servers,
  they don't select the same sys peer(s);

# e.g.
tos cohort 1 orphan 11
restrict source nomodify
keys "/etc/ntp.keys" # e.g. contains: 123 M YOUR_MD5_KEY
trustedkey 123
manycastserver 224.0.1.1
manycastclient 224.0.1.1 key 123 preempt prefer
multicastclient 224.0.1.1 key 123 preempt prefer
broadcastclient
server ntp.lan.corp.example.com key 123 iburst preempt prefer minpoll 9 # 8min Organization NTP Server
server ntp.wan.corp.example.net key 123 iburst preempt prefer minpoll 10 # 15min Organization NTP Server
server ntp.isp.example.net iburst minpoll 11 # 30min UpStream ISP Server
server ntp.os.example.com iburst minpoll 12 # 1hr OS Vendor Server
server us.pool.ntp.org iburst preempt minpoll 10 # 15min Regional NTP Pool Server

-- 
E-Mail Sent to this address <BlackList at Anitech-Systems.com>
  will be added to the BlackLists.




More information about the questions mailing list