Loading

×Sorry to interrupt
CSS Error

Refresh

Cookie Preference Center

General Information on cookies

When you visit our website, we use cookies to ensure that we give you the best experience. This information does not usually directly identify you, but it can give you a more personalized web experience. Because we respect your right to privacy, you can choose not to allow some types of cookies by clicking on the different category headings to find out more and change your settings. However, blocking some types of cookies may impact your experience on the site and the services we are able to offer. Further information can be found in our

Cookie Policy.

Strictly Necessary

Strictly Necessary

Always Active

Strictly Necessary

Strictly necessary cookies are always enabled since they are essential for our website to function. They enable core functionality such as security, network management, and website accessibility. You can set your browser to block or alert you about these cookies, but this may affect how the website functions. For more information please visit www.aboutcookies.org or www.allaboutcookies.org.

Cookie Details‎

Performance

Performance

Performance

Performance cookies are used to analyze the user experience to improve our website by collecting and reporting information on how you use it. They allow us to know which pages are the most and least popular, see how visitors move around the site, optimize our website and make it easier to navigate.

Cookie Details‎

Please confirm your settings by refreshing the page.

Functional

Functional

Functional

Functional cookies help us keep track of your past browsing choices so we can improve usability and customize your experience. These cookies enable the website to remember your preferred settings, language preferences, location and other customizable elements such as font or text size. If you do not allow these cookies, then some or all of these services may not function properly.

Cookie Details‎

Advertising

Advertising

Advertising

Advertising cookies are used to send you relevant advertising and promotional information. They may be set through our site by third parties to build a profile of your interests and show you relevant advertisements on other sites. These cookies do not directly store personal information, but their function is based on uniquely identifying your browser and internet device.

Cookie Details‎

Advertising Cookies

Consent Leg.Interest

Select All Vendors

Select All Vendors

Select All Hosts

Select All

Clear Filters

Information storage and access

Apply

Confirm My Choices Reject All Allow All

Skip to main content

Products and Accounts

Support

Knowledge

Communities

Success

Learning

My Subscriptions

Loading

Knowledge Base

Troubleshooting an ESXi host in a "not responding" state (1003409)

Last Updated: 4/6/2021Categories: TroubleshootingTotal Views: 162699Language:
Chinese (Simplified)Portuguese (European)KoreanJapaneseSpanishEnglishGerman

72 like this article

Subscribe to get an email
newsletter with new updates

72 people found this helpful Please provide article feedback:

Learn how VMware Skyline Advisor and Skyline Health Diagnostics work together to provide proactive intelligence and self-service log analysis.

Use Skyline Advisor to avoid issues before they occur across VCF, vSphere, vSAN, NSX, vROps & Horizon. Skyline Findings are based on top KBs, VMSAs/CVEs and design best practices.

Use Skyline Health Diagnostics to root cause vSphere & vSAN logs when an issue occurs. Skyline Health Diagnostic Findings are based on top KBs and VMSA/CVEs. You can use the Skyline Health Diagnostics tool in online or offline mode.

If you require additional help from technical support, please use Skyline Advisor to initiate a Log Assist to reduce time to upload logs. TSEs can also initiate logs to reduce effort.

Symptoms

An ESXi host shows as "not responding" in vCenter Server.

An ESXi host shows as disconnected in vCenter Server.

Cannot connect an ESXi host to vCenter Server.

Virtual machines on an ESXi host show as greyed out in vCenter Server.

When attempting to add an ESXi to vCenter Server, you see an error similar to:

Unable to access the specified host, either it doesn't exist, the server software is not responding, or there is a network problem

In the vpxd.log file, you see entries similar to:

<YYYY-MM-DD>T<time>.696-05:00 [08128 info 'vpxdvpxdMoHost' opID=37D08048-00006071-85] [HostMo] host connection state changed to [DISCONNECTED] for host-26725

</time>

<YYYY-MM-DD>T<time>.508-04:00 [04944 error 'vpxdvpxdInvtHostCnx' opID=HB-host-385@3560-79f8b53e] [VpxdInvtHostSyncHostLRO] FixNotRespondingHost failed for host host-385, marking host as notResponding
<YYYY-MM-DD>T<time>.633-04:00 [00812 error 'vpxdvpxdInvtHostCnx' opID=HB-host-385@3565-12c9cfec] [VpxdInvtHostSyncHostLRO] FixNotRespondingHost failed for host host-385, marking host as notResponding

</time></time>
For more information, see Location of vCenter Server log files (1021804)

Note: The preceding log excerpts are only examples. Date, time, and environmental variables may vary depending on your environment.

Purpose

This article provides steps to troubleshoot when an ESXi is in disconnected or a not responding state in vCenter Server. In addition, it provides steps to help you eliminate common causes for your problem by verifying that the configuration of your networking and management server agents is correct and confirm the availability of resources on your ESXi host.

Impact / Risks

Refer to each section to understand the impact and risks for those relevant actions.

Resolution

Important: Before proceeding, ensure to familiarize yourself with KB Article Understanding the difference between "Not Responding" and "Disconnected" ESXi hosts in VMware vCenter Server (2121031).

As there are a number of reasons why the ESXi host reaches a “Not Responding” state, VMware strongly recommends to:

Validate each troubleshooting step below is true for your environment.

Each step provides instructions or a link to another Knowledge Base article to eliminate possible causes. You can take corrective action as necessary.

