EndRun Tempus LX GPS, User Manual

Page: 35 / 116

T e m p u s L X G P S U s e r M a n u a l 22
C H A P T E R T H R E E
23 T e m p u s L X G P S U s e r M a n u a l
S E T T I N G U P N T P C L I E N T S O N U N I X - L I K E P L A T F O R M S
or the authenticated version added in MD5 Authenticated NTP Client Setup :
server 192.168.1.245 key 1
Re-start
ntpd
to have it begin using the Tempus LX as a broadcast or multicast server. Use the NTP
utility
ntpq
to check that
ntpd
is able to communicate with the Tempus LX. After issuing the com-
mand
ntpq
you will see the
ntpq
command prompt:
ntpq>
Use the command
peers
to display the NTP peers which your computer is using. One of them should be the Tempus LX
server which you have just configured. You should verify that it is being ‘reached’. (You may have
to continue issuing the peers command for a minute or two before you will see the ‘reach’ count
increment.)
If you are using authentication, you can verify that authentication is being used by issuing the com-
mand
associations
to display the characteristics of the client server associations. In the “auth” column of the display,
you should see “OK” for the row corresponding to the Tempus LX server. If you see “bad”, you
should wait a few minutes to be sure that there is a problem since “bad” is the initial state of this
setting. If the “bad” indication persists then you must check your configuration for errors. Typi-
cally this is due to a typing error in creating the /etc/ntp.keys file on the client that causes a mismatch
between the keys being used by the server and client. (If you transfer the file by
ftp
or
scp
, this
shouldn’t be a problem.) It is also possible to have a typing error in the /etc/ntp.conf file that causes
the needed key to not be included in the “trustedkey” list.