NTP reverts to local 127.127.1.0 (VMware)

Question

HI. I am experiencing an issue with a LAB deployment of CISCO ISE. I cannot get the NTP to sync and the DB services to start. See output below. Any help will be appreciated
iselab/admin# sh ntp
Configured NTP Servers:
172.16.0.101
synchronised to local net at stratum 11
time correct to within 11 ms
polling server every 1024 s
remote refid st t when poll reach delay offset jitter
==============================================================================
*127.127.1.0 .LOCL. 10 l 26 64 377 0.000 0.000 0.001
172.16.0.101 172.16.0.253 2 u 1630 1024 0 0.000 0.000 0.000
* Current time source, + Candidate
Warning: Output results may conflict during periods of changing synchronization.

Answer 1

The clock sync can take up to 20 minutes to complete.  You may also want to ensure that the ESXi server is also using the same NTP server as your ISE VM.  Since 127.127.1.0 is the local clock, having the ESXi configured this way will help to ensure the correct time in your VM.
The following quote is taken from the page linked below it:
"For example, NTP uses a pseudo IP address 127.127.8.n to access a Meinberg radio clock installed at the local computer. To access its own system clock, also called the local clock , NTP uses the pseudo IP address 127.127.1.0. This IP address must not be mixed up with 127.0.0.1, which is the IP of the localhost, i.e. the computer's loopback interface."
http://www.meinbergglobal.com/english/info/ntp.htm
Please let me know if this fixes your issue.  If it does, please rate this answer and mark your question as Answered.
Charles Moreton