Tasks
5.
For MD5 Key, select the appropriate method, Key or Auto. (If selecting Key, also select a
key number, 1 through 16.)
6.
Click the SAVE button.
7.
Click the RESTART button. When the NTP daemon finishes restarting, it broadcasts NTP
messages every 64 seconds.
Configuring the Multicast Client
To configure an NTP client as a multicast client, consult the manufacturer's documentation.
To configure a generic NTP multicast client with MD5 authentication, the user would upload
the ntp.keys file to the /etc directory and add the following lines to the ntp.conf file (example
values italicized):
multicastclient 224.0.1.1
enable auth
keys /etc/ntp.keys
trustedkey 1
The key number identified by trustedkey must match the key number on the multicast server
association.
The SyncServer can also be configured as a multicast client, as follows:
1. Configure authentication.
n
For example, use NTP - MD5 to upload the keys file.
2.
Add or edit an association on the NTP - Conf page.
3.
For Role, select Multicast Client.
4.
For MD5, select the appropriate method and Key if needed.
5.
Click the SAVE button.
6.
Click the RESTART button. When the NTP daemon finishes restarting, it listens for broad-
cast messages.
Also see:
n Working with Generic NTP Devices (on page 160)
n Using MD5 Keys on a SyncServer (on page 161)
n Using NTP Authentication (on page 160)
ConfiguringNTPClients
The user typically configures an NTP clients to synchronize with the SyncServer.
If available, consult the manufacturer's documentation for instructions on how to do this.
For a generic NTP device, this can be accomplished by adding one or more server asso-
ciations to the ntp.conf file. For example:
server 192.168.61.50#NTP server 1
server 192.168.61.54#NTP server 2
server 192.168.61.58#NTP server 3
Save the changes and restart the device.
See Working with Generic NTP Devices (on page 160).
Page 158..........................................................................997-01520-02 Rev. F1
To Next Page
Loading...
