HP-UX Internet Services Administrator's Guide (August 2003)

Configuring NTP
Troubleshooting NTP
Chapter 492
Table 4-8 indicates that the local NTP daemon has established an
association with the NTP daemon on node good.cup.hp.
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 with the other system’s clock. For more
information, type man 1M ntpdate at the HP-UX prompt.
Error Messages
This section describes the error messages that you may encounter while
working with NTP.
Table 4-8 An ntpq Output Indicating NTP Associations
remote refid st when poll reach delay offset disp
====================================================================
*good.cup.hp LOCAL(1) 2 29 64 377 5.43 -0.16 16.40
bad 0.0.0.0 - 31 64 0