Model: MTS200 (1U)
Doc. Ref. no. : - m08/om/201
Issue no.: 03
Page 137 of 195
User’s Manual
Now, user should close the SSH session with MTS200, as given below command:
exit
Now, at NTP client side, user should enter in folder where ntp client autokey files are generated.
cd /etc/ntp
and then,
ln
–s /path*/ntpkey_iffkey_MTS200 ntpkey_iffkey_username*
here, username = is the username of the ntp client unix or linux system
path* = is the path of folder where MTS200 trusted server IFF key is present
e.g.
ln
–s /etc/ntp/ntpkey_iffkey_MTS200 ntpkey_iffkey_ubuntu
Step 2:
Once, key is transferred to ntp clients and links made as per step1, user should configure ntp
client
ntp.conf
file for NTP Autokey IFF scheme as explained below.
First, add below lines in
ntp.conf
file.
crypto pw cryptppasswd #keys password
keysdir /etc/ntp
# directory where autokey is stored
crypto randfile /dev/urandom
server 192.168.100.153 minpoll 6 autokey
cryptopasswd = in ntp.conf file is the password used to generate the NTP IFF Autokeys in ntp
clients.
keysdir = is the directory in ntp clients where all IFF schemes related keys are stored.
User need to add “autokey” keyword in server address line in client ntp.conf which will ensure the
ntp communications between MTS200 and ntp client is through IFF based Autokey.
INFORMATION
User should only transfer IFF group key from MTS200 trusted server to
other group members. Other keys of certificate and private key of
MTS200 trusted server is not required by other group members.
After changes to NTP Autokey IFF parameters are done, NTP service
need to be restarted at ntp client side by user.
NTP takes few minutes to get synchronized when using Autokey
authentication and also depending on time difference between NTP
server and NTP client.
NTP client will only sync with NTP server with autokey keys only if
password and autokey options in ntp.conf file are correct as per
server and ntp service at client side is restarted after keys setup done
at client side.
