Verifying VelaSync Works
Between 1 to 5 minutes after turning on VelaSync, TimeKeeper should be active and running. Once synchronization is established, VelaSync will answer NTP queries and provide PTP service, as configured.
Note that initial GPS startup can take up to 15 minutes. You can monitor the progress via the Status tab.
Testing VelaSync's essential functionality encompasses two quick tests described below:
- Verify that TimeKeeper reports the presence of a GPS signal: See Verifying the GPS Signal below.
- Test that NTP and/or PTP clients do, in fact, receive the time signal emitted by VelaSync: See Verifying Network Configuration below.
TimeKeeper's Status and Timing Quality tabs provide a clear summary of which source is being used, the current accuracy, and also details on the behavior of the various configured time sources over time.
To verify that a GPS signal is present:
- In the TimeKeeper Web UI, navigate to Timing Quality > Life Graphs, and wait a few moments until enough data has been collected to build the graphical representation.
- Verify that the TimeKeeper GPS line item is present and not grayed out under the Sources tab on the left.
- Check for the presence of the signal (same color e.g., green) in the graph:
Timing quality graphs
Another source of status information are the TimeKeeper logs, which are accessible under the Logs tab (seeThe "Logs" Tab for more information). The log file contains a line for every update that TimeKeeper receives and how TimeKeeper is adjusting time for Source (0).
For more information on the log file contents, see Creating an Audit Trail.
A Ping Test will tell you if VelaSync is accessible to clients.
For further testing …
- …in an NTP or Unicast PTP environment, you have to go to the clients and configure them to use VelaSync as their timing server.
- …in a Multicast PTP environment, clients should see Multicast announce messages from your VelaSync unit, and will start synchronizing to VelaSync after a short while, if it is the best master.