EndRun Meridian II, Руководство пользователя

Страница: 101 / 240

M e r i d i a n I I U s e r M a n u a l 80
C H A P T E R S E V E N
81 M e r i d i a n I I U s e r M a n u a l
N E T W O R K T I M E P R O T O C O L ( N T P )
multicastclient ff05::101
If you are not using MD5 authentication, you would add these lines:
disable auth
multicastclient 224.0.1.1
or for IPv6:
disable auth
multicastclient ff05::101
You may remove the line added previously in Unix-like Platforms: Basic NTP Client Setup :
server 192.168.1.120
or the authenticated version added in Unix-like Platforms: MD5 Authenticated NTP Client Setup :
server 192.168.1.120 key 1
Test Broadcast/Multicast
Restart
ntpd
to have it begin using Meridian II as a broadcast or multicast server. Use the NTP util-
ity
ntpq
to check that
ntpd
is able to communicate with Meridian II. After issuing the command
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 Meridian II
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 Meridian II 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.