Lab B2: Migrate NSX Load Balancer to Avi for a VCF Workload Domain

VCF 9.0Intermediatespecialist⏱ 75 min

Objectives

Replace NSX-T native LB with Avi in an existing VCF 5.2 environment as the modernization path.

Prerequisites

VCF lab environment deployed and operational

Lab Environment

Standard VCF lab environment for Avi Load Balancer 30.x Specialist

Tasks

Task 1 Lab B2: Migrate NSX Load Balancer to Avi for VCF 5.2 Workload Domain

Replace NSX-T native LB with Avi in an existing VCF 5.2 environment as the modernization path.

Step 1

Inventory NSX-T LB VS, pools, persistence profiles in source WLD.

Step 2

Create equivalent Avi VS with one-to-one config mapping.

Step 3

Cut-over DNS to Avi VIPs for one test VS; monitor traffic.

Step 4

Roll the remaining VSes one by one with traffic mirroring.

Step 5

Decommission NSX-T LB and document reclaimed resources.

Validation Gate

Check: Verify lab completion

Expected: Lab exercise completed successfully

Common Errors

NSX ALB to Avi migration losing existing Virtual Service configurations

Fix: NSX LB configuration doesn't map 1:1 to Avi objects. NSX LB monitors, persistence profiles, and pool configurations must be manually recreated in Avi. Document all existing NSX LB settings before migration. Compare post-migration Avi config against the documented NSX LB config.

DNS records not updated to point to new Avi VIP after migration

Fix: After migrating from NSX LB to Avi, the VIP address changes (unless you configure Avi to use the same IP). Update DNS records to point to the new Avi VIP. Use Avi DNS VS for automatic DNS management if managing DNS through Avi.

Health monitors not validated after migration

Fix: NSX LB health monitors may use different check parameters than Avi defaults. After migration, verify health monitors in Avi: correct protocol, correct URL path for HTTP monitors, correct response code expectations. A misconfigured health monitor marks all pool members as down.

Final Validation

Lab completed successfully

✓ All steps completed → No errors observed

Cleanup / Restore

• Revert to snapshot if needed

Design Reflection (VCDX)

LB migration demonstrates operational planning skills. VCDX designs transitioning from NSX LB to Avi should include migration planning, rollback strategy, and DNS cutover procedure.

⚠ Known Pitfalls (from Community KB)

Assuming NSX LB config maps directly to Avi — it doesn't. Manual recreation is required.

Not updating DNS after migration — clients still reach the old NSX LB VIP.

Mark complete