Ntp- Prefs - Microsemi SyncServer S200 User Manual

Web Interface
Upload Keys: Use this text field, with the BROWSE button, to enter the file path of the keys file.
Then click the UPLOAD button to load the keys to the SyncServer.
Download Keys: Press the Save As... button to save the Current Keys to your PC as a file.
After keys are generated, the user can select Key and a key number in the MD5 key field on
the NTP - Config page.
Note: Disregard the "Unable to Open Key File" message while the Current Keys field is
empty.

NTP- Prefs

The settings on this page determine whether the NTP daemon, once synchronized, can
report an unsynchronized state.
Out of the three following stages of operation, the NTP - Prefs settings only apply during the
Loss of All References stage:
1. Startup: Upon starting, before synchronizing with any NTP associations, the NTP dae-
mon reports to potential NTP clients that it is unsynchronized by setting leap indicator to
11 and stratum to 16.
2. Typical Operation: After synchronizing to an NTP association the NTP daemon uses leap
indicator and stratum normally. Leap indicator reports whether a leap event is pending
(usually 00 - no alarm). Stratum reports the stratum of the NTP daemon relative to the
system peer (system peer number + 1).
3. Loss of All References: If the NTP daemon cannot get the time from any association:
With Standard NTP Rules (Factory Default) The stratum and leap indicator remain
n
the same as they were in the Typical Operation stage. The system peer remains
the unchanged, but the reference time stamp isn't updated and the reach statistic
gradually decreases to zero.
With Override Behavior, if the estimated time error exceeds the Time Error Limit on
n
the TIMING - Holdover page, stratum reports 16 and leap indicator reports 11, as
they did during in the Startup stage.
After Loss of All References, if the NTP daemon synchronizes with an NTP association
again, it resumes Typical Operation.
Comments:
Given a pool of NTP associations from which to choose, an NTP client typically syn-
n
chronizes with the best one, and does not require Override Behavior to declare an unsyn-
chronized state.
Given a lack of NTP associations from which to choose, an NTP client may reject a Syn-
n
cServer with better timing accuracy and stability than itself, if Override Behavior is
enabled.
The SyncServer's NTP daemon can get time from a server, peer, broadcastclient, and
n
multicastclient associations.
Page 40..........................................................................997-01520-02 Rev. G2