Note: The steps are ordered in the most appropriate sequence to isolate the issue and identify the proper resolution. After each step is completed, try to reconnect the ESXi host back to vCenter Server. Please do not skip a step.

VMware ESXi host that is in a "Not Responding" state

ESXi

Verify that the ESXi host is accessible from vCenter server or vSphere Client.For more information, see ESX/ESXi hosts do not respond and is grayed out (1019082)

Verify that the ESXi host can be reconnected, or if reconnecting the ESXi host resolves the issue. For more information, see Changing an ESXi or ESX host's connection status in vCenter Server (1003480).

Verify that the ESXi host is able to respond back to vCenter Server at the correct IP address. If vCenter Server does not receive heartbeats from the ESXi host, it goes into a not responding state. To verify if the correct managed IP Address is set, see Verifying the vCenter Server Managed IP Address (1008030) and  See also, ESXi host disconnects from vCenter Server after adding or connecting it to the inventory (2040630) and ESXi host keeps disconnecting and reconnecting when heartbeats are not received by vCenter Server (1005757).

Verify that network connectivity exists from vCenter Server to the ESXi host with the IP and FQDN. For more information, see Testing network connectivity with the ping command (1003486).

Verify that you can connect from vCenter Server to the ESXi host on TCP/UDP port 902. For more information, see Testing port connectivity with Telnet (1003487).

Verify if restarting the ESXi Management Agents resolves the issue. For more information, see Restarting the Management agents on an ESXi host (1003490).

Verify if the hostd process has stopped responding on the affected ESXi host. For more information, see Troubleshooting vmware-hostd service if it fails or stops responding on an ESX/ESXi host (1002849)  See also : ESXi host is non-responsive and disconnected in ESXi 6.x (56450)

The vpxa agent has stopped responding on the affected ESXi host. For more information, see Troubleshooting the vCenter Server Agent when it does not start (1006128)

Verify if the ESXi host has experienced a Purple Diagnostic Screen. For more information, see Interpreting an ESX/ESXi host purple diagnostic screen (1004250)

ESXi hosts can disconnect from vCenter Server due to underlying storage issues. For more information, see Identifying Fibre Channel, iSCSI, and NFS storage issues on ESXi/ESX hosts (1003659).

Related Information

Troubleshooting an ESXi host in a "not responding" state
For additional information, see All ESX hosts simultaneously show a status of Not Responding in vCenter (1011878).
Virtual machines appear as invalid or orphaned in vCenter Server

For translated versions of this article, see:

Español: Diagnósticando un host ESX o ESXi que se desconecta o no responde en vCenter Server (2003724)

Português: Diagnosticar no vCenter Server um host do ESX ou ESXi que esteja desconectado ou não esteja respondendo (2032480)

日本語: vCenter Serverから切断、又は無応答となっているESX・ESXiホストの診断方法 (2013645)

简体中文: 诊断在 vCenter Server 中已断开或无响应的 ESXi/ESX 主机 (2048204)

Troubleshooting vmware-hostd service if it fails or stops responding on an ESX/ESXi host
Changing an ESXi or ESX host's connection status in vCenter Server
Testing network connectivity with the ping command
Testing port connectivity with Telnet
Restarting the Management agents in ESXi
Verifying that the Management Service is running on an ESX host
Verifying that the vCenter Server Agent Service is running on an ESX host
Checking for resource starvation of the ESX Service Console
Identifying Fibre Channel, iSCSI, and NFS storage issues on ESX/ESXi hosts
Collecting diagnostic information in a VMware Virtual Infrastructure Environment
Interpreting an ESX/ESXi host purple diagnostic screen
ESXi host disconnects intermittently from vCenter Server
Troubleshooting the vCenter Server Agent when it does not start
Determining if the xinetd service is running on an ESX host
Verifying the VMware vCenter Server Managed IP Address
All ESX hosts simultaneously show a status of Not Responding in vCenter Server
TCP and UDP Ports required to access VMware vCenter Server, VMware ESXi and ESX hosts, and other network components
Determining why an ESXi/ESX host was powered off or restarted
Diagnósticando un host ESX o ESXi que se desconecta o no responde en vCenter Server
非応答の状態でESXi/ESX ホストの診断
ESXi 5.0 hosts are marked as Not Responding 60 seconds after being added to vCenter Server
Diagnosticar no vCenter Server um host do ESX ou ESXi que esteja desconectado ou não esteja respondendo
ESXi/ESX host disconnects from vCenter Server after adding or connecting it to the inventory
排除一个在无响应的状态中的 ESXi/ESX 主机
Diagnostizieren eines in VMware vCenter Server getrennten oder nicht reagierenden ESXi/ESX-Hosts

Detectable by VMware SkylineTM

Actions

Copy

link to clipboard
copied!

Print

Language:
Chinese (Simplified)Portuguese (European)KoreanJapaneseSpanishEnglishGerman

Attachments

Additional Resources

No results for undefined

Ask The Community

Get answers quickly from VMware experts in the community

Post Subject

CONTINUE IN COMMUNITIES

Related Products:

Related Versions:

Take Our Survey

Was this article helpful?

YES

NO

Copyright © 2005-2024 Broadcom. All Rights Reserved. The term “Broadcom” refers to Broadcom Inc. and/or its subsidiaries.

Terms of Use

Your California Privacy Rights

Privacy

Accessibility

Cookie Settings

Support Assistant