VCF 9 installer fails to deploy during the ESXi host vSAN HCL compatibility check for vSAN ESA disks because the vSAN HCL database is over 90 days old
Article ID: 412606
Updated On:
Products
Issue/Introduction
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
Environment
VCF 9.x
Cause
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.
Resolution
When the VCF installer is connected to an online depot, the latest vSAN HCL database is normally downloaded during the validation process.
If VCF installer is in an offline environment and cannot directly download the latest vSAN HCL database, you can update vSAN HCL database manually.
- Download the latest vSAN HCL database.
https://vvs.broadcom.com/service/vsan/all.json - Copy the downloaded all.json file to the /nfs/vmware/vcf/nfs-mount/ on the VCF installer appliance
- Access the VCF installer appliance via ssh and switch to the root user
- Move the all.json file into the designated vSAN HCL directory
# mv /nfs/vmware/vcf/nfs-mount/all.json /nfs/vmware/vcf/nfs-mount/vsan-hcl - Change the file owner.
# chown vcf_lcm:vcf /nfs/vmware/vcf/nfs-mount/vsan-hcl/all.json - From the VCF installer UI, execute Re-run Validations to trigger the HCL database check
Additional Information
Feedback
