Reassigning primary clusters for VCF for Classic - Automated instances
You can reassign a primary cluster to another cluster in your VMware Cloud Foundation for Classic - Automated instance according to your business needs.
Reassigning primary clusters for instances that are deployed with VMware vSphere® 6 is not supported.
Before you reassign a primary cluster
Review the following information before you reassign your primary cluster:
- Ensure that VMware NSX® is upgraded to the most recent version (4.1.2 or later).
- You must migrate the management virtual machines (VMs), the NSX edge management VMs, and the Usage Meter VM (if you deployed VMware vCloud Usage Meter).
- Do not migrate all VMs at the same time, as this action might cause failures.
To migrate your VMs, complete the following procedures in VMware vSphere Web Client.
Procedure to migrate management VMs
-
In VMware vSphere Web Client, go to the Virtual Machines tab, select the VM that you want to migrate and click Actions > Migrate.
-
Under Select a migration type, choose Change both compute resource and storage.
-
Under Select a compute resource, choose a target cluster or host in the target cluster.
-
Under Select storage, choose the vSAN datastore name for the target cluster.
If the target cluster has a higher version for the virtual switch than of the current cluster, you receive an error. For more information, see Migrating a virtual machine between two different vDS versions.
-
Under Select networks, ensure that the dpg source networks are equivalent to their target cluster. Do not change the edge-teps, as added clusters cannot create their own networks. Also, the destination network that is marked as none is a known issue and can be ignored.
-
Under Select vMotion priority, choose a priority option.
-
Under Ready to complete, verify the information and click Finish to start the migration.
Procedure to migrate NSX edge management VMs
After you migrate the management VMs, complete the following steps in NSX Manager:
-
Click the System tab.
-
From the left navigation menu, click Fabric > Nodes.
-
On the Edge Transport Nodes tab, click Edit to change the vMotion nodes.
-
Update the IPv4 Pool value so that it targets the cluster TEP pool. The IPv4 Pool value must be in the format
<instance name>-<cluster name>-tep-pool
. -
Click Save.
In the Edge Transport Nodes table, wait until the edge node Configuration Status shows Mismatch. This action happens when NSX identifies that the VM changed its cluster and datastore. Because it might be triggered from the NSX refresh of vCenter Server resources, it takes some time before the inconsistency is identified.
-
Select the edge node that has the Mismatch configuration status.
-
In the Resolve Sync Errors window, select the vSphere/Edge Appliance source.
Do not select NSX, as the migration will be reverted.
-
Click Resolve.
-
Refresh the table.
The validated configuration status changes to Success.
Procedure to reassign primary clusters for Automated instances
-
In the VMware Solutions console, click Resources > VCF for Classic from the left navigation panel.
-
In the VMware Cloud Foundation for Classic table, click the instance that contains the primary cluster that you want to reassign.
-
Click the Infrastructure tab and click Reassign primary cluster on the upper right of the Clusters table.
-
On the Reassign primary cluster pane, the original primary cluster is preselected. Verify that both the new primary cluster and the original primary cluster show a status of Available.
-
Select the new cluster that you want to assign as the primary cluster. The list shows only the new clusters that meet the following conditions, which are required for a successful reassignment:
- Must have vSAN storage.
- Must be on the same VLANs as the original primary cluster.
- Must have the same version of vSphere and the same networking type as the original primary cluster.
-
Click Reassign.
The reassignment of the new primary cluster can take up to one hour.
Results after you reassign the primary cluster
The status of the original and new primary clusters changes from Available to Modifying. After the reassignment is complete, the primary tag is shown on the new primary cluster and the status of both clusters changes to Available.