vSAN VUM integration can trigger the "vSAN Build Recommendation Engine Health" alert, even if VUM is not used for upgrading vSAN cluster(s).
When encountered, messages similar to below can be seen in vCenter's /var/log/vmware/vsan-health/vmware-vsan-health-summary-result.log, example:
INFO vsan-mgmt[#######] [VsanHealthSummaryLogUtil::PrintHealthResult opID=noOpId] Cluster Name-of-the-Cluster Overall Health : yellow Group vum health : yellow Test vumconfig health : yellow Com.Vmware.Vsan.Health.Test.Cloudhealth.Cloudhealthconfig.Testresult.Label: Com.Vmware.Vsan.Health.Test.Cloudhealth.Cloudhealthconfig.Testresult.Columnissue (Com.Vmware.Vsan.Health.Test.Cloudhealth.Isodepotisdown),
NOTE: this can happen despite:
- vCenter having connectivity with the internet,
- Token-based authentication correctly implemented (REF: VCF authenticated downloads configuration update instructions / https://knowledge.broadcom.com/external/article/390098).
vCenter Server 8.0 Update 3
This issue is due to changes how VMware Software Binaries are downloaded, more information on this topic is available at https://blogs.vmware.com/cloud-foundation/2025/03/24/download-changes-vmware-software-binaries/
In cases where VUM is not used for upgrades of vSAN clusters, user may chose to disable VUM integration in order to alleviate "vSAN Build Recommendation Engine Health" alerts.
To disable VUM integration:
1. Log into vCenter Appliance over SSH with root privileges.
2. Make a backup of /etc/vmware-vsan-health/config.conf config file, for example:
cp /etc/vmware-vsan-health/config.conf /etc/vmware-vsan-health/config.conf.backup
3. Edit /etc/vmware-vsan-health/config.conf and change 'enabled' parameter in [VumIntegration] section to False, example:
[VumIntegration] enabled = False
4. This should be followed by restart of vsan health service:
vmon-cli -r vsan-health
vSAN Build Recommendation Engine not able to generate baselines for host upgrade / https://knowledge.broadcom.com/external/article/400034