NTP sample scenarios
This first scenario would be used when configuring a single host to
use NTP.
The host seattle.mynet.com is expected to run as a stratum 2 server
because it is configured to get the time from two time servers with
radio clocks,
ntp1.ossi.com and ntp.olivetti.com.
The xntpd daemon stores the frequency error of the
clock on seattle.mynet.com in /etc/driftfile.
This is a good example to use if you just want to get xntpd
up and running quickly.
Note that it can take a day or two for a host to
synchronize with a time server.
Here is the ntp.conf file for seattle.mynet.com:
# # Peer configuration for 132.147.246.11 (seattle.mynet.com) # peer 192.240.4.1 # ntp1.ossi.com peer 129.189.134.6 # ntp.olivetti.comdriftfile /etc/driftfile
This next scenario is the complete configuration for mynet.com. The configuration files here configure mynet.com to match the topology discussed in ``NTP guidelines''. All hosts can be configured dynamically with xntpd. There are no restrictions on which hosts can be designated as time servers in a given host's configuration file.
Here is the ntp.conf file for acapulco:
# # Peer configuration file for 132.147.246.16 (acapulco.mynet.com) # peer 128.115.14.97 # clock.llnl.gov peer 16.1.0.22 # clepsydra.dec.com peer seattle.mynet.com peer moscow.mynet.comHere is the ntp.keys file for acapulco:broadcast 132.147.246.255
driftfile /etc/ntp.drift resolver /etc/xntpres keys /etc/ntp.keys requestkey 65534 controlkey 65535
2313 M APassword 65534 M NoSecret 65535 M BadKeyHere is the ntp.conf file for seattle:
# # Peer configuration for seattle (132.147.246.11) # peer 129.189.134.6 # ntp.olivetti.com peer 192.240.4.1 # ntp1.ossi.com peer acapulco peer moscowHere is the ntp.keys file for seattle:broadcast 132.147.246.255
driftfile /etc/ntp.drift resolver /etc/xntpres keys /etc/ntp.keys requestkey 65534 controlkey 65535
2313 M APassword 65534 M NoSecret 65535 M BadKeyHere is the ntp.conf file for moscow:
# # Peer configuration file for 132.147.246.7 # moscow.mynet.com # peer 130.43.2.2 # apple.com peer 192.52.195.10 # norad.arc.nasa.gov peer seattle.mynet.com peer acapulco.mynet.comHere is the ntp.keys file for moscow:broadcast 132.147.246.255
driftfile /etc/ntp.drift resolver /etc/xntpres keys /etc/ntp.keys requestkey 65534 controlkey 65535
2313 M APassword 65534 M NoSecret 65535 M BadKeyHere is the ntp.conf file for chicago:
# Peer configuration used by all stratum 3 # servers at mynet.com # broadcastclient yes broadcastdelay 0.0500 driftfile /etc/ntp.drift resolver /etc/xntpres keys /etc/ntp.keys requestkey 65534 controlkey 65535Here is the ntp.keys file for chicago:
2313 M APassword 65534 M NoSecret 65535 M BadKey