Launching soon: The world's first vendor agnostic bug scrubLearn more & join waitlist
OPERATIONAL DEFECT DATABASE
...
...
ESXi host is not responding to vCenter ServerAll virtual machines that are registered to the ESXi host are grayed out.You are unable to connect to the ESXi host directly using vSphere Client.The vpxd.log files residing in vCenter Server may contain events indicating an error when attempting to communicate with the ESXi host. The events always contain the words vmodl.fault.HostCommunication and may appear similar to the following examples: [VpxLRO] -- ERROR task-internal-6433833 -- host-24499 -- vim.host.NetworkSystem.queryNetworkHint: vmodl.fault.HostCommunication: (vmodl.fault.HostCommunication) { dynamicType = <unset>, faultCause = (vmodl.MethodFault) null, msg = "", } [VpxdMoHost::CollectRemote] Stats collection cannot proceed because host may no longer be available or reachable: vmodl.fault.HostCommunication. For more information on the location of the vpxd.log file, see Location of vCenter Server log files (1021804) .The issue may appear on multiple hosts, keep note on the opID that identifies the offending ESXi host:2012-04-09T15:03:51.540-04:00 [29348 verbose 'Default' opID=f6a80d55] [ServerAccess] Attempting to connect to service at vc1.hostname.vmware.net:10443 If this issue occurs due to a communication issue between the ESXi host and the vCenter Server, but the host is still responsive to user interaction, you may see events similar to these in the /var/log/vmware/vpxa.log files: Failed to bind heartbeat socket (-1). Using any IP. Agent can't send heartbeats.msg size: 66, sendto() returned: Network is unreachable.
This article provides troubleshooting steps to determine why an ESXi host is inaccessible from vSphere Client.
Networking issue, ESXi host hardware related,storage,hostd or other services.
None
To determine why an ESXi host is inaccessible: Verify the current state of the ESXi host hardware and power. Physically go to the ESXi host hardware, and make note of any lights on the face of the server hardware that may indicate the power or hardware status. For more information regarding the hardware lights, consult the hardware vendor documentation or support. Note: Depending on the configuration of your physical environment, you may consider connecting to the physical host by using a remote hardware interface provided by your hardware vendor. For more information about how this interface interprets the condition of the hardware, consult the hardware vendor documentation or support. If the hardware lights indicate that there is a hardware issue, consult the hardware vendor documentation or support to identify any existing hardware issues.If the hardware is currently turned off, turn on the hardware and see Determining why a ESX/ESXi host was powered off or restarted (1019238). Determine the state of the user interface of the ESXi host in the physical console. Note: Depending on the configuration of your physical environment, you may consider connecting to the physical host by using a remote application such as a Keyboard/Video/Mouse switch or a remote hardware interface provided by your hardware vendor. These interfaces are known to interfere with keyboard and mouse functionality. VMware recommends verifying the responsiveness at the local physical console prior to taking any action. If the user interface does not respond to user interaction, see Determining why an ESX/ESXi host does not respond to user interaction at the console (1017135).If the user interface displays a purple diagnostic screen, see Interpreting an ESX/ESXi host purple diagnostic screen (1004250). Verify that DNS is configured correctly on the ESX/ESXi host. For more information, see: Configuring VMware ESXi Management Network from the direct console (1006710)Clearing the DNS cache in VMware ESXi host (2117593)Reconnecting or adding an VMware ESXi host to VMware vCenter Server fails with the error: Agent can't send heartbeats because socket address structure initialization is failing (2091510)Identifying issues with and setting up name resolution on ESX/ESXi Server (1003735) Determine if the ESXi host responds to ping responses, there are several menu options provided to test the management network. If the ESXi host responds to user interaction, but does not respond to pings, you may have a networking issue. For more information, see ESXi hosts have intermittent or no network connectivity (1004109). Verify that you can connect to the VMware ESXi host using vSphere Client: Open the vSphere Client.Specify the hostname or IP address of the VMware ESXi host, along with the appropriate credentials for the root user.Click Login. If you receive an error indicating that a connection failure occurred, it may indicate that the agents responsible for facilitating the vSphere API are not functioning. For more information, see Diagnosing the vSphere Client when it fails to connect to an ESXi host or vCenter Server (1003870).If you are able to connect to the VMware ESXi host using the vSphere Client, but it continues to show as unresponsive from vCenter Server, verify if the correct Managed IP Address is set in vCenter Server. For more information, see Diagnosing an ESXi host that is disconnected or not responding in vCenter Server (1003409). Determine if the ESXi host is rebooted. Physically log in to the console of the ESXi host. Login to tech support mode see Using Tech Support Mode in ESXi 4.1, ESXi 5.x, and ESXi 6.0 (1017910). Type the command uptime to view the uptime of the ESXi host. If the ESXi host is recently rebooted, see Determining why a ESXi host was powered off or restarted (1019238).
For related information, see Assessing commonalities of an outage affecting multiple virtual machines (1019000). High Availability High Availability (HA) feature uses a different trigger than vCenter Server when ensuring that an ESXi is operational. The following is a brief explanation of each criteria: The Host connection and power state alarm is triggered as a result of a HostCommunication fault. A HostCommunication fault occurs if vCenter Server is unable to communicate to an ESXi host using the vSphere API.The HA isolation response is triggered as a result of an agent on the ESXi host that is unable to communicate with agents on other ESXi hosts (not the vCenter server). It must also fail to communicate with a designated isolation address (by default, it is the default gateway). If both of these conditions are met, the host performs the designated HA isolation response. Both systems are managed by different agents and may communicate with different hosts on the network. Therefore, with respect to the relationship: A host that is not responding within vCenter Server does not always trigger a high availability isolation response. It may still be maintaining a network connection with other hosts or its isolation address and thus is not isolated .A host experiencing an HA isolation response is likely to appear as Not Responding within vCenter Server. Troubleshooting an ESXi/ESX host in non responding stateTesting network connectivity with the ping commandTech Support Mode for Emergency SupportIdentifying issues with and setting up name resolution on ESX/ESXi ServerDiagnosing the vSphere Client when it fails to connect to an ESX/ESXi host or vCenter ServerESX/ESXi hosts have intermittent or no network connectivityInterpreting an ESX/ESXi host purple diagnostic screenConfiguring VMware ESXi Management Network from the direct consoleDetermining why an ESX/ESXi host does not respond to user interaction at the consoleUsing Tech Support Mode in ESXi 4.1, ESXi 5.x, and ESXi 6.xAssessing commonalities of an outage affecting multiple virtual machinesDetermining why an ESXi/ESX host was powered off or restartedLocation of log files for VMware productsESX/ESXi ホストは非応答およびグレー表示されていますESX/ESXi 主机不响应且灰显Reconnecting or adding an VMware ESXi host to VMware vCenter Server fails with the error: Agent can't send heartbeats because socket address structure initialization is failingClearing the DNS cache in VMware ESXi 5.5 and later hosts