Life is a journey, not a race!

enjoy the journey

"Troubleshooting FDM and HA issue in VMware Cluster"

 

 

be careful when you want to install Patch on your vCenter!
after you patch your vCenter 7.0 U3 to higher version, maybe you faced some issues regarding HA on cluster. for example I received bunch of errors like:

Error: "vSphere HA agent cannot be correctly installed or configured"


or


After update to ESXi 7.0 Update 3 vSphere HA fails to enable


or


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

ok folks, now we will see how we can knockdown the all Error messages and fix FDM problem on our cluster.

 


Caution: ""DO NOT TRY TO REMOVE FDM PACKAGE, IF YOU CAN NOT PUT YOUR HOST IN MANTENANACE MODE""

 


just imagine, today is your vCenter patch day and you do it over vCenter appliance and after reboot, try to login on your vCenter to check the cluster health, but you faced FDM and High Availability problem!

whats the right way to troubleshoot and find the problem?

01. try to disable HA on your Cluster and Enable it again.

if problem exist

02. disable HA, check the vib packages and looking after i40enu!
put the host in Maintenace mode, remove the package, reboot your Host. do same for your all Host.
hashtag#hint: esxcli software vib remove --vibname=i40enu

if problem exist

03. try to update the FDM package on your Hosts. you have to copy the right FDM version from your vCenter with WinScp,

 

# /etc/vmware-vpx/docRoot/vSphere-HA-depot/vib20/vmware-fdm/

 

then upload it to your Shared storage, I suggest to upload it on local Storage, try to find out the difference between ESXi FDM and vCenter with :

esxcli software vib list |grep fdm

then if you find the FDMs are different, you can start update process:

esxcli software vib update -v /tmp/VMware_bootbank_vmware-fdm_x.x.x-xxxxxx.vib -f

03.1. after executing the command, you received error regarding Volume, never mind, try to rescan Storage for your host from vCenter GUI, then try step 03 again!

after vib update, you can check the vib version by this command:

esxcli software vib list |grep fdm

now you can see the FDM version is exactly same with your vCenter. then when you done for all Hosts, you can safely Enable HA on your Cluster.


be happy 😎 😁

#VMware #ESXi #Cloudhba #FDM #HA #Cluster #Error

vExpert Badge