NTP Server cannot work in 6509

[3back]

Dear All

We deployed a both 6509 with VSS. The network also acquires 3750 and 2960. The below is NTP testing within the network. I ever input "debug ntp" can see the ntp request but cannot be sync.

Is that a bug in 6509?

Outside NTP server >> 6509 (Can sync)

Outside NTP server >> 6509 >> 3750 >> 2960(Can't work)

6509(NTP server) >>3750 >> 2960(Can sync)

[sathvik k v]

So 6509 is NTP server to other two switches and you cant see them to be in Sync? Can you share configuration and output of the commands:

show ntp status

show ntp association 

show ntp association detail.

[3back]

This is the output from 6500. Since 6500 got from outsite NTP 10.220.x.x that other switches cannot get ntp from 6500

sh ntp status
Clock is synchronized, stratum 15, reference is 10.220.x.x 
nominal freq is 250.0000 Hz, actual freq is 249.9969 Hz, precision is 2**20
ntp uptime is 32688200 (1/100 of seconds), resolution is 4016
reference time is DE62E884.B987E092 (11:33:24.724 HKT Mon Mar 26 2018)
clock offset is 1.4518 msec, root delay is 0.55 msec
root dispersion is 31.69 msec, peer dispersion is 20.81 msec
loopfilter state is 'CTRL' (Normal Controlled Loop), drift is 0.000012276 s/s
system poll interval is 64, last update was 67 sec ago.

sh ntp associations

address ref clock st when poll reach delay offset disp
~127.127.1.1 .LOCL. 7 3 16 377 0.000 0.000 0.232
*~10.220.x.x 172.29.x.x 14 5 64 377 0.801 10.536 20.136
* sys.peer, # selected, + candidate, - outlyer, x falseticker, ~ configured

sh ntp associations detail
127.127.1.1 configured, ipv4, insane, invalid, stratum 7
ref ID .LOCL., time DE62E8C9.B98DFF7B (11:34:33.724 HKT Mon Mar 26 2018)
our mode active, peer mode passive, our poll intvl 16, peer poll intvl 16
root delay 0.00 msec, root disp 0.00, reach 377, sync dist 1.00
delay 0.00 msec, offset 0.0000 msec, dispersion 0.23, jitter 0.00 msec
precision 2**20, version 4
assoc id 58071, assoc name 127.127.1.1
assoc in packets 20432, assoc out packets 20432, assoc error packets 0
org time DE62E8C9.B98DFF7B (11:34:33.724 HKT Mon Mar 26 2018)
rec time 00000000.00000000 (08:00:00.000 HKT Mon Jan 1 1900)
xmt time DE62E8C9.B98DEB20 (11:34:33.724 HKT Mon Mar 26 2018)
filtdelay = 0.00 0.00 0.00 0.00 0.00 0.00 0.00 0.00
filtoffset = 0.00 0.00 0.00 0.00 0.00 0.00 0.00 0.00
filterror = 0.00 0.24 0.48 0.72 0.96 1.20 1.44 1.68
minpoll = 4, maxpoll = 4

10.220.x.x configured, ipv4, our_master, sane, valid, stratum 14
ref ID 172.29.x.x , time DE62DCDA.CFDF3A74 (10:43:38.811 HKT Mon Mar 26 2018)
our mode client, peer mode server, our poll intvl 64, peer poll intvl 64
root delay 0.00 msec, root disp 0.00, reach 377, sync dist 24.25
delay 0.80 msec, offset 10.5367 msec, dispersion 20.13, jitter 3.56 msec
precision 2**6, version 4
--More-- assoc id 58072, assoc name 10.220.10.1
assoc in packets 5241, assoc out packets 5241, assoc error packets 0
org time 00000000.00000000 (08:00:00.000 HKT Mon Jan 1 1900)
rec time DE62E8C7.BCAC0757 (11:34:31.736 HKT Mon Mar 26 2018)
xmt time DE62E8C7.BCAC0757 (11:34:31.736 HKT Mon Mar 26 2018)
filtdelay = 0.87 0.83 0.89 0.88 0.95 0.93 0.85 0.80
filtoffset = 11.76 10.68 10.87 9.99 3.95 13.76 4.75 10.53
filterror = 15.62 16.63 17.65 18.65 19.64 20.57 21.50 22.43
minpoll = 6, maxpoll = 10

[Deepak Kumar]

Hi, 

Make sure that you have run "ntp update-calendar" command on 2960 switches. 

We need some details from you as 

Show ntp status 

Show ntp associations

show ntp  packets

show ntp information 

Regards,

Deepak Kumar

[3back]

You can find Show ntp status and Show ntp associations in this post. 

sh ntp packets
Ntp In packets : 48226
Ntp Out packets : 48226
Ntp bad version packets : 28238
Ntp protocol error packets : 0

sh ntp information
Ntp Software Name : Cisco-ntpv4
Ntp Software Version : Cisco-ntpv4-1.0
Ntp Software Vendor : CISCO
Ntp System Type : Cisco IOS / M8572

[sathvik k v]

From which switch are these outputs? I see some bad version packets. Which version of NTP are you running on switches?

Ntp bad version packets : 28238 

[Deepak Kumar]

Hi,

In your NTP STATUS output, I can see that your clock is synchronized successfully. But there are other issues shown "Ntp bad version packets : 28238". Currently, you are using NTPv4 and which version is configured on your server?

Did you try with NTPv3?

Regards,

Deepak Kumar

[3back]

Dear All

We found 3750 and PC can get an NTP from 6509 but 3750 need to take around 20 minutes to get a clock from 6509. By the way! 2960 still cannot get a clock from 6509. I ever checked 2960 only can support NTP v1-v3, 6509 is running NTPv4 now. Is this any set up can settle that?

Best Regards

[Deepak Kumar]

Hi, 

Make 6509 to NTP V3 read with the command "NTP Version3"

Regards,

Deepak Kumar

[3back]

Dear all

I checked the NTP status again today. Unfortunately, the NTP service is malfunction again. All 3750 cannot get NTP from 6509 now. The below situation still cannot be fixed. By the way! I ever created a window NTP server for a test but still cannot work. So the outside NTP server should haven’t a problem.

Outside NTP server >> 6509 >> 3750 >> 2960(Can't work)