- How to use VMware vSAN ReadyNode Configurator - Fri, Dec 17 2021
- VMware Tanzu Kubernetes Toolkit version 1.3 new features - Fri, Dec 10 2021
- Disaster recovery strategies for vCenter Server appliance VM - Fri, Nov 26 2021
The ease of management seems one of the main reasons, but there are others. Most people tend to read words better than numbers. If I needed to manage an environment with 10+ hosts by their IPs, I would be lost. I'd need some kind of a table that would translate the IPs and names, and with this I'd certainly have more chances to introduce an error too.
You know that when you first install VMware vCenter Server and create your first datacenter object and cluster object, you then need to add a host to the cluster object.
vCenter Server itself depends on a domain name system (DNS) too. Before you deploy the vCenter Server Appliance (VCSA) with a static IP address, you must verify that this IP address has a valid internal DNS registration.
Also, you must ensure that DNS reverse lookup returns an FQDN when queried with the IP address of the vCenter Server. It is one of the best practices when you install vCenter Server. Reverse lookup is implemented using pointer (PTR) records.
Let's get back to our ESXi host, which is configured to use our DNS server architecture (you should put at least two DNS servers within the DNS configuration).
And when adding a new host into the cluster, you use the FQDN and not the IP address of the host.
Note: In fact, you need to add at least two hosts into each cluster so you are able to activate some of the cluster's services, such as High Availability (HA), VMware Distributed Resource Scheduler (DRS), or a virtual storage area network (VSAN).
Previously, within vSphere 4.x, an agent was responsible for VMware HA. The agent depended on functional DNS. However, with vSphere 5.x and higher releases, VMware has eliminated this dependency.
In fact, the newer Fault Domain Manager (FDM) HA agent architecture is not dependent on DNS at all. But today, many applications are DNS dependent, and it's normal. Developers creating these applications also seek simplicity because they're human too.
It's up to you as system administrator to eliminate all points of failure in your DNS. That's why your DNS should be redundant. A DNS service should never be offline. If this happens, you have another big issue you have to resolve first.
There are also other factors. A lot of VMware services require proper DNS configuration, for example, single sign-on (SSO), Microsoft Active Directory (AD) integration, and more.
You can probably get along with IP addresses until you start hardening your management connections with trusted certificates. So by the time you'll be deploying your own certificates and replacing the self-signed certificates that VMware provides, you'll certainly need a DNS resolution.
Here is a view of a VMware ESXi host console:
Let's recap some of the advantages and disadvantages of managing vSphere infrastructure when configuring and adding your hosts to vCenter via FQDN versus an IP address.
- Easy to manage because it is easier to remember a name than an IP address
- There are many additional application checks a FQDN resolves
- If you change the ESXi IP, you don't need to remove and re-add the host back to vCenter (not the case with IP only)
Subscribe to 4sysops newsletter!
- DNS server static IP creation
- DNS server infrastructure management (this is disputable of course, as usually there is always a DNS server infrastructure within any IT company)
VMware has eliminated a dependency of their HA function, which is one of the key elements within each cluster. Allowing automatic restart of VMs when you have a hardware failure is the principle of VMware HA. As such, administrators do not need to worry about their VMs and applications because VMware HA can restart those VMs on remaining hosts within the cluster. A VMware cluster has to comprise at least two hosts, but the maximum limit is 64 hosts. vCenter Server itself can manage up to 2,000 hosts organized into clusters.