Model: MTS200 (1U)
Doc. Ref. no. : m08/om/201
Issue no. : 03
User’s Manual
Page 192 of 195
Page 192 of 195
1) Autokey password used to generate autokey files at client side should be added in client
ntp.conf file. This password can be different from autokey password of MTS200 trusted
server.
2) NTP client ntp.conf is configured for disable authentication or symmetric key authentication.
3) NTP client ntp.conf is wrongly configured for autokey parameters.
4) NTP client ntp.conf server address of MTS200
should have “autokey” keyword appended in
its line.
5) Old keys not deleted at MTS200 side or ntp client side.
6) NTP service should be restarted at server and client side after configuration done.
7) Wrong autokey files transferred to ntp client
8) NTP client side autokey file names improper.
9) NTP client autokey files directory path and path defined in client ntp.conf should be same.
17.26 NTP Client Not synchronized with MTS200 using IFF scheme AutoKey
association with multiple MTS200 units.
Below options can be possible reasons affecting the process.
1) Autokey password used to generate autokey file, mismatch at MTS200 trusted server and
MTS200 as server side.
2) NTP autokey group key IFFkey contents of MTS200 as trusted server should be copied and
pasted as Group key contents of MTS200 as server only and other ntp clients.
3) Autokey password used to generate autokey files at client side should be added in client
ntp.conf file. This password can be different from autokey password of MTS200 trusted
server.
4) NTP client ntp.conf is configured for disable authentication or symmetric key authentication.
5) NTP client ntp.conf is wrongly configured for autokey parameters.
6) NTP client ntp.conf server address of MTS200
should have “autokey” keyword appended in
its line.
7) Old keys not deleted at MTS200 side or ntp client side.
8) NTP service should be restarted at all MTS200 servers and client side after configuration
done.
9) Wrong autokey files transferred to ntp client
10) NTP client side autokey file names improper.
11) NTP client autokey files directory path and path defined in client ntp.conf should be same.
17.27 NTP association between MTS200 and ntp clients working with old NTP
settings.
Below options can be possible reasons affecting the process.
1) NTP Service need to be restarted in MTS200 after any NTP related configurations change
done in MTS200.
2) NTP Service need to be restarted in NTP client after any NTP related configurations change
done.
17.28 NTP client not synchronize with NTP broadcast/Multicast frames from
MTS200.
Below options can be possible reasons affecting the process.
1) NTP service need to restarted in MTS200 after broadcast or multicast settings changes done
in MTS200 device.
