NTP clock not syc with software clock

[R Manjunatha]

Hi 

After the "clock update-calendar " software and hardware clock are not sync and I can able to ping DNS 8.8.8.8

R120#sh run | in ntp
ntp source Loopback0
ntp update-calendar
ntp server 129.6.15.32
ntp server 128.138.141.177
ntp server 10.1.1.1
ntp server 34.202.215.187
ntp server pool.ntp.org
ntp server 132.163.96.5
ntp server 132.163.97.5

R120#sh ntp st
Clock is unsynchronized, stratum 4, reference is 34.202.215.187
nominal freq is 250.0000 Hz, actual freq is 250.0000 Hz, precision is 2**10
ntp uptime is 169900 (1/100 of seconds), resolution is 4000
reference time is E7132E9A.0A3D70C0 (07:13:30.040 UTC Mon Nov 7 2022)
clock offset is 4.4304 msec, root delay is 263.23 msec
root dispersion is 65.98 msec, peer dispersion is 1.94 msec
loopfilter state is 'FREQ' (Drift being measured), drift is 0.000000000 s/s
system poll interval is 64, last update was 63 sec ago.
R120#sh clock de
R120#sh clock detail
*07:14:52.073 UTC Mon Nov 7 2022
Time source is NTP
R120#sh calendar
09:11:12 UTC Sun Mar 23 1952
R120#sh ntp ass

address ref clock st when poll reach delay offset disp
~129.6.15.32 .INIT. 16 - 512 0 0.000 0.000 15937.
~128.138.141.177 .INIT. 16 - 512 0 0.000 0.000 15937.
~10.1.1.1 .INIT. 16 - 512 0 0.000 0.000 15937.
*~34.202.215.187 45.32.207.136 3 38 64 377 224.94 7.567 1.939
+~185.35.202.197 77.40.226.121 2 23 64 377 329.96 23.213 1.946
~132.163.96.5 .INIT. 16 - 1024 0 0.000 0.000 15937.
~132.163.97.5 .INIT. 16 - 1024 0 0.000 0.000 15937.
* sys.peer, # selected, + candidate, - outlyer, x falseticker, ~ configured
R120#

[balaji.bandi]

why do you need so many NTP Peers. ? is there any reason ?

i would like to cutdown to 2 ..max 4  ( you have mix of local IP also)

ntp source Loopback0  ( from using this interface are you able to reach any of the IP listed in the NTP peers ?)

what IP you have loopback0 ?

some reference for your guidance :

https://www.cisco.com/c/en/us/support/docs/ip/network-time-protocol-ntp/116161-trouble-ntp-00.html

[R Manjunatha]

Hi

why do you need so many NTP Peers. ? is there any reason ? --------If I created 4 NTP servers any one of the nearest values of stratum will be selected out of 4 NTP peers

i would like to cutdown to 2 ..max 4  ( you have mix of local IP also) --OK I will rectify 

ntp source Loopback0  ( from using this interface are you able to reach any of the IP listed in the NTP peers ?)....yes I need use NTP client as well

what IP you have loopback0 ?----120.120.120.120

some reference for your guidance 

[balaji.bandi]

Can you post some output you are able to reach outside using this source?

120.120.120.120

[paul driver]

Hello
Looks like R120 is suppose to be a client, but its isnt set as such, make sure the loopback is reachable if your are sourcing from it and specify a preffered server.

Try the following:
ntp peer
clock read-calendar
ntp server x.x.x.x prefer