6.x
7.x
vCenter logging within the vpxd.log will show the host is giving bad information
YYYY-MM-DDT00:00:00.000Z info vpxd[39496] [Originator@6876 sub=MoHost opID=SWI-########] Host [vim. HostSystem:host-###, <ESXI_HOSTNAME>]: host Config information is nullptr
YYYY-MM-DDT00:00:00.000Z error vpxd[39441] [Originator@6876 sub=licenseClient opID=LicenseClientProcessInventoryLoadedAsync-########] Bad host information for host-###
YYYY-MM-DDT00:00:00.000Z error vpxd[39441] [Originator@6876 sub=licenseClient opID=LicenseClientProcessInventoryLoadedAsync-########] UpdateAllHostsUsages Failed to get host usages,hostMoId: host-### error: N3Vim5Fault24IncorrectHostInformation9ExceptionE (Fault cause: vim. fault. IncorrectHostInformation
YYYY-MM-DDT00:00:00.000Z info vpxd[39406] [Originator@6876 sub=HostCnx opID=CheckforMissingHeartbeats-########] [VpxdHostCnx] No heartbeats received from host; cnx: ########-####-####-####-############, h: host-###, time since last heartbeat: ######ms
/opt/vmware/vpostgres/current/bin/psql -d VCDB -U postgres -c "UPDATE vpx_host SET enabled = 0 where id = <HOST_ID>;"
NOTE: <HOST_ID> can be identified by selecting the target host in the inventory via the vCenter UI and checkign the web browser URL, host ID will be presented as host-### within the URL, the ### parameter is all that is required for the command above.
service-control --stop --all
service-control --start --all