Federation Disaster Recovery failover test shows traffic still routing to Active/Primary datacenter

Products

• VMware NSX

Issue/Introduction

• NSX Federation with two Local Manager instances, one being primary (Site-A) and the other being secondary (Site-B)

• Global NSX Segment connected to Global T1 in Active/Standby (A/S) connected to Global T0 in Active/Active (A/A)

• Global T0 location configuration is Site-A = Primary and Site-B = Primary

• Global T1 location configuration is Site-A = Primary and Site-B = Secondary

• After failover to Site-B, traffic is not egressing locally out of Site-B's Global T0 and dropping at the T1 uplink in NSX Traceflow:

Environment

VMware NSX

Cause

Global T1 location configuration needs to be manually changed from secondary to primary

Resolution

To Change Primary Location of Global T1:

1. Navigate to Global NSX Manager UI > Networking > Tier-1 Gateways

2. Edit the Tier-1 Gateway object in question

3. Change Site-B's location mode from secondary to primary

4. Confirm that you want to switch the primary location by clicking 'YES'

   • 

5. Save

Additional Information

NSX Federation Reference Design Guide:

NSX-T Multi-Location Design Guide (Federation + Multisite)