Renaming a vSAN ESXi Host FQDN and Re-adding to vCenter Server - VMware vSAN
search cancel

Renaming a vSAN ESXi Host FQDN and Re-adding to vCenter Server - VMware vSAN

book

Article ID: 327019

calendar_today

Updated On:

Products

VMware vCenter Server VMware vSAN VMware vSphere ESXi

Issue/Introduction

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

Environment

  • VMware vSAN
  • VMware vSphere ESXi
  • VMware vCenter Server

Resolution

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.

  1. Considerations:

  2. Assumptions:

    • This guide assumes that there are no other maintenance or network changes being conducted at the same time.
    • This guide assumes that the user has knowledge of third-party products and other software that may be impacted by this hostname change. The implementor is expected to anticipate and plan for taking the appropriate actions to maximize business continuity.
    Attention: If any of the steps fail, STOP and contact Broadcom support for assistance.
  3. Procedure:

    Complete all of the following steps for one host at a time:

    1. Place the host in Maintenance Mode with Ensure Accessibility (or Full Data Migration if appropriate).
    2. Disconnect the ESXi host from vCenter. Right click the host and select Disconnect.
    3. Remove the ESXi host from the vCenter inventory. Right click the host and select Remove From Inventory.
    4. Change the FQDN name of the host using either the DCUI, iDRAC, iLO, or from a direct web client with command, using the command:
      # esxcli system hostname set --fqdn=<hostname.fulldomain>
    5. Make sure to update the related DNS records on the DNS servers.
    6. Re-add, and if neccessary reconnect the host back to vCenter.
    7. Move the host out of Maintenance Mode.
    8. If the above steps are not completed in less than 1 hour (60 minutes), a resync might be triggered. Allow the resync to complete before continuing with the next host.
    9. Validate cluster health (Cluster → Monitor → Skyline Health → Retest) to ensure there are no partition alerts.

    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:

    1. Take screenshots of the current DVS configuration for the host(s)
    2. Upon re-adding the host(s) to the vCenter the following error will be shown for the DVS in vSphere Client:
      The vSphere Distributed Switch configuration on some hosts differed from that of the vCenter Server.
      Example:
    3. To fix this, use the screenshots taken of the host(s) DVS configuration earlier and re-add the host(s) to the DVS with the exact same config to avoid any network outages.
    Note: When running into any issues while reconfiguring the DVS, contact Broadcom support by opening a networking case for assistance.
  4. Optional secondary procedure:

    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:

      1. Navigate to Hosts and Clusters and select a host.
      2. Right-click the host and select Connection → Connect in the pop-up menu.
      3. Follow the steps described in Renew or Refresh ESXi Certificates


    • Option 2 - By using the command line interface (CLI) of the ESXi host:

      1. Connect to the host via SSH.
      2. Login using the root account.
      3. Run the following command to generate a new self-signed certificate:
        # /sbin/generate-certificates
      4. Restart the ESXi management agents:
        # /etc/init.d/hostd restart && /etc/init.d/vpxa restart

      See Regenerating Self-Signed Certificates on Standalone ESXi Hosts for more information.