Loading...
Loading...
Unable to install or update the vCenter Server vSphere High Availability (vSphere HA) agent service. The vmware-fdm VIB is the package that runs this service on each ESXi host Powering on virtual machines fails with error: The host is reporting errors in its attempts to provide vSphere HA support In the VMware vCenter Server summary, you may see this vSphere HA service error: vSphere HA agent for this host has an error: vSphere HA agent cannot be correctly installed or configure
Provide information on how to troubleshoot and fix vSphere HA not configuring on ESXi hosts.
Some things which can cause this issue include: ESXi host problem with third-party VIBESXi host heartbeat datastore problemsESXi host OS problemsvCenter Server OS problems
When ESXi host cannot install or configure to join the vSphere HA agent, VMs may not vMotion to it or may not restart on another ESXi host if the problem ESXi host fails.Restarting management agents on ESXi hosts risks that the agents don't fully restart. In that situation you may find you have to shut down the running VMs on the host and reboot the host to recover.
To resolve this issue: If the error is "vSphere HA agent is unreachable" follow vSphere HA agent is unreachable and the Summary tab of the ESXi host reports the error: vSphere HA reports that an agent is in the Agent Unreachable stateIf the ESXi host is in a vSAN cluster, ensure: It is networked to, configured for, and participating in the vSAN cluster.It is showing good health for vSAN per Check vSAN Health. Disconnect, then reconnect the ESXi host to vCenter In the vCenter GUI, use the Hosts and Clusters view,Right-click the ESXi host and select Connection > DisconnectRight-click the ESXi host and select Connection > ConnectDisable, then re-enable vSphere HA for the cluster per Configuring vSphere Availability Settings. If the problem persists, check whether the vSphere HA agent service needs restarting per Reconfiguring HA (FDM) on a cluster fails with the error: Operation timed out.If the problem persists, restart the vSphere HA service for the cluster Turn vSphere HA off for the whole cluster per Disabling VMware High Availability (HA). Turn vSphere HA back on for the whole cluster per Configure vCenter HA With the vSphere Client. If the problem persists, check whether the ESXi host version is compatible with the vCenter Server version per the VMware Product Interoperability Matrix. If not compatible, upgrade the software appropriately.If upgrading your ESXi hosts, always check the VMware Compatibility Guide to ensure the server hardware is compatible with the new ESXi version. If the problem persists, follow ESXi host not responding , /tmp folder 100% to check and resolve if the ramdisk /tmp directory is too full.If the problem persists, review the /var/run/log/fdm-installer.log file: cat /var/run/log/fdm-installer.log |less If you see errors for third-party VIBs such as the below see Resolve third-party VIB preventing vSphere HA agent updates: bootbank_qlogic_hcli_2.2.60.7.0.0vmw.500.0.0.472560 violates extensibility rule: Installing the VIB fdm-installer: [24683] 2013-07-18 18:41:45: Result of esxcli software vib install -v=/tmp/vmware-root/ha-agentmgr/vpx-upgrade-installer/vmware-fdm.vib: [DependencyError] fdm-installer: VIB QLogic_bootbank_qlogic_hcli_2.2.60.7.0.0vmw.500.0.0.472560 violates extensibility rule checks: [u'(line 31: col 0) Element vib failed to validate content'] fdm-installer If you see errors in the fdm-installer.log indicating a boot is needed The ESXi host will need to be rebooted.See Configuring vSphere HA fails with the error: Cannot install the vCenter Server agent service. Unknown installer error. If the problem persists, check for heartbeat datastore problems per Troubleshoot ESXi heartbeat datastore problems affect vSphere HA.If the problem persists, restart the Platform Services Controller (if your vCenter uses an external PSC). Once it finishes rebooting, then restart the vCenter Server managing the ESXi host. Note that versions 7.x have no external PSC, it is always embedded into vCenterIf you're running a 6.x version and unsure if your vCenter uses an external PSC or which device the external PSC is, follow How to find your vCenter Server's PSC. If the problem persists, rule out network issues Ensure that if the ESXi host vmnics MTU size is set uniformly, across all switch ports and other infrastructure are allowing that MTU to go through. Ensure that no firewall changes were made to the ESXi host or network switches blocking ports 80, 443, or 902 between hosts and vCenter Server. If the problem persists, restart management services on the ESXi host per Restarting the Management agents in ESXi.If the problem persists, follow the bottom half of the article Resolve third-party VIB preventing vSphere HA agent updates, starting at "To remove the vSphere HA agent VIB".If the problem persists, reboot the ESXi host.
FDM stands for "Fault Domain Manager" which is the original name for the vSphere High Availability feature.VMware Skyline Health Diagnostics for vSphere - FAQFor more information on enabling and reconfiguring HA, see the vSphere 7.0 Availability Guide.Restarting the Management agents in ESXiAfter update to ESXi 7.0 Update 3 vSphere HA fails to enableCannot install Fault Domain Manager agent for VMware HA after agent is uninstalledCannot configure HA after disabling the Host Welcome login page on an ESXi hostvSphere HA (FDM) agent fails to install on an ESXi host when network traffic throughput between ESXi and vCenter Server is insufficient.VMware vSphere 5.x High Availability (FDM) fails to configure and a timeout is reported during HA electionConfiguring HA on an ESXi 5.x host fails with the error: Cannot install the vCenter agent service. Unknown installer errorエラー: vSphere HA エージェントは正しくインストールまたは構成できません错误: “无法正确安装或配置 vSphere HA 代理 (vSphere HA agent cannot be correctly installed or configured)”
Click on a version to see all relevant bugs
VMware Integration
Learn more about where this data comes from
Bug Scrub Advisor
Streamline upgrades with automated vendor bug scrubs
BugZero Enterprise
Wish you caught this bug sooner? Get proactive today.