Hello All,
CUCM System version: 12.5.1.13900-152 - 1 Publisher and 3 subscribers
I'm having an issue where NTP is unsynchronized. I can sit and use utils ntp restart on the publisher all day long and it never synchronizes.
remote refid st t when poll reach delay offset jitter
==============================================================================
+<NTP IP ADDRESS> u 15 64 1 1.023 -1823.8 1653.58
+<NTP IP ADDRESS> u 14 64 1 40.296 -1865.4 1568.27
+<NTP IP ADDRESS> u 13 64 1 0.907 -1910.8 1698.47
*<NTP IP ADDRESS> u 45 64 1 42.508 -519.46 287.555
unsynchronised
polling server every 64 s
You can see lots of jitter and offset. this status is right after I had just restarted NTP
We're using known good internal Linux NTPs (CUCM is the only system in our network having the NTP issue) that we have been using for years with no issues. port 123 is open, no issues there.
I have a case open with TAC, they are recommending to uncheck the "Synchronize Time with Host" option on the VM in VMWare (ESXi version 7.0). Which I haven't been able to do yet because our company is in a change freeze.
I just wanted to check here to see if anyone else has experienced this and if they had any suggestions to get NTP resynchronized. I also wanted to see if anyone who had this issue was able to resolve it by unchecking the "Synchronize Time with Host" option in VMWare. Most info I can find says to do traces (we've done that with TAC) and just keep trying to restart NTP, but this does not seem to help with getting NTP synchronized.
This issue is causing a DBRepliecationFailure to occur every hour. The issue seems to have started after I upgraded from 11.5 to 12.5 (SU1) and continues to happen after we upgraded to 12.5 (SU4), which is the most current version of CUCM available.
When it first started happening, it seemed like restarting the CUCM cluster would resolve it temporarily. About one week after the restart, the issue would occur again. But the issue came up again two days ago and now restarting the cluster isn't even helping as the issue persists pretty much immediately after the cluster restart.
Any info would be greatly appreciated
Thanks!
