Model: MTS200 (1U)
Doc. Ref. no. : - m08/om/201
Issue no.: 03
Page 121 of 195
User’s Manual
User can configure NTP broadcast Authentication via console based utility in Symmetric key mode only
and in Symmetric and Autokey authentication via webserver mode.
Broadcast Authentication
– Symmetric key:
Before configuring NTP Broadcast Authentication, user need to configure NTP main Authentication mode
to required Broadcast Authentication mode (SYMM / AUTO) for symmetric key and Autokey because ntp
driver can be configured only in one authentication mode either Symmetric key or Autokey, at a time for
complete ntp authentication and ntp broadcast authentication.
However, NTP broadcast Authentication is optional as user can set NTP main Authentication mode to
SYMM or AUTO but broadcast authentication can be made NONE if no authentication is required for NTP
broadcast/multicast, but it is recommended to always use ntp broadcast/multicast with either of
authentication technique.
1.
In Console based configuration utility: For configuration NTP broadcast / multicast with symmetric
key authentication, user need to set field “BCAST. Key” parameter to SYMM mode and “BCAST.
SYMM KeyID” parameter to applicable trusted key configured.
2.
In Webserver mode: For configuration NTP broadcast / multicast with symmetric key authentication,
user need
to set the field “Key Type” to “SYMMETRIC” and field “Key ID” to trusted key value as
shown in below figure.
Broadcast Authentication
– Autokey Mode:
Before using NTP Autokey (AUTO) authentication for NTP broadcast/multicast, user need to generate or
should have the ntpkeys in MTS200 for configured PC or IFF scheme. Please refer section 11.3.3.4 for
method for NTP Autokey Authentication process.
Broadcast
– NTP Client modificaitons:
1. For Broadcast without authentication :
User have to do below changes in client ntp.conf file for receiving ntp broadcast packets.
disable auth
broadcastclient yes
broadcastdelay 0.01
Ordinarily, upon receiving a message for the first time, the broadcast client measures the nominal server
propagation delay using a brief client/server exchange with the server, after which it continues in listen-
only mode. If the
broadcastdelay
command is not used, the default is 4.0 ms or user can specify their
own
broadcastdelay
depending on their network architecture.
2. For Broadcast with symmetic key authentication :
