Launching soon: The world's first vendor agnostic bug scrubLearn more & join waitlist
OPERATIONAL DEFECT DATABASE
...
...
HA fails to configure on an ESXi 5.x hostUnable to configure HA on an ESXi 5.x host.In the vSphere Client connected to vCenter Server, you see these errors: Cannot install the vCenter agent servicevSphere HA agent cannot be correctly installed or configured
This issue can occur when network traffic throughput between ESXi and vCenter Server is insufficient and the vCenter Server cannot push the FDM agent to the ESX host over the network in a timely manner.
To verify if this is the issue you are experiencing, copy the FDM install package manually onto the ESXi host and then perform these steps to see if it is possible to manually push the fdm install file from vCenter Server to the ESXi host:For vCenter server windows Connect to the vCenter Server using RDP.Verify that you can ping the ESX host.Verify that SSH is enabled on the ESX host and that port 22 is not blocked. For more information, see Using Tech Support Mode in ESXi 4.1 and ESXi 5.0 (1017910).Using WinSCP or similar software, copy the file C:\Program Files\VMware\Infrastructure\VirtualCenter Server\upgrade\fdm-upgrade-eesx-x-linux-xxxxx to the ESXi tmp folder.If the file fails to copy or takes a long time to copy to the host, insufficient network traffic throughput between ESXi and vCenter Server is preventing the agent from installing. For vCenter Server Appliance Connect to the ESXi with SSHConfirm that fdm isn't installed already : esxcli software vib list |grep fdmConnect to the vCenter Server Appliance using SSH.Verify that you can ping the ESX host.Verify that SSH is enabled on the ESXi host and that port 22 is not blocked. For more information, see Using Tech Support Mode in ESXi 4.1 and ESXi 5.0 (1017910).Using WinSCP, SCP or a similar protocol, copy the fdm vib file located at /etc/vmware-vpx/docRoot/vSphere-HA-depot/vib20/vmware-fdm/ to the ESXi /tmp folder, (e.g. scp VMware_bootbank_vmware-fdm_6.0.0-3634794.vib root@ESXi_FQDN:/tmp).If the file fails to copy or takes a long time to copy to the host, insufficient network traffic throughput between ESXi and vCenter Server is preventing the agent from installing.Install the vib on ESXi : esxcli software vib install -v /tmp/VMware_bootbank_vmware-fdm_x.x.0-xxxxxx.vibConfirm that agent is installed by running : esxcli software vib list |grep fdm If you determine that network traffic throughout is causing the issue, you need to determine what is causing the network issues. Determine if: There is a hardware problem with the NIC. If possible, change the NIC on the management network.There is a mismatch between NIC speed and switch speed.Hardware or a firewall is blocking or slowing traffic.
Troubleshooting network performance issues in a vSphere environmentInstalling vCenter Server 5.0 best practicesCannot install Fault Domain Manager agent for VMware HA after agent is uninstalledCannot install the vSphere HA (FDM) agent on an ESXi hostESXi と vCenter Server の間のネットワーク トラフィックのスループットが不十分な場合に、ESXi ホストでの vSphere HA (FDM) エージェントのインストールに失敗する