In this quick and small blog postfix about vSAN. I get in vSAN Health Network checks an error with one of the vSAN ESXi hosts: “Checks if API calls from VC to a host are falling while the host is in connected state”.
In VMware KB we can’t find much information about how to fix it, only states that this is very rare to happen.
Note: vSAN API Calls are used for vCenter/vSAN communication with ESXi hosts.
The first thing to check is if the vSAN Health service is running on the faulty ESXi host with the command: /etc/init.d/vsanmgmtd status.
Has we can check above that the service was in a stopped state.
You can also double check vsanmgmtd service log to check if you have any extra information about the problem that stopped your service, in: /var/log/vsanmgmt.log.
In my case I did not find anything that could give me any answer, so I decided just to start the service: /etc/init.d/vsanmgmtd start
After starting the service and rerun “Retest with Online health” (I always use the online option) all went green and no issues found and the error is gone. It seems was just the service was down and vSAN was not able to communicate with ESXi hosts using the vSAN Health monitor.
Note: Something that can also trigger this error is vCenter/vSAN version build is different from the ESXi version build. Always have them running at least in the same build/update.
Even this error is a bit general and VMware doesn’t present a proper solution, in this case, was just a service down, I hope this small tip was useful to fix this type of error on your vSAN.
Share this article if you think it is worth sharing. If you have any questions or comments, comment here, or contact me on Twitter.