Has anyone else had any issues with NTP on 3810M switches? I am using the exact same config on my 2930F switches where NTP does work. I've tried multiple NTP servers but I can't get the 3810M switches to sync.
Both the 2930F and 3810M switches are running KB.16.04.0008, time to open a TAC case?
2930F# show config | i ntp
timesync ntp
ntp unicast
ntp server 193.190.198.10 iburst
ntp enable
3810M# show config | i ntp
timesync ntp
ntp unicast
ntp server 193.190.198.10 iburst
ntp enable
2930F# show ntp status
NTP Status Information
NTP Status : Enabled NTP Mode : Unicast
Synchronization Status : Synchronized Peer Dispersion : 0.00000 sec
Stratum Number : 3 Leap Direction : 0
Reference Assoc ID : 0 Clock Offset : 0.32301 sec
Reference ID : 193.190.198.10 Root Delay : 0.00582 sec
Precision : 2**-18 Root Dispersion : 1.82694 sec
NTP Up Time : 1d 15h 28m Time Resolution : 820 nsec
Drift : 0.00013 sec/sec
System Time : Sun Oct 8 02:58:48 2017
Reference Time : Sat Oct 7 23:03:12 2017
3810M# show ntp status
NTP Status Information
NTP Status : Enabled NTP Mode : Unicast
Synchronization Status : Not Synced Peer Dispersion : 0.00000 sec
Stratum Number : 16 Leap Direction : 0
Reference Assoc ID : 0 Clock Offset : 0.00000 sec
Reference ID : 0.0.0.0 Root Delay : 0.00000 sec
Precision : 2**-18 Root Dispersion : 41.67973 sec
NTP Up Time : 32d 3h 50m Time Resolution : 420 nsec
Drift : 0.00000 sec/sec
System Time : Sun Oct 8 02:55:19 2017
Reference Time : Mon Jan 1 02:00:00 1990
3810M# show log -r
M=Major D=Debug E=Error
---- Reverse event Log listing: Events Since Boot ----
I 10/08/17 03:02:09 04911 ntp: ST1-CMDR: The NTP Server 193.190.198.10 is unreachable.
3810M# ping 193.190.198.10
193.190.198.10 is alive, time = 4 ms