The VCF 9 Installer performs a pre-validation using an offline HCL JSON file to determine if the vSAN ESA disks/controllers are listed on the HCL.
If the drives are not present, or if the validation process encounters any issues, the deployment is halted.
VCF installer UI reports: No vSAN ESA certified disks found on the ESXi Host #######Remediation: No vSAN ESA certified disks found on the ESXi Host #######. Provide ESXi Host with vSAN ESA certified disk/var/log/vmware/vcf/lcm/lcm-debug.log . The VCF Installer cannot connect to a depot to download the latest HCL
1The HCL file defaults to the embedded HCL file that is older than 90 days
ERROR [vcf_lcm,0000000000000000,0000] [c.v.e.s.l.s.i.v.VsanHclDownloadRunner,HCL-Sync-1] Failed to download HCL file
com.vmware.evo.sddc.lcm.model.error.LcmException: vSAN HCL service API invocation failed. HCL Client Error : Failed to process fetched last update time of HCL with exception vsanhealth.vmware.com: Name or service not known
2.
DEBUG [vcf_lcm,0000000000000000,0000] [c.v.e.s.l.s.i.v.VsanHclDownloadUtil,HCL-Sync-1] Timestamp of data: 1767691299, current timestamp: 1787237837, difference in days: 226
VCF 9.x
1. vSAN HCL database file that the installer is using is more more than 90 days old.
Verify the date from this file: /nfs/vmware/vcf/nfs-mount/vsan-hcl/all.json
The latest version available can be validated from https://vvs.broadcom.com/service/vsan/all.json.
2. The VCF Installer is not connected to an offline or online depot
When the VCF installer is connected to an online depot, the latest vSAN HCL database is normally downloaded during the validation process.
First, confirm the VCF Installer can reach the offline depot and the HCL file in the offline depot is the most recent version.
Once a connection is established to the offline depot and the latest vSAN HCL file is present proceed with the deployment.
When the VCF installer is in an offline environment or cannot establish a connection to the offline depot and does not have the latest vSAN HCL database, you can update vSAN HCL database manually.
# mv /nfs/vmware/vcf/nfs-mount/all.json /nfs/vmware/vcf/nfs-mount/vsan-hcl# chown vcf_lcm:vcf /nfs/vmware/vcf/nfs-mount/vsan-hcl/all.json