cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
401
Views
0
Helpful
2
Replies

NTP status: clock unsynchronized on SW 2960

patramirezort
Level 1
Level 1

Hi,

I'm trying to synchronize Cisco 2960's switches to an internal NTP server, but I have the ntp status 'clock unsynchronized' and ntp associations 'master, sane, valid'. After a while the ntp associations change to 'insane, invalid, stratum 4'.  SW is running Version  15.2(6)E .

The corporate have different locations, the local NTP server (192.168.15.15) depends from HQ 192.168.7.15. 

This network don't use L3 Switches as a main core on this location, only L2.

Any suggestions would be appreciated. Thank you!

................

Here are the current NTP configuration and status. 

SW#sh run | b ntp
ntp update-calendar
ntp server 192.168.15.15

SW#sh ntp status
Clock is unsynchronized, stratum 5, reference is 192.168.15.15
nominal freq is 286.1023 Hz, actual freq is 286.1023 Hz, precision is 2**19
ntp uptime is 72700 (1/100 of seconds), resolution is 3496
reference time is E8AB2C10.1420546F (11:27:28.078 PDT Tue Sep 12 2023)
clock offset is 34.8297 msec, root delay is 92.05 msec
root dispersion is 175.21 msec, peer dispersion is 0.96 msec
loopfilter state is 'FREQ' (Drift being measured), drift is 0.000000000 s/s
system poll interval is 64, last update was 48 sec ago.

SW#sh ntp associations detail
192.168.15.15 configured, ipv4, our_master, sane, valid, stratum 4
ref ID 192.168.7.15 , time E8AB28DF.7A5A6EE1 (11:13:51.477 PDT Tue Sep 12 2023)
our mode client, peer mode server, our poll intvl 64, peer poll intvl 64
root delay 89.06 msec, root disp 124.52, reach 377, sync dist 188.01
delay 2.77 msec, offset 41.9905 msec, dispersion 0.98, jitter 15.69 msec
precision 2**23, version 4
assoc id 60545, assoc name 172.27.10.10
assoc in packets 20, assoc out packets 20, assoc error packets 0
org time 00000000.00000000 (16:00:00.000 PDT Wed Dec 31 1899)
rec time E8AB2C99.1E7361F7 (11:29:45.118 PDT Tue Sep 12 2023)
xmt time E8AB2C99.1E7361F7 (11:29:45.118 PDT Tue Sep 12 2023)
filtdelay = 2.77 2.55 2.98 1.18 2.81 1.76 3.05 2.12
filtoffset = 41.99 38.72 34.82 32.10 27.76 24.73 20.58 17.38
filterror = 0.00 1.03 2.05 3.04 4.06 5.05 6.06 7.06
minpoll = 6, maxpoll = 10

SW#sh ntp associations detail
192.168.15.15  configured, ipv4, insane, invalid, stratum 4
ref ID 192.168.7.15 , time E8AB2CDF.7E10E52A (11:30:55.492 PDT Tue Sep 12 2023)
our mode client, peer mode server, our poll intvl 64, peer poll intvl 64
root delay 87.28 msec, root disp 95.44, reach 1, sync dist 8078.75
delay 1.92 msec, offset 40.2234 msec, dispersion 7937.50, jitter 0.00 msec
precision 2**23, version 4
assoc id 60545, assoc name 172.27.10.10
assoc in packets 31, assoc out packets 31, assoc error packets 0
org time 00000000.00000000 (16:00:00.000 PDT Wed Dec 31 1899)
rec time E8AB2EB2.2600CE5C (11:38:42.148 PDT Tue Sep 12 2023)
xmt time E8AB2EB2.2600CE5C (11:38:42.148 PDT Tue Sep 12 2023)
filtdelay = 1.92 0.00 0.00 0.00 0.00 0.00 0.00 0.00
filtoffset = 40.22 0.00 0.00 0.00 0.00 0.00 0.00 0.00
filterror = 0.00 16000.0 16000.0 16000.0 16000.0 16000.0 16000.0 16000.0
minpoll = 6, maxpoll = 10

2 Replies 2

Hello,

 

Have you checked the logs on the internal NTP server to see if traffic is making it to there. Can you provide the NTP debugs on the switches?

debug ntp packets

 

-David

Is it possible that there are connectivity problems between the switch and the NTP server? 

HTH

Rick
Review Cisco Networking for a $25 gift card