HP-UX Internet Services Administrator's Guide (February 2007)

NTP Associations
Each NTP daemon must form an association with a time source: a higher-level (lower
stratum) server for stratum-1 servers, or an external clock. NTP daemons can form
additional associations with peer servers. Use the following command to list the NTP
associations established by the local NTP daemon:
/usr/sbin/ntpq -p
In the output, an asterisk (*) must appear next to the node name to indicate that an
association has been formed.
Table 4-8 indicates that the local NTP daemon has established an association with the
NTP daemon on node good.cup.hp.
Table 4-8 An ntpq Output Indicating NTP Associations
dispoffsetdelayreachpollwhenstrefidremote
====================================================================
16.40-0.165.4337764292LOCAL(1)*good.cup.hp
06431-0.0.0.0bad
If the local node is unable to form an association with its higher-level server or its peer,
you must login to the higher-level server or peer and issue the following command:
/usr/sbin/ntpq -p
Verify whether the higher-level server or peer has established an association with a
time source.
Query with Debug Option
If you cannot form an association with a server or peer, stop the local xntpd and send
a time request to the server or peer using the ntpdate command and the debug (-d)
option, as shown in the following example:
#/sbin/init.d/xntpd stop
#/usr/sbin/ntpdate -d server
The debug (-d) option prints information about the requests sent to the remote xntpd
daemon, and the information returned by the remote xntpd. The ntpdate command
fails if xntpd is already running on the local system. Also, the ntpdate command
does not use authentication; therefore, it must be executable only by the root.
You can also use ntpdate on systems where exact time synchronization is not
necessary. You can run ntpdate periodically from cron to synchronize the local clock
Troubleshooting NTP 73