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

My Subscriptions

Loading

Knowledge Base

Identifying issues with and setting up name resolution on ESX/ESXi Server (1003735)

Last Updated: 3/21/2024Categories: TroubleshootingTotal Views: 238364Language:
English

4 like this article

Subscribe to get an email
newsletter with new updates

4 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

Unable to configure VMware High Availability (HA).

Configuring VMware HA fails at about 97% completion.

Configuring VMware HA fails between 85 to 91%.

Reconfiguring VMware HA fails.

Adding an ESX host to a cluster fails.

Enabling VMware HA in a cluster fails.

These errors are generated when attempting to configure VMware HA:

An error occurred during configuration of the HA agent on the host

HA agent on <ESX> in cluster <cluster> in <Datacenter> has an error

Error: Cannot complete the configuration of the HA agent on the host. Other HA configuration error

cmd addnode failed for primary node:/opt/vmware/aam/bin/ft_startup failed

Host fails to remediate or exit Maintenance Mode.

You see these errors:

Operation timed out

Unable to connect to the MKS: Host address lookup for server failed: No such host is known

In the Tasks view of VirtualCenter/vCenter Server, you see the error:

There are errors during the remediation operation

Failed to find host

Update Manager is unable to scan ESX/ESXi hosts.

Host disconnects from the vCenter Server.

ESX/ESXi host enters a not responding state in the vCenter Server.

Note: A common cause for an ESX/ESXi host dropping out of vCenter Server is due to the DNS (both forward and reverse) not functioning or configured correctly.

Purpose

The errors listed in the Symptoms section are generated as a result of name resolution issues.

This article guides you through identifying issues with name resolution which can seriously impact the normal operation of ESX/ESXi, particularly in HA clustered environments. The article also details correctly configuring host files when there is no DNS server in the environment, or if the DNS server is incorrectly configured.

Resolution

Identifying issues

There is a problem with name resolution if any of these tests fail. ESX/ESXi hosts must be able to find each other by:

IP address

Short Name

Fully Qualified Domain Name (FQDN)

If an issue with name resolution has been identified it must be resolved either on the DNS server or by using hosts files.

Note: After making any changes to DNS or hosts files, ensure that you delete the file /etc/FT_HOSTS (or /etc/opt/vmware/aam/FT_HOSTS and /var/run/vmware/aam/FT_HOSTS ) on all affected ESX/ESXi hosts.

Verify that all ESX/ESXi hosts can ping each other by short name. All ESX/ESXi hosts in the environment must be able to ping each other by using short name only. For more information, see Testing network connectivity with the ping command (1003486).

Verify that all ESX/ESXi hosts can nslookup each other.

Use nslookup (reverse IP address lookup) to verify that the appropriate name is associated to a particular IP address.

For example:

[root@esx-server-1 /]# nslookup 192.168.0.5

Server: 192.168.0.7

Address: 192.168.0.7#53

5.0.168.192.in-addr.arpa name = esx-server-2.domain.com

Verify that all ESX/ESXi hosts can reverse nslookup each other.

Use nslookup (forward IP address lookup) to verify that the appropriate IP address is associated to a particular name.

For example:

[root@esx-server-1 /]# nslookup esx-server-2

Server: 192.168.0.7

Address: 192.168.0.7#53

Name: esx-server-2.domain.com

Address: 192.168.0.5

Verify that the DNS server has both an A Record (Address Record) and a C NAME record (Canonical name record) configured for each ESX/ESXi hosts.

Additional checks for VMware High Availability (HA) environments - ESX/ESXi 3.x and 4.x Only

Perform these additional checks for VMware High Availability environments with ESX/ESXi versions 3.x and 4.x (this does not apply to ESXi 5.0):

Verify that the reported host name is in lowercase when you run:

[root@esx-server-1 /]# hostname

[root@esx-server-1 /]# hostname -s

Verify that all host names in /etc/hosts are in lowercase.

Verify that the search domain in /etc/resolv.conf is in lowercase.

Verify that the host name in /etc/sysconfig/network is a fully qualified domain name, and is lowercase.

Verify that the host name in /etc/vmware/esx.conf is a fully qualified domain name, and is lowercase.

If your ESX/ESXi hosts are registered in DNS, verify that your system host name is lowercase and the record is a A name. Run this command to ensure the FQDN is resolvable and all lowercase:

nslookup short_hostname

Verify that all primary Service Consoles in the VMware HA cluster have the same name.

Verify that all primary Service Consoles are in the same IP subnet.

Note: If a VMotion VMkernel port is on the same vSwitch as the primary Service Console, or if a host has multiple Service Consoles, see Incompatible HA Networks appearing when attempting to configure HA (High Availability) (1006541).

Configuring hosts files on ESX/ESXi

The hosts file on the ESX host is located at /etc/hosts .

Open the file for editing using a text editor such as nano or vi .

Example hosts file:

# Do not remove the following line, or various programs
# that require network functionality will fail.
127.0.0.1 localhost.localdomain localhost

# Any line beginning with a pound sign is a comment and will not be read.
192.168.0.5 esx-server-1.domain.com esx-server-1
192.168.0.6 esx-server-2.domain.com esx-server-2

# The VMware Virtual Center Server must also have an entry here
192.168.0.20 virtualcenter.domain.com virtualcenter

Notes:

localhost must always be present in the hosts file. Do not modify or remove the entry for localhost .

The hosts file must be identical on all ESX/ESXi hosts in the cluster.

There must be an entry for every ESX/ESXi host in the cluster.

Every host must have an IP address, Fully Qualified Domain Name (FQDN), and short name.

The hosts file is case sensitive. Be sure to use lowercase throughout the environment.

Note: This issue has been resolved in vCenter 2.5 U3 and above. For more information, see VMware HA Can Be Configured on a Cluster Regardless of the Letter Case of the ESX Server Host Names in the Resolved Issues section of the VirtualCenter 2.5 Update 3 Release Notes.

Related Information

Testing network connectivity with the ping command
Incompatible HA Networks appearing when attempting to configure HA (High Availability)
ESX/ESXi Server における名前解決の問題の特定とセットアップ
Identificar problemas e configurar a resolução de nomes no ESX/ESXi Server
Identificar problemas con la resolución de nombres en ESX/ESXi Server y configurarla
ESX/ESXi 服务器上的名称解析问题识别及设置

Detectable by VMware SkylineTM

Actions

Copy

link to clipboard
copied!

Print

Language:
English

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:

VMware vSphere ESXi

VMware ESX Server

Related Versions:

VMware vSphere ESXi 6.7

VMware vSphere ESXi 6.5

VMware vSphere ESXi 6.0

VMware vSphere ESXi 5.5

VMware vSphere ESXi 5.1

VMware vSphere ESXi 5.0

VMware ESXi 4.1.x Installable

VMware ESXi 4.1.x Embedded

VMware ESXi 4.0.x Installable

VMware ESXi 4.0.x Embedded

VMware ESXi 3.5.x Installable

VMware ESXi 3.5.x Embedded

VMware ESX Server 3.5.x

VMware ESX Server 3.0.x

VMware ESX 4.1.x

VMware ESX 4.0.x

view all

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