Harlan Stenn wrote:
> Lose the local refclock.
> Use "orphan mode" instead.
> Orphan mode is documented in the Support web at support.ntp.org.
At risk of repeating myself way too often;
When you have a group of computers on a LAN configured for
orphan mode, and they lose contact with remote servers,
the LAN client/servers will follow each other around.
Then when the remote servers can be contacted again,
the remote servers are selected.
This appears to happen, even if there are a large number
of LAN anycast orphan machines, and only one remote server
(as opposed to the recommended 4 minimum), due to the
large dispersion that has built up while the LAN servers
were isolated, and chasing each other in orphan mode.
e.g. I use something similar to this on all PCs / Devices
# ALL (Clients and/or Servers)
tos cohort 1 orphan 11
restrict default limited kod nomodify notrap
restrict 127.0.0.1
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
multicastclient 224.0.1.1 key 123 preempt
broadcastclient
... and add Server, Pool, Peer and RefClock lines
to your Primary Server (& Secondary if you have one).
e.g. server 1.nokia.pool.ntp.org iburst preempt
pool 0.nokia.pool.ntp.org iburst preempt
peer ntpserver1.ntc.nokia.com iburst
peer ntp2.nsn.com iburst
--
E-Mail Sent to this address <[email protected]>
will be added to the BlackLists.
_______________________________________________
questions mailing list
[email protected]
http://lists.ntp.org/listinfo/questions
