VM problem with DRS and HA
Article ID: 400602
Updated On:
Products
Issue/Introduction
- DRS is putting all the VM's onto one or two nodes in a 4 host node cluster
- VM's have no affinity rules to prevent them from moving to other hosts in the cluster
- When clicking on the vCenter Menu > Administration > vCenter Server Extensions > vSphere ESX Agent Manager (for the vCenter in question) > Configure you may see the vSAN file services agency have an alert status
- When you click on the agency you may see the following error: Unable to access agent OVF package file at http://localhost:1080/external-vecs/http1/<vcenter_fqdn>/443/vsanHealth/fileService/ovf/7.0.3.1000-22348816/VMware-vSAN-File-Services-Appliance-7.0.3.1000-22348816-system.vmdk
Environment
VMware vSphere ESXi
VMware vCenter Server
Resolution
Reference KB: Unable to enable vSAN file service after vSAN cluster restart to resolve this issue and used the following steps:
1. Download all 6 vSAN file services files through the Broadcom Portal via KB: Download location of vSAN Witness Appliance and File Service Appliance
Note: Ensure the File Services download version is for the OVF that vCenter EAM Agent is erroring about.
2. SSH into the vCenter appliance, navigate to directory: /storage/updatemgr/vsan/fileService
3. Make a new directory with name ovf-<version> . Example : mkdir ovf-7.0.3.1000-18502520
4. Use scp to copy all 6 OVF files to this new directory: /storage/updatemgr/vsan/fileService/ovf-7.0.3.1000-18502520/
5. Restart the vmware-eam service once complete : service-control --restart eam
Feedback
