Change Active Directory Domain Services (ADDS) in the vSAN cluster
search cancel

Change Active Directory Domain Services (ADDS) in the vSAN cluster

book

Article ID: 396997

calendar_today

Updated On:

Products

VMware vSAN

Issue/Introduction

  • Administrators need to change the Fully Qualified Domain Name (FQDN) of the vCenter Server in an environment using vSAN clusters. There is a risk that this change could disrupt the vSAN unicastagent list, potentially impacting cluster communication and stability. Guidance is required to perform this operation safely, minimizing service disruption and ensuring data integrity.

Environment

VMware vSphere vSAN 7.x
VMware vSphere vSAN 8.x

Resolution

Note: Before going ahead with any changes in the environment please make sure to have healthy backups.

  • Set up the new Active Directory Domain Services (ADDS) in the environment with the help of your networking team.

  • To avoid the vSAN unicastagent list being impacted by the change, the recommendation is to deactivate cluster member updates from the vCenter Server by setting the parameter "IgnoreClusterMemberListUpdates" to 1 in all vSAN nodes before the FQDN change.

  • A value of 1 for "IgnoreClusterMemberListUpdates" tells the host to ignore any updates coming from vCenter regarding the unicastagent list. While a value of 0, which is the default setting, tells the host to accept the changes coming from vCenter.

    • Set the parameter to 1 by running the following command in each vSAN node:

# esxcfg-advcfg -s 1 /VSAN/IgnoreClusterMemberListUpdates

    • While the parameter "IgnoreClusterMemberListUpdates" is configured to 1, Skyline Health will report errors. Please ignore them until the whole procedure is over and this is configured to 0 again in all hosts.

    • Although vSAN can run independently from vCenter, we do recommend having valid backups for the VMs in the vSAN clusters before performing the task.

    • For more information on how to change vCenter Server's FQDN, you may refer to Changing your vCenter Server’s FQDN.

  • Then follow Changing your vCenter Server's FQDN - VMware vSphere Blog, to change the FQDN for vCenter.

  • Then follow How to Change the vSAN ESXi Host Name , to change the hostname.

  • Set the parameter "IgnoreClusterMemberListUpdates" to 0 again in all vSAN nodes to enable cluster member updates from vCenter again, by running the following command in each node:

    # esxcfg-advcfg -s 0 /VSAN/IgnoreClusterMemberListUpdates

     

Powered by Wolken Software