S o n o m a U s e r M a n u a l
22
C H A P T E R T H R E E
23
S o n o m a 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 )
ntpq>
Use the command
peers
to display the NTP peers which your computer is using. One of them should be the Sonoma 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 incre-
ment.) If you have other peers configured, verify that the offset information for the Sonoma server
peer and your other peers is in agreement to within a few milliseconds, assuming that the other peers
are synchronized to that level of accuracy.
It may also be useful to start the NTP daemon in ‘debug’ mode (
ntpd -d
) to confirm successful con-
figuration. Refer to the NTP documentation for detailed usage of these debug utilities.
Unix-like Platforms: MD5 Authenticated NTP Client Setup
MD5 authenticated setup is relatively simple, if:
• You have been able to successfully communicate with the Sonoma on your network.
• Your Sonoma has been configured to perform authentication either by factory default, or by run-
ning the
ntpconfig
shell script. The example Sonoma authentication configuration shown in
Con-
figuring NTP Using the Network Interface or Serial Port
above, will be assumed in the example
configuration commands shown here.
• You have installed NTP on your client computer.
• You have successfully performed the
Unix-like Platforms: Basic NTP Client Setup
on your client
computer.
Create the ntp.keys File
You must create a file named
ntp.keys
in the
/etc
directory. It must be a copy of the one residing in
the
/etc
directory of your Sonoma. You can
telnet
into your Sonoma and start an
ftp
session with
your client computer to send the Sonoma’s
/etc/ntp.keys
file to your client computer, use the secure
copy utility
scp
, or you can just use a text editor on your client computer to create an equivalent file.
IMPORTANT
Handling of the
/etc/ntp.keys
file is the weak link in the MD5 authentication scheme. It is very impor-
tant that it is owned by
root
and not readable by anyone other than
root
.
After transferring the file by
ftp
, and placing it in the
/etc
directory on the client computer, issue
these two commands at the shell prompt:
chown root.root /etc/ntp.keys
chmod 600 /etc/ntp.keys
Summary of Contents for Sonoma N12
Page 2: ......
Page 16: ...S o n o m a U s e r M a n u a l This page intentionally left blank...
Page 20: ...S o n o m a U s e r M a n u a l 4 C H A P T E R O N E This page intentionally left blank...
Page 32: ...S o n o m a U s e r M a n u a l 16 C H A P T E R T W O This page intentionally left blank...
Page 48: ...S o n o m a U s e r M a n u a l 32 C H A P T E R T H R E E This page intentionally left blank...
Page 70: ...S o n o m a U s e r M a n u a l 54 C H A P T E R S I X This page intentionally left blank...
Page 82: ...S o n o m a U s e r M a n u a l 66 C H A P T E R S E V E N This page intentionally left blank...
Page 122: ...S o n o m a U s e r M a n u a l 106 A P P E N D I X A This page intentionally left blank...
Page 156: ...S o n o m a U s e r M a n u a l 140 A P P E N D I X E...
Page 158: ...S o n o m a U s e r M a n u a l 142 A P P E N D I X F This page intentionally left blank...
Page 168: ...S o n o m a U s e r M a n u a l 152 A P P E N D I X H...
Page 169: ...153 S o n o m a U s e r M a n u a l S P E C I F I C AT I O N S...
Page 170: ...S o n o m a U s e r M a n u a l 154 A P P E N D I X H This page intentionally left blank...
Page 173: ......