Skip to main content

3.6.9 Specifying the XSCF as an NTP Client


3.6.9 Specifying the XSCF as an NTP Client
To have the XSCF use an NTP server, configure the XSCF as an NTP client. By default, the XSCF does not act as an NTP client obtaining the time from an NTP server. To configure the XSCF as an NTP client, use the setntp command with the -s client option specified.
  1. Execute the showntp command to display the XSCF status as an NTP client.
XSCF> showntp -a
client : disable
server : enable
  1. Execute the setntp command to configure the XSCF as an NTP client.
XSCF> setntp -s client -c enable
Please reset the XSCF by rebootxscf to apply the ntp settings.
  1. Execute the rebootxscf command to reboot the XSCF.
XSCF> rebootxscf -a
The XSCF will be reset. Continue? [y|n] :y
  1. The XSCF session is disconnected at this time. Reconnect to the XSCF, and log in again.
  2. Execute the showntp command, and confirm that the XSCF is configured as the NTP client.
XSCF> showntp -a
client : enable
server : enable
Note - If the time difference between the XSCF and the NTP server reaches 1000 seconds (about 17 minutes) or more, the ntp daemon of the client XSCF stops. As a result, time synchronization with the NTP server becomes impossible. To check whether the ntp daemon is stopped, execute the showntp -l command. If "NTP is unavailable." appears, then the daemon is stopped.
To restart the ntp daemon, execute the rebootxscf command, which reboots the XSCF.
  1. When the ntp daemon is stopped
XSCF> showntp -l
NTP is unavailable.
  1. When the ntp daemon is operating
XSCF> showntp -l
remote refid st t when poll reach delay offset jitter
==============================================================================
*192.168.10.10 10.0.20.20 4 u 805 1024 377 19.429 0.083 0.917
127.127.1.0 .LOCL. 5 l 7 64 377 0.000 0.000 0.008
XSCF>