NTP Log (Not Configurable)
The NTP log displays operational information about the NTP daemon, as well as NTP through-
put statistics (e.g., packets/sec.). Examples for entries in this log include indications for when
NTP was synchronized to its configured references (e.g., it became a Stratum1 time server), as
well as stratum level of the NTP references.
The NTP throughput statistics data can be utilized to calculate mean values and the standard
deviation.
Example log entries include:
Synchronized to (IP address), stratum=1: NTP is synchronizing to another Stratum 1 NTP
server.
ntp exiting on signal 15: This log entry indicates NTP is now indicating to the network that
it is a Stratum 15 time server because it is not synchronized to its selected reference.
Time reset xxxxx s: These entries indicate time corrections (in seconds) applied to NTP.
No servers reachable: NTP cannot locate any of its configured NTP servers.
Synchronized to PPS(0), stratum=0: NTP is synchronized using the PPS reference clock
driver (which provides more stable NTP synchronization).
Oscillator Log
Displays log entries related to oscillator disciplining. Provides the calculated frequency error
periodically while synchronizing to a reference.
GPS Qualification Log
If SecureSync is connected to a GNSS antenna and is tracking satellites, this log contains a run-
ning hourly count of the number of GNSS satellites tracked each hour. This history data can be
used to determine if a GNSS reception problem exists and whether this is a continuous or inter-
mittent reception issue.
GNSS reception may be displayed as cyclic in nature. A cyclic 12 hour pattern of decreased
GNSS reception typically indicates that the GNSS antenna has an obstructed view of the hori-
zon. The GNSS satellites are in a 12-hour orbit, so if part of the sky is blocked by large obstruc-
tions, at the same time every day (at approximately 12 hour intervals), the GNSS reception
may be reduced or may vanish altogether. If this occurs, the antenna should be relocated to
afford it an unobstructed view of the sky.
Every hour (displayed in the log as UTC time), SecureSync counts the total number of satellites
that were tracked during that hour. The GNSS qualification log shows the number of satellites
that were tracked followed by the number of seconds that the particular number of satellites
were tracked during the hour (3600 seconds indicates a full hour). The number to the left of the
“=” sign indicates the number of satellites tracked and the number to the right of the “=” sign
indicates the number of seconds (out of a total of 3600 seconds in an hour) that the unit was
tracking that number of satellites. For example, “0=3600” indicates the unit was tracking 0 satel-
lites for the entire hour, while “0=2700 1=900” indicates the unit was tracking one satellite for
900 seconds, but for the remaining portion of the hour it was tracking zero satellites.
306
CHAPTER 4 • SecureSync User Reference Guide Rev. 26
4.5 Quality Management
To Next Page
Loading...
