...
+ Nexus 9300 is not updating the time change received from an NTP server until all-peers statistics are reset/cleared. + Incorrect System Time: The Nexus device may continue to display the incorrect time even after the NTP server has synchronized with the correct time source. + Time Drift: Over time, the device's system time may drift further away from the actual time, causing potential synchronization issues in a network environment.
+ N9300-FX running NX-OS version 9.3(9) + Nexus configured as NTP client
Issue the following command to clear statistics: - clear ntp statistics all-peers Issue not observed in version 10.2(5)
Nexus 9300 is not updating the time change received from an NTP server until all-peers statistics are reset/cleared: configuration: N9K-1# show run ntp ntp server 2.2.2.2 use-vrf default ntp source 10.10.10.2 N9K-1# show clock 06:40:13.335 UTC Tue Sep 05 2023 Time source is NTP N9K-1# show ntp peer-status Total peers : 1 * - selected for sync, + - peer mode(active), - - peer mode(passive), = - polled in client mode remote local st poll reach delay vrf ----------------------------------------------------------------------------------------------------------------------- =2.2.2.2 0.0.0.0 16 64 0 0.00000default <<< Nexus not syncronizing ('*' is missing) + You will see the Nexus receiving NTP packets from NTP server configured 2023-08-30 19:51:21.293843 10.10.10.2 -> 2.2.2.2 NTP NTP client 2023-08-30 19:51:21.294115 2.2.2.2 -> 10.10.10.2 NTP NTP server 2023-08-30 19:51:23.293854 10.10.10.2 -> 2.2.2.2 NTP NTP client 2023-08-30 19:51:23.294205 2.2.2.2 -> 10.10.10.2 NTP NTP server + NTP statistics incrementing for sent and received NTP packets NTP-CLIENT# show ntp statistics peer ipaddr 2.2.2.2 remote host: 2.2.2.2 local interface: 10.10.10.2 time last received: 7s time until next send: 9s reachability change: 199s packets sent: 24 packets received: 18 bad authentication: 0 bogus origin: 0 duplicate: 0 bad dispersion: 0 bad reference time: 0 candidate order: 6