Manual NSX Edge Migration for Federated Environments Managed by VMware Cloud Foundation (VCF)

Products

• VMware NSX
• VCF Operations

Issue/Introduction

Scenarios where the information within this KB may be useful:

• You need to diversify your storage so that if one storage array goes down, you don't lose all of your Edge nodes with it.
• You are adding storage and not changing the primary data store of the cluster.

The procedure found within the Resolution section applies exclusively to NSX Edge nodes within a VCF-managed Federated environment. This procedure is NOT valid for standalone NSX-T Federation deployments. Do not attempt this procedure on environments outside of VCF orchestration.

Environment

Vmware Cloud Foundation

NSX Federated

Cause

The standard Expand/Shrink methodologies for migrating an Edge Cluster cannot be used on a Federated Environment, as the Edge Cluster cannot be "shrunk".

Resolution

1. Place the target Edge node into NSX Maintenance Mode to ensure non-disruptive migration.
2. Perform a standard vSphere Storage vMotion of the Edge VM to the new storage platform.
3. Once migration is complete, exit NSX Maintenance Mode.
4. If a "Configuration Mismatch" alarm appears for the Edge node in the NSX UI, navigate to the alarm, select "vSphere/Edge Appliance," and click "Resolve."
5. If moving multiple Edge nodes, wait for the first one to stabilize before moving onto the next one.

Additional Information

• If you are changing the primary data store please open a new case with Broadcom. See: Creating and managing Broadcom support cases
• See: How to migrate a virtual machine's configuration files and disks to different datastores with Storage vMotion.