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.”.
„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?
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.
Any good news about this issue? If the vSAN in production state, we cannot rescreate it, and customer hate some stuff like warning ignoring...
Can we do some esxcli magic or any else to resolve this problem?
Same issue here. Used Quickstart wizard to configure a single NTP server, then added a second NTP server later on. Cannot find a way to update Quickstart parameters such as NTP servers, post deployment. This is vCenter 7.0U1c and ESXi 7.0U1c. This is a fairly major limitation with Quickstart, as editing parameters such as NTP servers should be very routine and non-disruptive. Can this be flagged as an issue to get resolved in a future update?
I've recently built a 3 node x 7.0.2 cluster and the QuickStart has the exact same issue. I changed my NTP server per each host and VCSA, now QuickStart shows all nodes are non-compliant NTP Settings. I've searched web client for a way to reset with no avail.
I fixed it
A lite bit risky, so recommended to backup your VCSA before operation
login your VCSA via SSH
/opt/vmware/vpostgres/current/bin/psql -U postgres -d VCDB
you can get your cluster_id of vSAN by the following SQL:
select * from vc.vpx_hci_config_info;
Get current configuration by the following SQL:
select datetime_config from vc.vpx_hci_config_info;
update vc.vpx_hci_config_info set datetime_config='<obj xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns="urn:vim25" versionId="184.108.40.206" xsi:type="HostDateTimeConfig"><ntpConfig><server>220.127.116.11</server><server>18.104.22.168</server></ntpConfig></obj>' where cluster_id=24;
Need to restart VCSA it seems that vSAN has loaded the configuration into memory so Updating the configuration in DB does not work if without restart VCSA
Use the PowerCLI AddHostNtpServer commandlet, don't go messing around with the database. Personally, I skip the quickstart and have my own configuration script to set my common settings. It is a hold over from ESX 6.x days, but I've heard of some craziness with QuickStart that makes me think it's better to keep a simple script around.