Technical data

Configuring and Managing NTP
12.6 NTP Event Logging
12.6.1 Sample NTP Log File
The following sample shows an NTP log file:
16 Apr 16:36:30 ntpd version = 3-5.91
16 Apr 16:36:31 tickadj = 97, tick = 976, tvu_maxslew = 99231, est. hz = 1024
16 Apr 16:36:31 precision = 976 usec
16 Apr 16:36:33 read drift of 0 from TCPIP$NTP.DRIFT
16 Apr 16:43:00 synchronized to 16.20.208.100, stratum=2
16 Apr 16:43:00 time reset (slew) -62.810275 sec
16 Apr 16:43:00 synchronization lost
16 Apr 16:44:58 Previous time adjustment incomplete; residual -0.005758 sec
16 Apr 16:48:21 synchronized to 16.20.208.100, stratum=2
16 Apr 16:52:28 Previous time adjustment incomplete; residual -0.005270 sec
16 Apr 16:53:26 Previous time adjustment incomplete; residual -0.085888 sec
16 Apr 17:11:40 synchronized to 16.20.208.23, stratum=3
16 Apr 17:13:49 synchronized to 16.20.208.100, stratum=2
16 Apr 17:14:53 time reset (slew) -0.577109 sec
16 Apr 17:14:53 synchronization lost
16 Apr 17:21:38 synchronized to 16.20.208.23, stratum=3
16 Apr 17:26:54 synchronized to 16.20.208.100, stratum=2
16 Apr 17:35:24 offset: 0.033115 sec freq: -7.813 ppm poll: 1024 sec
16 Apr 17:46:23 synchronized to 16.20.208.97, stratum=3
16 Apr 17:47:28 Previous time adjustment incomplete; residual -0.000020 sec
16 Apr 17:49:32 Previous time adjustment incomplete; residual 0.093696 sec
16 Apr 17:49:36 Previous time adjustment incomplete; residual 0.003318 sec
16 Apr 17:52:08 Previous time adjustment incomplete; residual -0.049460 sec
16 Apr 17:52:24 Previous time adjustment incomplete; residual 0.003416 sec
16 Apr 17:53:28 Previous time adjustment incomplete; residual 0.000088 sec
16 Apr 18:06:10 time reset (slew) -0.218843 sec
16 Apr 18:06:11 synchronization lost
16 Apr 18:17:39 synchronized to 16.20.208.97, stratum=3
16 Apr 18:17:43 synchronized to 16.20.208.100, stratum=2
16 Apr 18:21:47 synchronized to 16.20.208.97, stratum=3
16 Apr 18:23:41 synchronized to 16.20.208.100, stratum=2
16 Apr 18:35:40 offset: -0.052522 sec freq: -7.839 ppm poll: 1024 sec
12.7 NTP Authentication Support
Authentication support is implemented using the MD5 algorithm to compute a
message digest. The servers involved in an association must agree on the key
and key identifier used to authenticate their messages.
Keys and related information are specified in a key file. Keys are used for:
• Ordinary NTP associations
• The NTPQ utility program
• The NTPDC utility program
Configuring and Managing NTP 12–13