03-28-2022 10:49 PM - edited 03-29-2022 02:25 AM
I have a Cisco 1841 with IOS Version 15.1(4)M1.
But it cant sync to my setting NTP server.
Interestingly, there are 2 cisco devices under its subnet, a C2960 switch and a ASA 5510 working in transparent mode. Only C2960 switch can sync to the NTP server, ASA 5510 have the same problem with Cisco 1841.
All device under it have access to NTP server, and I am sure the NTP traffic is not been blocked by ACL.
Cisco-1841#show ntp status Clock is unsynchronized, stratum 16, no reference clock nominal freq is 250.0000 Hz, actual freq is 250.0000 Hz, precision is 2**24 reference time is 00000000.00000000 (08:00:00.000 CST Mon Jan 1 1900) clock offset is 0.0000 msec, root delay is 0.00 msec root dispersion is 0.72 msec, peer dispersion is 0.00 msec loopfilter state is 'CTRL' (Normal Controlled Loop), drift is 0.000000000 s/s system poll interval is 64, never updated.
You may notice timestamp is correct here, that's because I manully set the time using clock set
Mar 29 05:39:46.021: IP: s=219.217.199.100 (local), d=116.13.10.10, len 76, local feature, NAT(2), rtype 0, forus FALSE, sendself FALSE, mtu 0, fwdchk FALSE Mar 29 05:39:46.021: IP: s=219.217.199.100 (local), d=116.13.10.10 (FastEthernet0/0), len 76, sending Mar 29 05:39:46.021: IP: s=219.217.199.100 (local), d=116.13.10.10 (FastEthernet0/0), len 76, output feature, Post-routing NAT Outside(24), rtype 1, forus FALSE, sendself FALSE, mtu 0, fwdchk FALSE Mar 29 05:39:46.021: IP: s=219.217.199.100 (local), d=116.13.10.10 (FastEthernet0/0), len 76, output feature, Stateful Inspection(27), rtype 1, forus FALSE, sendself FALSE, mtu 0, fwdchk FALSE Mar 29 05:39:46.021: IP: s=219.217.199.100 (local), d=116.13.10.10 (FastEthernet0/0), len 76, output feature, NAT ALG proxy(55), rtype 1, forus FALSE, sendself FALSE, mtu 0, fwdchk FALSE Mar 29 05:39:46.021: IP: s=219.217.199.100 (local), d=116.13.10.10 (FastEthernet0/0), len 76, sending full packet Mar 29 05:39:46.021: NTP message sent to 116.13.10.10, from interface 'FastEthernet0/0' (219.217.199.100). Mar 29 05:39:46.093: IP: s=116.13.10.10 (FastEthernet0/0), d=219.217.199.100, len 76, input feature, Stateful Inspection(5), rtype 0, forus FALSE, sendself FALSE, mtu 0, fwdchk FALSE Mar 29 05:39:46.093: IP: s=116.13.10.10 (FastEthernet0/0), d=219.217.199.100, len 76, input feature, Virtual Fragment Reassembly(25), rtype 0, forus FALSE, sendself FALSE, mtu 0, fwdchk FALSE Mar 29 05:39:46.093: IP: s=116.13.10.10 (FastEthernet0/0), d=219.217.199.100, len 76, input feature, Virtual Fragment Reassembly After IPSec Decryption(39), rtype 0, forus FALSE, sendself FALSE, mtu 0, fwdchk FALSE Mar 29 05:39:46.097: IP: s=116.13.10.10 (FastEthernet0/0), d=219.217.199.100, len 76, input feature, NAT Outside(66), rtype 0, forus FALSE, sendself FALSE, mtu 0, fwdchk FALSE Mar 29 05:39:46.097: IP: s=116.13.10.10 (FastEthernet0/0), d=219.217.199.100, len 76, input feature, MCI Check(80), rtype 0, forus FALSE, sendself FALSE, mtu 0, fwdchk FALSE Mar 29 05:39:46.097: IP: tableid=0, s=116.13.10.10 (FastEthernet0/0), d=219.217.199.100 (FastEthernet0/0), routed via RIB Mar 29 05:39:46.097: IP: s=116.13.10.10 (FastEthernet0/0), d=219.217.199.100 (FastEthernet0/0), len 76, output feature, Post-routing NAT Outside(24), rtype 1, forus FALSE, sendself FALSE, mtu 0, fwdchk FALSE Mar 29 05:39:46.097: IP: s=116.13.10.10 (FastEthernet0/0), d=219.217.199.100 (FastEthernet0/0), len 76, output feature, Stateful Inspection(27), rtype 1, forus FALSE, sendself FALSE, mtu 0, fwdchk FALSE Mar 29 05:39:46.097: IP: s=116.13.10.10 (FastEthernet0/0), d=219.217.199.100 (FastEthernet0/0), len 76, rcvd 3 Cisco-1841# Mar 29 05:39:46.097: IP: s=116.13.10.10 (FastEthernet0/0), d=219.217.199.100, len 76, stop process pak for forus packet Mar 29 05:39:46.101: NTP message received from 116.13.10.10 on interface 'FastEthernet0/0' (219.217.199.100). Mar 29 05:39:46.101: NTP Core(DEBUG): ntp_receive: message received Mar 29 05:39:46.101: NTP Core(DEBUG): ntp_receive: peer is 0x6576B708, next action is 1. Mar 29 05:39:46.101: NTP Core(DEBUG): receive: packet given to process_packet
Solved! Go to Solution.
03-28-2022 11:31 PM - last edited on 03-30-2022 07:49 PM by Translator
Enter the filename
c1841-adventerprisek9-mz.151-4.M8.bin
into a web browser. Follow where it goes to.
03-29-2022 12:00 AM
03-28-2022 11:18 PM
I would be upgrading the firmware of that router, if possible.
03-28-2022 11:19 PM - edited 03-28-2022 11:19 PM
But I dont have access to IOS image download in Cisco
03-28-2022 11:20 PM - edited 03-28-2022 11:22 PM
(Hey, don't give me kudos if the answer is wrong. It will give the wrong impression.)
Can you give me the filename of IOS currently being used?
03-28-2022 11:23 PM
c1841-advipservicesk9-mz.151-4.M1.bin
03-28-2022 11:31 PM - last edited on 03-30-2022 07:49 PM by Translator
Enter the filename
c1841-adventerprisek9-mz.151-4.M8.bin
into a web browser. Follow where it goes to.
03-28-2022 11:33 PM
I found it, now I am copying it to my CF flash
03-28-2022 11:43 PM
Thanks, it works fine now!
Cisco-1841#show clock *14:43:09.314 CST Tue Mar 29 2022
03-28-2022 11:45 PM - last edited on 03-30-2022 07:50 PM by Translator
@sfc9982 wrote:
Thanks, it works fine now!
Cisco-1841#show clock *14:43:09.314 CST Tue Mar 29 2022
No. It is not.
See the time has a "*" in front? That means NTP is not "synch". NTP is static assigned.
What is the output to the command
sh ntp associate
?
03-28-2022 11:47 PM
After a while, its OK, I was too hurry
Cisco-1841#show clock 14:46:27.613 CST Tue Mar 29 2022 Cisco-1841#show ntp ass Cisco-1841#show ntp associations address ref clock st when poll reach delay offset disp *~202.112.31.197 .PTP. 1 7 64 17 10.386 1104.54 938.76 * sys.peer, # selected, + candidate, - outlyer, x falseticker, ~ configured Cisco-1841#
Thank you
03-28-2022 11:52 PM
That output is perfect.
Yes, NTP is now working.
03-28-2022 11:18 PM
- It seems that your logs match this : https://www.cisco.com/c/en/us/support/docs/ip/network-time-protocol-ntp/116161-trouble-ntp-00.html#anc6 and or packets not being received by the NTP server, check routing towards it too and test with ping for instance, last but not lease review the complete document too : https://www.cisco.com/c/en/us/support/docs/ip/network-time-protocol-ntp/116161-trouble-ntp-00.html
M.
03-29-2022 12:00 AM
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