Monitor an edge node's NTP servers

After you set up an NTP solution for an edge node, you can monitor the status and performance of the NTP servers included in your solution.

Edge nodes publish status and performance metrics of their NTP servers to ZEDEDA Cloud. You can see these metrics in the ZEDEDA GUI in each edge node's Status page.

By default, edge nodes will send this information to ZEDEDA Cloud every 10 minutes, or when the mode, state, or reachability of a server changes.

This guide explains how to access these metrics and what the possible values of each metric mean.

Prerequisites

You may want to read our Clock synchronization overview.

Software requirements

To be compatible with NTP status reporting, an edge node must be running at least EVE-OS version 12.6.0.

View an edge node's NTP servers' statuses

  1. Log in to the ZEDEDA GUI.
  2. Click on Edge Nodes in the side nav on the left.
  3. Click on the edge node that you know more about.
  4. Click on the Status tab. You'll see the following table.


    If an edge node is running an EVE-OS version that doesn’t support NTP status reporting, you’ll see the following message: “No NTP server information available”. This message does not imply NTP is not active.

Status values

Find Value
Mode

Client - Requests time information from an NTP server.

Peer - Sends and receives time information.

Reference - Highly precise clock source, typically GPS or better.

State

Sync: Currently synchronized and providing valid time updates.

Unreach: Source is unreachable

FalseTicker: Source is providing incorrect time updates.

Jittery: Source has high variability or jitter in time updates, reducing its reliability. 

Candidate: Candidate for synchronization but is not currently the selected time source

Outlier: Not used for time synchronization due to significant discrepancies

Destination NTP server IP address
Reachable Reachable ‘Yes’ indicates that the last 8 NTP polls have been successful. A server can be an active source even though not all attempts are successful. 
Stratum The number of NTP hops away the edge node is from an authoritative time source
Offset Time difference between the local and reference clock
Delay Round-trip time for communication between NTP client and server
Jitter Variability in delay over successive communications
Was this article helpful?
1 out of 1 found this helpful