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."
Thank You Andrey. I double checked the setting and it is as you recommended. The guest is not syncing with the VMWare host. I still cannot get the ISE to sync with the NTP server. Even though the server is in the sh ntp output as more reliable and Stratum2. When I add the NTP server during setup of the ISE I do not get an NTP sync error.
Table of ContentsIntroductionVersion HistoryPossible Future
UpdatesDocuments PurposeNAT Operation in ASA 8.3+ SectionsRule Types
Network Object NATTwice NAT / Manual NATRule Types used per SectionNAT
Types used with Twice NAT / Manual NAT and Network Obje...
Table of Contents Introduction:This document describes details on how
NAT-T works. Background: ESP encrypts all critical information,
encapsulating the entire inner TCP/UDP datagram within an ESP header.
ESP is an IP protocol in the same sense that TCP an...