4.11
Logs
SecureSync maintains different types of event logs (see below) to allow for traceability, and for
record keeping. Should you ever require technical support from Spectracom, you may be asked for
a copy of your logs to facilitate remote diagnosis.
Logs stored internally are being kept automatically, while the storage of log files in a remote loc-
ation has to be set up by the user.
For each type of log, four 75 KB files are maintained internally on a revolving basis, i.e. the oldest
file will be overwritten, as soon as all four files have filled up with event data. The life expectancy
of a log file depends on the amount of data accumulating over time: Some types of logs will fill up
within days, while others can take months until they have reached their maximum storage capa-
city.
Logs can be deleted by the user at any time, see "Clearing Logs" on page 272.
4.11.1
Types of Logs
SecureSync generates log files for the following event categories:
System Log
Displays log entries related to the Timing System events and daemon events (such as the Alarms,
Monitor, Notification, or SNMP daemons starting or stopping, etc.)
Events Log
Displays log entries related to GNSS reception status changes, Sync/Holdover state changes,
SNMP traps being sent, etc. Examples include:
CHAPTER
•
4
SecureSync User Reference Guide Rev. 18
To display a higher resolution graph for a shorter time span, move one or both time
sliders at the bottom of the graph inwards.
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).
4.11 Logs
255
Need help?
Do you have a question about the SecureSync and is the answer not in the manual?