When you implement NSX-T Federation, all existing NSX-T Manager nodes become NSX-T Local Manager nodes. You must perform certain configurations before you can enable NSX-T Federation in Region A.
Procedure
Create an IP Pool for Remote Tunnel Endpoints in NSX-T Data Center for the Management Domain in Region B Configure Automatic Backups of the NSX-T Global Manager Cluster Configurations for the Management Domain in Region B Obtain the Certificate Thumbprint of the NSX-T Manager Cluster Virtual IP for the Management Domain in Region B Delete the Existing Cross-Region Segment from the NSX-T Manager for the Management Domain in Region B xreg-m01-seg02 cross-region segment to avoid conflicts in the NSX-T Data Center environment when you enable NSX-T Federation in Region B. The same segment is also configured in Region A and you later stretch that segment to Region B.Enable NSX-T Federation for the Management Domain in Region B Delete the Existing Tier-0 Gateway for the Management Domain in Region B Configure the Tier-0 Gateway to Provide Networking for the Management Domain in Region B Configure an Any IP Prefix in the Tier-0 Gateway for the Management Domain Any IP prefix on the Tier-0 Gateway to allow access to any network to perform route advertisement. Route maps use IP prefixes to prepend a path to one or more autonomous systems (AS-path prepend) for BGP neighbors and to configure local-reference on learned default-route for BGP neighbors.Create a Route Map for No Export Traffic in the Tier-0 Gateway for the Management Domain Configure Route Filters and Route Redistribution for BGP for the Management Domain Configure the Tier-1 Gateway for the Management Domain in Region B lax-m01-ec01-t1-gw01 Tier-1 gateway for the region-specific workloads in Region B to the Tier-O gateway in Region A.Add Region B as a Location in the Cross-Region Tier-1 Gateway for the Management Domain in Region A Prevent Password Lockout on the NSX-T Local Manager Nodes for the Management Domain in Region B
