NTP unsynchronized on Subscriber

[munzirk]

I am facing issue with NTP synchronized on Subscribers where as it is synchronized correctly on Publisher. How can i resolve this issue. Please help.

admin:utils ntp status
ntpd (pid 3007) is running...

remote refid st t when poll reach delay offset jitter
==============================================================================
10.19.240.90 .INIT. 16 u 40 64 0 0.000 0.000 0.000

unsynchronised
polling server every 8 s

Current time in UTC is : Mon Jul 22 07:52:01 UTC 2019
Current time in Asia/Riyadh is : Mon Jul 22 10:52:01 AST 2019

All the diagnostic information is attached here.

Thank you.

[Jinto Alakkal]

Are you using FQDN or IP address, if you are using FQDN can you try to use IP address and see if it resolves the issue.

[piyush aghera]

Couple of things to check:

1. is your publisher using 10.19.240.90 (same as sub) as NTP or 10.19.240.90 is the pub ?

2. is your NTP 10.19.240.90 reachable from sub ?

3. is your dbreplication fine in CUCM cluster ?

If 10.19.240.90 is not your pub, then you can try to set your sub NTP as your pub, which is mostly used in case of CUCM clusters.  Dont forget to restart your NTP service on sub when you change the NTP server details.

[Prassha]

Hello munzirk
Let me know if you are facing any issue with the time or cluster replication.
If everything is okay, you shouldn't be worry about the NTP Sync because all endpoints will take the time as per NTP sync from Pub.
What is the CUCM version?
How many subs are affected?
Are you using windows based NTP server or IOS based?
Is there any recent changes you made in the cluster ?

Regards,
PRASSHA3

Rate if you find this helpful or Mark Solutions as Accepted