Different NTP options on peers

[Stier, Matthew]

No need.  The NTP client will query all available NTP services and choose one to follow.  This query/choose continues as long as the client is running, so it knows it is getting the best time source available.  As the time service stabilize, the NTP client will slowly increase the time period between queries, to reduce the load on the NTP servers.  If there is a disruption, the client will simply reset to a short time period, and when thing settle down again, it will again, slowly increase the time period between queries.

Run ‘ntpq –p’ on your NTP client.  The ‘poll’ column is the time period between polling (On my systems, it is 1024 seconds).  The ‘when’ column is the number of seconds since the last poll of the system in the ‘remote’ column.  The asterisk in the first column, signifies the selected server.  A plus signifies a selected server.  A minus signifies a discarded server (good, but outside the balance of the selected servers) and a space signifies a system discarded for high stratum level.
From: dhcp-users-bounces at lists.isc.org [mailto:dhcp-users-bounces at lists.isc.org] On Behalf Of matt.southward at gmail.com
Sent: Tuesday, February 16, 2016 9:41 AM
To: dhcp-users at lists.isc.org
Subject: Different NTP options on peers

I have a pair of DHCP servers that specify 2 NTP servers for each pool. The pool definitions are exactly the same on each peer, and they are set to split 128. We have recently set up 2 additional NTP servers. I know the order of the NTP servers listed is in order of preference. Is there a recommended practice in order for load balancing the clients usage of the NTP servers? All of the NTP servers are the same strata. Does it make sense to define different NTP server options on each DHCP server? For example on DHCP1 use NTP1 and NTP2 and on DHCP2 use NTP3 and NTP4. Or does it make more sense to set the NTP servers in a round-robin fashion in pool definitions? For example pool1 defines NTP1, NTP2, NTP3, NTP4, then pool2 defines NTP2, NTP3, NTP4, NTP1, etc...
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.isc.org/pipermail/dhcp-users/attachments/20160216/ffd4a515/attachment-0001.html>