Using the VCF 9 Installer, previously, managing vSAN ESA clusters, such as creation, expansion, and stretching, required certified vSAN ESA disks. This limitation prevented users from evaluating vSAN ESA if their existing disks were not certified. The VCF installer strictly validates disk certification against the local HCL database, which may not recognize certain NVMe firmware/model strings even if the hardware is compatible.
Symptoms may include the VSAN_ESA_HOST_NOT_HCL_COMPATIBLE error code, or the failure of the 'vSAN ESA Disks Eligibility' subtask.
To address ESX Host vSAN HCL Compatibility, a new configurable property allows users to evaluate vSAN ESA features within the SDDC Manager workflow, even when using non-certified SSD disks.
Note:
This configurable property should be used only when the vSAN ESA disks are listed in the HCL JSON but cannot be programmatically verified as supported by the installer.
5.2.2, 9.0.1.0
To enable this feature:
VCF Cloud Builder Bringup (5.2.2)
vsan.esa.sddc.managed.disk.claim=true" to /etc/vmware/vcf/bringup/application.propertiessystemctl restart vcf-bringupVCF Installer Bringup (9.0.0.0+)
vsan.esa.sddc.managed.disk.claim=true" to /etc/vmware/vcf/domainmanager/application.propertiessystemctl restart domainmanagerHost Commission.
vsan.esa.sddc.managed.disk.claim=true" to /etc/vmware/vcf/operationsmanager/application.propertiessystemctl restart operationsmanagerCreate Domain/Cluster, Add Host, and Stretch Cluster
vsan.esa.sddc.managed.disk.claim=true" to /etc/vmware/vcf/domainmanager/application.propertiessystemctl restart domainmanager