Overview

Accurate system time is critical for ONT device logging, alarm correlation, and management plane operations. This FAQ addresses the most common technical questions network engineers ask when configuring NTP (Network Time Protocol) synchronization on ONT platforms, from initial CLI access to verification and failover troubleshooting.

Frequently Asked Questions

Q1: How do I configure an NTP server on an ONT device via CLI?

Enter global configuration mode and use the ntp server <ip-address> command to specify the time source. Most ONT CLI implementations require at minimum a reachable NTP server IP and a valid time zone offset before synchronization begins . For redundancy, configure two to three NTP servers using separate ntp server commands; the device will select the most reliable source based on stratum and reachability metrics . After configuration, commit the changes with commit or save to persist across reboots.

Q2: What is the difference between NTP and SNTP on ONT devices?

NTP provides full clock synchronization with complex algorithms for drift correction, while SNTP (Simple NTP) is a lightweight subset commonly implemented on customer-premises ONT devices for basic time accuracy. Many ONT platforms expose SNTP client functionality through a web GUI or ACS (TR-069) rather than full CLI NTP configuration . If your ONT only supports SNTP, the same server IP configuration applies, but expect coarser synchronization intervals and no peer hierarchy negotiation.

Q3: How do I verify that the ONT has successfully synchronized with the NTP server?

Use the show ntp status or display ntp status command; a synchronized device will display "Clock is synchronized" along with the stratum level and reference server IP . If the status shows an unsynchronized state, check reachability to the NTP server using ping and verify that UDP port 123 is not blocked by any intermediate firewall or ACL. On GUI-managed ONTs, navigate to the Status page and confirm that the displayed Date/Time field reflects the current time rather than the factory default .

Q4: Why does the ONT time remain incorrect despite NTP being configured?

The most common cause is a missing or incorrect time zone offset configuration. NTP servers provide UTC time; without a proper clock timezone or equivalent setting, the ONT will display UTC rather than local time . Second, verify that the ONT can route to the NTP server through its management VRF or WAN interface—an NTP server on the public internet is unreachable if the ONT management plane lacks a default gateway. Finally, some ONTs require the NTP client service to be explicitly enabled with a command such as sntp client enable before any server configuration takes effect .

Q5: What is the recommended NTP polling interval for ONT devices?

The default polling interval varies by vendor, typically ranging from 1024 to 3600 seconds; 1024 seconds is a common default for infrastructure-grade equipment . For stable enterprise deployments, the default is generally sufficient unless the ONT experiences frequent reboots or resides in an environment with poor clock stability. Reducing the interval below 256 seconds increases management traffic without meaningful accuracy benefit for typical ONT logging and alarm timestamping use cases.

Q6: Can I use authentication for NTP on ONT devices?

Yes, many carrier-grade ONT platforms support NTP authentication using MD5 or SHA keys. Configure the key with ntp authentication-key <id> md5 <password> and mark it trusted with ntp trusted-key <id> before associating it with the server . Authentication prevents the ONT from synchronizing with a rogue NTP server, which could corrupt log timestamps and undermine forensic accuracy. Note that SNTP-only ONTs typically do not support authentication.

Q7: What happens to ONT time synchronization if the primary NTP server fails?

If multiple NTP servers are configured, the ONT will automatically fail over to the next reachable server with the lowest stratum value. The synchronization state may briefly show "unsynchronized" during the failover interval, but the local clock continues to run on its last known good time until a new server is reached . To verify failover behavior, temporarily block the primary server IP with a test ACL and observe that the show ntp status reference IP changes to the backup server within the polling interval.

Q8: How do I set the time zone and daylight saving time on an ONT?

Use the clock timezone command with an offset from UTC (for example, clock timezone CST add 8 for China Standard Time) to align displayed time with local requirements . For regions observing daylight saving time, configure the start and end rules explicitly using commands such as ip ntp daylightsaving start and ip ntp daylightsaving end . Verify the final configuration with show clock detail, which should display both the UTC offset and any active DST rule .