05-18-2014 03:29 AM - edited 03-03-2019 07:24 AM
I am currently in a situation where I have three ISR G1 routers running IOS 15.1(4)M7 and I am completely unable to sync them to any NTP source. Be it public NTP servers or setting up one of the routers as an NTP server itself.
Here is the configuration from the NTP server that I set up on the 1841
NTP-MASTER#sh run | section ntp
ntp logging
ntp authentication-key 1 md5 0802455D0A16544541 7
ntp authenticate
ntp trusted-key 1
ntp master 7
And this is what is configured and displayed on the NTP-CLIENT (an 1811 router running IOS 15.1(4)M7
NTP-CLIENT#sh run | section ntp
ntp logging
ntp authentication-key 1 md5 02250D4808095E731F 7
ntp authenticate
ntp trusted-key 1
ntp server 10.0.0.1
*May 17 17:54:36.459: NTP Core (INFO): synchronized to 10.0.0.1, stratum 7
*May 17 17:55:20.732: %SYS-6-CLOCKUPDATE: System clock has been updated from 17:54:36 UTC Sat May 17 2014 to 17:55:20 UTC Sat May 17 2014, configured from NTP by 10.0.0.1.
*May 17 17:55:20.732: NTP Core (NOTICE): time reset 44.272715 s
*May 17 17:55:38.732: NTP Core (INFO): peer 10.0.0.1 event 'event_reach' (0x84) status 'unreach, conf, 7 events, event_reach' (0x8074)
*May 17 17:55:38.732: NTP Core (INFO): synchronized to 10.0.0.1, stratum 7
*May 17 17:55:45.734: %SYS-6-CLOCKUPDATE: System clock has been updated from 17:55:40 UTC Sat May 17 2014 to 17:55:45 UTC Sat May 17 2014, configured from NTP by 10.0.0.1.
*May 17 17:55:45.734: NTP Core (NOTICE): time reset 5.002567 s
NTP-CLIENT#sh ntp status
Clock is unsynchronized, stratum 16, reference is 10.0.0.1
nominal freq is 250.0000 Hz, actual freq is 249.9949 Hz, precision is 2**15
reference time is 00000000.00000000 (00:00:00.000 UTC Mon Jan 1 1900)
clock offset is 11255.8437 msec, root delay is 0.00 msec
root dispersion is 1.58 msec, peer dispersion is 7937.51 msec
loopfilter state is 'SPIK' (Spike), drift is 0.000020457 s/s
system poll interval is 64, never updated.
NTP-CLIENT#sh ntp associations
address ref clock st when poll reach delay offset disp
~10.0.0.1 127.127.1.1 7 13 64 3 1.456 27264.0 3937.7
* sys.peer, # selected, + candidate, - outlyer, x falseticker, ~ configured
This shows is telling me something about the server being unreachable, but... I don't know why it isn't working. Same config in IOS 12.4 works perfectly. And, also, I tried with an 881 router running 15.3(3)M1 and it synched to public NTP servers just fine using the "ntp server" command. Also, it needs to be said that the ISR G1 routers also show the same messages in the log when trying to connect to public NTP servers.
I do think I am doing something wrong here, but I just can't find anything on it anywhere. I have looked through the documentation for the IOS version and configured NTP as shown there and I also looked for any caveats that may be open on the platform/IOS, but found nothing relating to my issue.
So, is there anyone out there that can spot my error here? It is driving me mad. I would also like to note that these are not in production - they are in my lab rack at home. So, there is a great amount of flexibility when it comes to troubleshooting the issue.
Any help would be much appreciated.
05-18-2014 03:34 AM
If NTP works with 12.4 and it doesn't on this version, then it's got to be a bug. You may need to upgrade to the next train up.
05-18-2014 03:42 AM
I also tried 15.1(3)T4 in both adventerprise and advipservices, but with the same result.
There is only one image newer than the 15.1(4)M7 that I currently use and that is 15.1(4)M8, but nothing in the release notes address any NTP issue.
I just think that if it were a bug in the IOS it would have been noticed by someone other than myself. It's like it's some sort of niche feature I am trying to get to work - it's NTP.
05-18-2014 04:51 AM
I just think that if it were a bug in the IOS it would have been noticed by someone other than myself. It's like it's some sort of niche feature I am trying to get to work - it's NTP.
In Catalyst switch IOS version 15.0(2)SE2, it will take 10 minutes (instead of 5) for NTP to get synch. It wasn't mentioned in the Bug Toolkit (BTK). Not all bugs are reported in BTK especially if the bugs are deemed to be "internal".
It's a bug. Your description points that way.
05-19-2014 12:48 AM
I agree with you, Leo. It does point to an issue. But I just find it strange that I can't find anyone on Google who mentions the same issue. I would think that someone out there would be wanting to comment on it somewhere - kind of like I do right now.
I will see if I can get a hold of the newer IOS and update this thread as to whether it helps with my NTP issue or not.
Thanks.
Discover and save your favorite ideas. Come back to expert answers, step-by-step guides, recent topics, and more.
New here? Get started with these tips. How to use Community New member guide