Time synchronization Architecture and strategies
66 U41855-J-Z125-3-76
Time synchronization of the SU with an NTP server
If a server with a more accurate system time can be reached over the network
MANPU/MONPU, the local system time can be synchronized with this server using NTP
(Network Time Protocol). As soon as the administrator has entered this server as the MUs
NTP server, an NTP process starts which periodically adjusts the local time to the NTP
server’s time:
● If at startup time a deviation of more than 0.1 seconds exists, the process sets the time
absolutely precisely (accurate to the millisecond).
● In the subsequent time comparison, any time differences are adjusted relatively
precisely. The local time thus remains accurate to within a few milliseconds.
This process is restarted if the NTP configuration or the accessibility of the NTP server
changes (e.g. reachable again after a connection failure).
By and large it is sufficient to configure one (external) NTP server on the MU.
Figure 13: SE300 with external time synchronization
The SE Manager displays the current NTP configuration, see section “Setting the system
time (time synchronization or local)” on page 214. In addition to the status and the current
time difference, the accuracy of the NTP server‘s time is also displayed. The accuracy of
the NTP server’s time, the NTP server quality stratum, is specified in quality levels from 1
to 15. The best NTP server quality level 1 has a radio clock.
The administrator can also enter more than one NTP server. In this case the NTP process
selects a server which is currently accessible and has the most accurate time.
SU x86
BS2000
System time
X2000 SVP clock,
Linux System time
MU
Linux
Linux System time
AU
Linux (default)
Linux System time
MANPU
MCNPR
NTP
server
TODR
To Next Page
Loading...
Need help?
General