Safran SecureSync 2400 User Manual page 346

4.5 Quality Management
Journal Log
Displays log entries created for all configuration changes that have occurred
(such as creating a new user account, for example).
NTP Log
The NTP log displays operational information about the NTP daemon, as well as
NTP throughput 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 Stratum 1 time server), as well as stratum level of the NTP ref-
erences.
The NTP throughput statistics data can be utilized to calculate mean values and
the standard deviation.
Example log entries include:
Oscillator Log
330
were not restored before the Holdover period expired (Time Sync alarm is
asserted).
In Sync: SecureSync is synchronized to its Time and 1PPS inputs.
Not In Sync: SecureSync is not synchronized to its Time and 1PPS inputs
and is not currently in Holdover. NTP will indicate to the network that it is
Stratum 15 and so the time server likely be ignored as a time reference.
Sending trap for event 1
SNMP agent to the SNMP Manager. The event number in this entry indic-
ates which SNMP trap was sent.
The Unit has Rebooted: SecureSync was either rebooted or power cycled.
Synchronized to (IP address),
Stratum 1 NTP server.
ntp exiting on signal
the network that it is a Stratum 15 time server because it is not syn-
chronized 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 serv-
ers.
Synchronized to PPS(0),
reference clock driver (which provides more stable NTP synchronization).
(SNMPSAD): An SNMP trap was sent by the
stratum=1: NTP is synchronizing to another
15: This log entry indicates NTP is now indicating to
stratum=0: NTP is synchronized using the PPS
CHAPTER •
4 SecureSync 2400 User Manual Rev. 5.2