04-26-2016 03:46 AM - edited 03-17-2019 06:43 AM
Hi,
I have the following weird issue with NTP. When I check with the command "utils ntp status" I get the information that clock is Synchronized:
admin:utils ntp status
ntpd (pid 6811) is running...
remote refid st t when poll reach delay offset jitter
==============================================================================
+193.239.214.227 145.238.203.10 3 u 153 256 377 35.319 -1.920 0.647
*178.239.61.38 193.67.79.202 2 u 202 256 377 61.296 -2.136 0.574
synchronised to NTP server (178.239.61.38) at stratum 3
time correct to within 122 ms
polling server every 256 s
But in the CUCM GUI I see "WARNING: NTP server unreachable
In the OS administration I see:
1.gr.pool.ntp.org The NTP server could not be contacted.
1.europe.pool.ntp.org The NTP server could not be contacted.
When I use IP addresses instead of names, everything is OK
Any idea?
Bye
04-26-2016 03:54 AM
Please note NTP does not go unsynchronized straightaway, it takes time hence the output you are getting on OS Admin is valid. BTW, if the IP address is working fine then why are you choosing FQDN. Also, it is not recommended to use free NTP source available on the internet. You should be using a dedicated IOS based NTP source within your internal network itself for the UC applications.
Regards
Deepak
04-26-2016 04:08 AM
Hello Deepak,
Normally with an installation I use an IOS box to sync to an NTP resource in the Internet, and the CUCM Publisher uses this IOS box as it's NTP resource
Just find it weird that when the NTP (on CUCM) is configured with IP (External or Internal) the GUI and the CLI tell me that all is OK, but when I configure an FQDN, the CLI says all is OK, but the GUI says unreachable.
Just curious why this is, doesn't make sense!
Thanks
Jan
05-31-2016 09:09 AM
Hi Jan,
I have the same behavior with internal NTP servers. I configured the server with FQDN via CLI - status shows fine on CLI. In GUI it says "The NTP server could not be contacted." Did you find a solution for this?
Thank you,
Andreas
05-31-2016 09:32 AM
nope, just use IP's
Bye
09-21-2016 07:58 AM
Hi,
I have same issue, could you please tell me which CUCM version did you use ?
Tnx
09-21-2016 08:34 AM
I have seen this issue in CUCM 10.5.2. I restarted the NTP service to fix this issue. Run the command 'utils ntp restart' from the cli.
09-21-2016 08:33 AM
I have seen this issue in CUCM 10.5.2. I restarted the NTP service to fix this issue. Run the command 'utils ntp restart' from the cli.
05-04-2018 09:32 AM
Restarting NTP did not work for me.
- CUCM/CUC 12.0 & UCCX 11.6 are all experiencing this.
- Same symptoms as others where CLI shows sync with utils ntp status, but CLI and GUI state "NTP server unreachable" when you login.
- Configuration is pool.ntp.org & time.nist.gov which I realize is abnormal and I should be using an IOS router but that's not an option quite yet.
- utils ntp server add x.x.x.x results in "Inaccessible NTP server. Not added."
05-31-2018 09:30 AM - edited 05-31-2018 09:30 AM
I can confirm that this is occurring in UCCX 11.6 and restarting NTP is not resolving the issue. Anyone else have anything to add on this "cosmetic" bug or could this actually be an issue?
VMware Installation:
2 vCPU: Intel(R) Xeon(R) CPU E5-2630 v3 @ 2.40GHz
Disk 1: 146GB, Partitions aligned
10240 Mbytes RAM
WARNING: NTP server unreachable
admin:utils ntp status
ntpd (pid 1828) is running...
remote refid st t when poll reach delay offset jitter
==============================================================================
*66.135.44.92 216.218.254.202 2 u 15 64 17 47.023 1.701 0.387
synchronised to NTP server (66.135.44.92) at stratum 3
time correct to within 1020 ms
polling server every 64 s
Current time in UTC is : Thu May 31 16:28:45 UTC 2018
Current time in America/New_York is : Thu May 31 12:28:45 EDT 2018
05-31-2018 10:36 AM
Hi there
You can run utils diagnose test command on CUCM CLI and see the ntp tests are passed. If yes, I dont think you have something to worry about.
test - ntp_reachability
test - ntp_clock_drift
test - ntp_stratum
Hope this Helps
Cheers
Rath!
***Please rate helpful posts***
04-11-2022 06:42 AM
It worked for me, thanks
06-01-2018 01:16 AM
Please ensure the ntp version you are using is version 4.
please refer to :
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