Displays log entries related to GNSS reception status changes, Sync/Holdover state changes,
SNMP traps being sent, etc. Examples include:
Reference Change: SecureSync has switched from one input reference to another (for
example, IRIG was the selected input being used, but now GNSS is the selected ref-
erence).
GPS Antenna Problem: The GPS Antenna Problem alarm indicates the GNSS receiver has
detected an over-current or undercurrent condition (an open or short exists in the GNSS
antenna cable, or the GNSS antenna is not connected to SecureSync). The receiver will
attempt to continue the normal acquisition and tracking process regardless of the
antenna status. The current draw measurements that will indicate an antenna problem
are:
Under-current indication < 8 mA
Over-current indication > 80 mA
Note: This alarm condition will also be present if a GNSS antenna splitter that
does not contain a load to simulate an antenna being present is being used.
GPS Antenna OK: The antenna coax cable was just connected or an open or short in the
antenna cable was being detected but is no longer being detected.
Frequency Error:The oscillator’s frequency was measured and the frequency error was
too large. Or, the frequency couldn’t be measured because a valid input reference was
not available.
Frequency Error cleared:The Frequency Error alarm was asserted but was then cleared.
In Holdover: Input references were available, but all input references have since been
lost. If the references are not restored before the Holdover period expires, time sync will
be lost.
No longer in Holdover: Input references were lost at one point (or declared not valid), but
have since been restored OR the Input references 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 cur-
rently 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 (SNMPSAD): An SNMP trap was sent by the SNMP agent to the
SNMP Manager. The event number in this entry indicates which SNMP trap was sent.
The Unit has Rebooted: SecureSync was either rebooted or power cycled.
Journal Log
Displays log entries created for all configuration changes that have occurred (such as creating
a new user account, for example).
4.5 Quality Management
CHAPTER 4 • SecureSync User Reference Guide Rev. 26
305
To Next Page
Loading...
