vSphere HA (FDM) agent fails to install on an ESXi host when network traffic throughput between ESXi and vCenter Server is insufficient
search cancel

vSphere HA (FDM) agent fails to install on an ESXi host when network traffic throughput between ESXi and vCenter Server is insufficient

book

Article ID: 328258

calendar_today

Updated On:

Products

VMware

Issue/Introduction

Symptoms:
  • HA fails to configure on an ESXi 5.x host
  • Unable 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 service
    • vSphere HA agent cannot be correctly installed or configured


    Cause

    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.

    Resolution

    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
    1. Connect to the vCenter Server using RDP.
    2. Verify that you can ping the ESX host.
    3. 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).
    4. 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.
    5. 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
     
    1. Connect to the ESXi with SSH
    2. Confirm that fdm isn't installed already : esxcli software vib list |grep fdm
    3. Connect to the vCenter Server Appliance using SSH.
    4. Verify that you can ping the ESX host.
    5. 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).
    6. 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).
    7. 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.
    8. Install the vib on ESXi : esxcli software vib install -v /tmp/VMware_bootbank_vmware-fdm_x.x.0-xxxxxx.vib
    9. Confirm 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.


    Additional Information

    Troubleshooting network performance issues in a vSphere environment
    Installing vCenter Server 5.0 best practices
    Cannot install Fault Domain Manager agent for VMware HA after agent is uninstalled
    Cannot install the vSphere HA (FDM) agent on an ESXi host
    ESXi と vCenter Server の間のネットワーク トラフィックのスループットが不十分な場合に、ESXi ホストでの vSphere HA (FDM) エージェントのインストールに失敗する

    Powered by Wolken Software