Safran VersaSync - NTP Servers and Peers

Prefer Stratum1
Uncheck this option to prevent VersaSync's NTP service from “weigh-
ing” the Timing System input heavier than input from other NTP serv-
ers. Thus, during normal operation, the time provided by the external
Stratum1 NTP server will be used (unless its quality is determined to
be low).
Note: If enabled, this function would give GPS additional
“weight” for NTP to select the GNSS input over other
NTP Servers.
5. Click the Submit button.
2.8.11.8 NTP Servers and Peers
VersaSync can be configured to receive time from one or more available NTP
Servers (VersaSyncs or different models). This allows for NTP Servers on a timing
network to be configured as potential (fallback) input time references for Ver-
saSync System Time synchronization. In the event that a current reference
becomes unavailable, VersaSync can fallback to the other NTP Servers available
on the network.
A group of NTP servers at the same Stratum level (Stratum 1 time servers, for
example) are considered as NTP Peers to each other.
NTP Servers at a higher Stratum level, on the other hand, are called NTP Servers
(Note that Internet Time Servers should be configured as NTP Servers and not as
NTP Peers).
Note: IMPORTANT: In order for other NTP servers to be a valid ref-
erence, you must enable “NTP” in the Reference Priority table (see
"Configuring Input Reference Priorities" on page173).
For mutual fallback purposes, it is recommended to use one or more NTP Peers.
Each peer is normally configured to operate from one or more time sources
including reference clocks or other higher stratum servers. If a peer loses all ref-
erence clocks or fails, the other peers continue to provide time to other clients on
the network.
NTP Servers at the same Stratum level
118
CHAPTER 2 • VersaSync User Manual Rev. 12
2.8 Configuring Network Settings