Problems with cluster HA or DRS may occur at any time. If you have a problem with vSphere HA, you must first check the HA logs stored in /var/log/fdm.log. A typical problem can occur during the installation of the FDM agent (HA agent) to the ESXi host. The relevant logs are located in /var/log/esxupdate.log.

If you have a problem with the /root partition space, it is possible to control the partition through the CLI with the vdf command.

Other possible problems in the cluster can be related to VMkernel ports, VMs reservation on the target host, and incorrect network time. If the time is not synced in the VMware environment, you can have issues. Another typical vMotion issue is often due to misconfiguration of the IP address or VLANs.

To check the VMkernel, you can use the ping command, but when using the vMotion stack, you should use the ++netstack=vmotion parameter.

DRS can also cause a problem with vMotion. Keep in mind that DRS uses vMotion to balance resources. Sometimes, a problem is simply due to DRS misconfiguration (manual or fully automated setup) or related to DRS rules.