Renzo Marengo wrote:
In my wide area company with about 1000 clients, I organized ntp server
hierarchy in 2 levels:
level A - n.1 Physical Linux server (Centos 6) - SERVER MASTER
level B - n.3 Physical Linux server (Centos 6) - NTP1, NTP2, NTP3 (for clients)
Server MASTER retrieves time directly from servers of public newtwork.
Server NTP1, NTP2, NTP3 retrieves time from server MASTER and they are the
official NTP server used from clients.
What do you think about this ntp server structure? I know NTP server numbers
must be 1, 3 or 4,
I know ntp server must be a physical machine because its clock is more exact.
Right ?
When I did the same for Hydro (multi-national corporation with 77K
employees in 130 countries) I had 3 primary servers (running FreeBSD)
with GPS and external reference servers, plus one (in Germany) using the
DCF77 pseudo-random signal and anoterh in the US that used their cell
phone timing signal.
These master servers all referenced each other, in case their local S1
clock would fail.
Next I had 6 S2 servers (running Linux or FreeBSD) that listed every S1
server as a source, while every client server (a few K in number) simply
used the same config file listing all six S2 servers.
This setup never even hiccuped during the 10+ years I ran it.
Terje
--
-
"almost all programming can be viewed as an exercise in caching"
--
This is questions@lists.ntp.org
Subscribe: questions+subscr...@lists.ntp.org
Unsubscribe: questions+unsubscr...@lists.ntp.org
