Highlighted
Contributor
Contributor

NTP settings on host <esxi host> is different from the desired settings.

Hi,

I have created a vSan Cluster via Quickstart configuration. The Cluster itself is running and healthy. After the deployment I changed the NTP Settings of my vCenter Server Appliance and ESXi hosts. The Skyline Host compliance check for hyperconverged cluster configuration now shows me the warning “NTP settings on host <esxi host> is different from the desired settings.”.

sshot-1.png

https://kb.vmware.com/s/article/58896 states:

„4. NTP setting
NTP setting on hosts should be the same with the specifications. NTP setting will be persistent if it's configured via QuickStart and health check reports a warning if the NTP setting on the host is not consistent with the cluster level. If NTP is not configured in QuickStart, the health check will not validate NTP compliance status, then the user can configure it on the host later.
How to set NTP.“

Is there a way to change the NTP settings set during Quickstart / the value to validate against?

Or is my only option to recreate the cluster / silence the alert?

Thanks

0 Kudos
3 Replies
Highlighted
VMware Employee
VMware Employee

Hello roffty​,

Welcome to Communities.

What build of ESXi/vCenter in use here?

I haven't had the time to validate what (if any) changes to this there have been in 7.0 U1, but in 6.7 U3/7.0 GA this is unfortunately not configurable/changeable after inception e.g. if the settings have changed to be something other than the initial Quickstart configuration then they will always appear as non-compliant (as they are) and thus it is a case of going with the options of recreate or silence the alert.

I will ping back here when I get around to doing more in-depth testing of whether this is the case in 7.0 U1.

Bob

0 Kudos
Highlighted
Contributor
Contributor

Hello TheBobkin,

Thank you!

vCenter

Version: 7.0.1 Build: 16858589

ESXi:

Version: 7.0.1 Build: 16850804

Roffty

0 Kudos
Highlighted
Contributor
Contributor

Hello,

 I have the same warning in vSAN skyline health with VMware ESXi, 7.0.1, 16850804

0 Kudos