This article explains the process to change the name of the vSAN ESXi host.
VCF Convergence to VCF 9.x pre-checks can fail with "ESXi FQDN mismatch," if the vSAN ESX hosts were added to vCenter inventory with an IP address instead of FQDN
Attention: Before applying the steps outlined in this article, make sure to have full and current backups of ALL critical data before proceeding
Modifying the Fully Qualified Domain Name (FQDN) or hostname of an ESXi host participating in a VMware vSAN cluster requires removing and re-adding the host to vCenter Server. When ESXi hosts utilize a vSphere Distributed Virtual Switch (DVS), additional precautions are required to preserve network connectivity and prevent cluster configuration discrepancies.
Notes:
- If this is a VxRail cluster engage Dell VxRail support for assistance with this.
- If using VCF changing the hostname once the cluster has been deployed is not supported so do not follow these steps for changing the hostname.
- For VCF Convergence Preparation, renaming the ESX host(s) is required to satisfy the installer's FQDN validation before the VCF deployment is finished.
This procedure details the steps to safely update the host FQDN via command line interface (CLI) or remote management console, adjust the DNS infrastructure, and restore DVS alignment without causing network downtime or unexpected vSAN data resynchronization.
Attention: If any of the steps fail, STOP and contact Broadcom support for assistance.
Complete all of the following steps for one host at a time:
# esxcli system hostname set --fqdn=<hostname.fulldomain>
This process cleanly reintroduces the host to vCenter and updates the vCenter database.
Additional steps will be required, if a Distributed Virtual Switch is used, but for other reasons the host was neither migrated to a Standard Switch nor to an ephemeral port group on the Distributed Virtual Switch prior to removing/readding the host to the vCenter inventory:
The vSphere Distributed Switch configuration on some hosts differed from that of the vCenter Server.Example:
Note: When running into any issues while reconfiguring the DVS, contact Broadcom support by opening a networking case for assistance.
If required, regenerate the host certificates once the hostname persists correctly across reboots, regenerate the internal certificates to match the FQDN, using either of the following options:
Option 1 - By using the vSphere Client UI:
Option 2 - By using the command line interface (CLI) of the ESXi host:
root account.# /sbin/generate-certificates
# /etc/init.d/hostd restart && /etc/init.d/vpxa restart
See Regenerating Self-Signed Certificates on Standalone ESXi Hosts for more information.