NTP authentication requires that the authentication keys configured for the server and the client be the
same. Besides, the authentication keys must be trusted keys. Otherwise, the clock of the client cannot
be synchronized with that of the server.
Configuring NTP authentication on the server
Table 1-12 Configure NTP authentication on the server
Operation
Enter system view
Enable NTP authentication
Configure an NTP
authentication key
Configure the specified key
as a trusted key
Enter VLAN interface view
Configure on
the NTP
broadcast
Associate
server
the specified
key with the
correspondi
Configure on
ng
the NTP
broadcast/m
multicast
ulticast client
server
The procedure for configuring NTP authentication on the server is the same as that on the client.
Besides, the client and the server must be configured with the same authentication key.
Command
system-view
ntp-service authentication
enable
ntp-service
authentication-keyid key-id
authentication-mode md5
value
ntp-service reliable
authentication-keyid key-id
interface Vlan-interface
vlan-id
ntp-service
broadcast-server
authentication-keyid key-id
ntp-service
multicast-server
authentication-keyid key-id
1-12
Description
—
Required
Disabled by default.
Required
By default, no NTP authentication
key is configured.
Required
By default, no trusted authentication
key is configured.
—
In NTP broadcast server mode
and NTP multicast server mode,
you
need
to
associate
specified
key
corresponding
broadcast/multicast client
You can associate an NTP
broadcast/multicast client with an
authentication
key
configuring NTP mode. You can
also
use
this
command
associate them after configuring
the NTP mode.
the
with
the
while
to
Need help?
Do you have a question about the 4210 9-Port and is the answer not in the manual?
Questions and answers