How to migrate an NSX Native Load Balancer to a new Edge Cluster
search cancel

How to migrate an NSX Native Load Balancer to a new Edge Cluster

book

Article ID: 432489

calendar_today

Updated On:

Products

VMware NSX VMware NSX Data Center for vSphere

Issue/Introduction

VMware NSX (NSX-T). Administrators may need to migrate an actively running NSX Native Load Balancer to a new Edge Cluster. This is typically required for capacity management, hardware lifecycle replacement, or isolating load balancing services to dedicated routing topologies.

Environment

  • VMware NSX-T Data Center
  • VMware NSX 4.x

Cause

Administrative configuration change to reallocate Edge node resources or adjust network routing topologies.

Resolution

There are two supported administrative workflows to migrate the load balancer to a new Edge Cluster.

Warning: Both methods will cause a temporary datapath disruption. The centralized load balancer service executes on the Tier-1 Service Router (SR). Migrating the service forces the NSX Manager to tear down the existing SR on the original Edge node and instantiate a new SR on the target Edge node. This process drops active stateful connections and clears persistence tables. Perform this activity during an approved maintenance window.

Method 1: Modify the Edge Cluster Assignment on the Existing Tier-1 Gateway

  1. Log in to the NSX Manager UI.

  2. Navigate to Networking > Tier-1 Gateways.

  3. Locate the Tier-1 Gateway hosting the load balancer service, click the vertical ellipsis, and select Edit.

  4. In the Edge Cluster drop-down menu, select the new target Edge Cluster.

  5. Ensure the Edge Pool Allocation Size remains correctly sized for your deployed load balancer (e.g., LB Small, LB Medium).

  6. Click Save to apply the configuration and initiate the migration.

Method 2: Migrate the Load Balancer to a New Tier-1 Gateway

  1. Navigate to Networking > Tier-1 Gateways and click Add Tier-1 Gateway.

  2. Configure a new gateway name, link it to the same upstream Tier-0 Gateway as the original, and select the new target Edge Cluster.

  3. Set the Edge Pool Allocation Size to match your existing load balancer requirements.

  4. Expand Route Advertisement and enable All LB VIP Routes and All LB SNAT IP Routes (or mirror the specific advertisement rules of the original Tier-1).

  5. Click Save.

  6. Navigate to Networking > Network Services > Load Balancing > Load Balancers.

  7. Locate the target load balancer, click the vertical ellipsis, and select Edit.

  8. Modify the Attachment drop-down to select the newly created Tier-1 Gateway.

  9. Click Save to initiate the migration.

 

Additional Information

Powered by Wolken Software