Skip to main content

⏰ Resolving Time Sync Errors

Time synchronization is the backbone of accurate alarm processing. When Genesis and Talos clocks drift apart, it can lead to out-of-order events, missed SLAs, and fragmented audit logs.

🔍 How to Identify Drift​

You likely have a sync issue if you notice:

  • Alarms appearing in the Talos buffer with "Future" or "Past" timestamps.
  • Video playback not aligning with the alarm event marker.
  • Scheduled workflows (like auto-arming) triggering at the wrong time.

🛠️ Step-by-Step Diagnostic​

  1. 1

    1. Compare System Times​

  2. 2
    • In Genesis: check the device dashboard for the current "Last Seen" timestamp.
    • In Talos: view the site overview and check the "Last Pulse" time.
    • The Gap: A difference of more than 5 seconds is considered a drift.
  3. 3

    2. Verify NTP Configuration​

  4. 4

    Most devices should point to the centralized NXGEN time server:

  5. 5
    • NTP Server: time1.nxgen.cloud
    • Port: UDP 123 (Ensure this is open in your Firewall).
  6. 6

    3. Check Timezone Alignment​

  7. 7

    Mismatched timezones are the most common cause of "drift."

  8. 8
    • Ensure both the Genesis Site Profile and the Talos Site Settings are set to the exact same regional timezone.

🚀 Common Fixes​

Solution 1: Global NTP Push​

If multiple sites are drifting, update the Default NTP in your Tenant Settings to time1.nxgen.cloud.

Solution 2: Firewall Whitelisting​

If the NTP status is "Timeout," ensure your edge router is not blocking UDP Port 123. Some ISPs block this port by default to prevent DDoS attacks.

Related Articles

NTP Configuration

Detailed setup for localized time servers.

Firewall Rules

Whitelisting NTP traffic.

Next: Resolving Alarm Overflow Thresholds