Not Responding' state in the vCenter Server UI. /var/log/vmware/vpxd/vpxd.log the same host(s) state has changed to NO_RESPONSE.YYYY-MM-DDTHH:MM:SS:SS warning vpxd[386913] [Originator@6876 sub=MoHost opID=HB-host-####@162289-a5e439e] host [vim.HostSystem:host-####,<host_fqdn>] connection state changed to NO_RESPONSEYYYY-MM-DDTHH:MM:SS:SS info vpxd[06905] [Originator@6876 sub=DAS opID=FdmMonitor-domain-c####-27b36072] Lost connection to master [vim.HostSystem:host-####,<host_fqdn>] - updating host fdm states to unknownYYYY-MM-DDTHH:MM:SS:SS info vpxd[06905] [Originator@6876 sub=MoHost opID=FdmMonitor-domain-c####-27b36072] VC state for host host-#### (FDM unreachable (from VC) -> FDM unreachable (from VC)), FDM state (Master -> UNKNOWN_FDM_HSTATE), src of state (host-#### -> null)
YYYY-MM-DDTHH:MM:SS:SS error vpxd[06767] [Originator@6876 sub=vmomi.soapStub[16209] opID=2a####65] Resetting stub adapter: service state request timed out; a: <</hgw/host-####>, /vpxa>, pa: <last binding: <<UNIX ''>, <UNIX '/var/run/envoy-hgw/hgw-pipe'>> >, timeout: 120sec
YYYY-MM-DDTHH:MM:SS:SS warning vpxd[386913] [Originator@6876 sub=InvtHostCnx opID=HB-host-####@162289-a5e439e] Exception occurred during host sync; Host communication failed; [vim.HostSystem:host-####,<host_fqdn>], e: N5Vmomi5Fault17HostCommunication9ExceptionE(Fault cause: vmodl.fault.HostCommunication
/var/run/log/vpxa.log. YYYY-MM-DDTHH:MM:SS:SS In(166) Vpxa[2099484]: [Originator@6876 sub=HTTP.HTTPService.HttpConnection opID=TaskLoop-host-####-5e] HTTP Connection has timed out while waiting for further requests; <io_obj p:0x000000abf3e1cac0, h:-1, <TCP '127.0.0.1 : 8089'>, <TCP '127.0.0.1 : 58364'>>, N7Vmacore16TimeoutExceptionE(Operation timed out: Stream: <io_obj p:0x000000abf3e1cac0, h:-1, <TCP '127.0.0.1 : 8089'>, <TCP '127.0.0.1 : 58364'>>, duration: 00:20:04.830186 (hh:mm:ss.us))YYYY-MM-DDTHH:MM:SS:SS info vpxd[06315] [Originator@6876 sub=MoHost opID=HostSync-host-####-7d6de18c] host [vim.HostSystem:host-####,<host_fqdn>] connection state changed to CONNECTEDThis issue will occur when there is an interruption in the physical network responsible for carrying and delivering the network communication between the vCenter Server and the ESXi host that is in "Not Responding" state.
Additional troubleshooting steps for this issue can be found in KB Intermittent network connectivity on ESXi or host disconnect issues.