Skip to main content

NTP Configuration and Fallback Behavior

Written by Sunny

NTP Configuration and Behavior – Support Document

Overview

Network Time Protocol (NTP) is used by the device to synchronize its system time with a remote time server.

Correct time synchronization is critical for:

  • Event logging accuracy

  • Cloud communication

  • Certificate validation

  • Troubleshooting and monitoring

  • Scheduled operations

How to Configure NTP

  1. Go to Configuration → NTP

  2. Select Enable

  3. Enter the NTP Server URL

  • Example: time.google.com

  1. Press Enter after adding the URL

  2. Click Update Configuration

Important Points

  • Device must have internet connectivity to reach NTP server

  • Multiple NTP servers can be added for redundancy

  • After configuration change, device must be rebboted take new NTP config

NTP Logging Behavior

Once NTP configuration is applied, logs can be verified under:

Monitor → Events Logging

Typical log message:

  • New Config Applied

NTP Fallback Behavior (Very Important)

If a wrong / unreachable NTP server is configured and the device is rebooted, the device will automatically fallback to the default NTP server.

Default Fallback Server:

time.google.com

This automatic fallback ensures:

  • Device time remains synchronized

  • Event logs continue to show correct timestamps

  • Cloud heartbeat and communication are not impacted

  • System stability is maintained

How to Verify Fallback

Go to Events Logging

You will see log entry similar to:

Setting NTP servers to time.google.com

This confirms that:

  • Configured NTP server was invalid or unreachable

  • Device reverted to default Google NTP after reboot

Troubleshooting NTP Issues

If time is not syncing:

  • Check WAN / internet connectivity

  • Verify DNS resolution

  • Confirm NTP server is reachable

  • Reboot device after correcting NTP

  • Check firewall blocking UDP port 123

Best Practice Recommendation

  • Always configure valid public NTP servers

  • Prefer adding 2–3 NTP servers

  • Avoid leaving incorrect NTP entries

  • Verify logs after every configuration change

Example Recommended NTP Servers

  • time.google.com

  • pool.ntp.org

  • time.cloudflare.com

Conclusion

Proper NTP configuration is essential for device health, monitoring accuracy, and cloud stability.

The built-in fallback mechanism ensures operational continuity even if incorrect NTP settings are applied.

Did this answer your question?