Setup guide

parallel client continues to look for more NTP servers by sending multicast messages
periodically.
Client
system ntp client
Property Description
enabled (yes | no; default: no) - whether the NTP client is enabled or not
mode (unicast | broadcast | multicast | manycast; default: unicast) - NTP client mode
primary-ntp (IP address; default: 0.0.0.0) - specifies IP address of the primary NTP server
secondary-ntp (IP address; default: 0.0.0.0) - specifies IP address of the secondary NTP server
status (read-only: text) - status of the NTP client:
stopped - NTP is not running (NTP is disabled)
error - there was some internal error starting NTP service (please, try to restart (disable and
enable) NTP service)
started - NTP client service is started, but NTP server is not found, yet
failed - NTP server sent invalid response to our NTP client (NTP server is not synchronized to
some other time source)
reached - NTP server contacted. Comparing local clock to NTP server's clock (duration of this
phase is approximately 30s)
timeset - local time changed to NTP server's time (duration of this phase is approximately 30s)
synchronized - local clock is synchronized to NTP server's clock. NTP server is activated
using-local-clock - using local clock as time source (server enabled while client disabled)
Example
To enable the NTP client to synchronize with the 159.148.60.2 server:
[admin@Wandy] system ntp client> set enabled=yes primary-ntp=159.148.60.2
[admin@Wandy] system ntp client> print
enabled: yes
mode: unicast
primary-ntp: 159.148.60.2
secondary-ntp: 0.0.0.0
status: synchronized
[admin@Wandy] system ntp client>
Server
system ntp server
Property Description
enabled (yes | no; default: no) - whether the NTP client is enabled
broadcast (yes | no; default: no) - whether NTP broadcast message is sent to 255.255.255.255
every 64s
multicast (yes | no; default: no) - whether NTP multicast message is sent to 224.0.1.1 every 64s
manycast (yes | no; default: yes) - whether NTP server listens for multicast messages sent to