With NSX Federation, you can federate the management domain NSX-T Data Center or a VI workload domain NSX-T Data Center across VMware Cloud Foundation (VCF) instances.

See VMware Configuration Maximums for your version of NSX-T Data Center for information about the maximum number of supported federated NSX Managers and other NSX federation maximums.
Note: VI workload domains that share an NSX Manager are considered a single location.

Some tasks described in this section are to be performed on the first NSX Data Center instance while others need to be performed on each NSX Data Center instance that is being federated. See the table below for more information.

NSX Data Center Intance Tasks to be Performed
First Instance
  1. Create a Global Manager Cluster in VMware Cloud Foundation
  2. Replacing Global Manager Cluster Certificates in VMware Cloud Foundation

    You can skip this step if you are using self-signed cerificates.

  3. Prepare Local Manager for NSX Federation in VMware Cloud Foundation
  4. Enable NSX Federation in VMware Cloud Foundation

  5. Stretching Segments between VMware Cloud Foundation Instances:

    1. Create and Configure Cross-Instance Tier-1 Gateway

    2. Connect Cross-Instance Segments to Cross-Instance Tier-1 Gateway

Enable high availability for NSX Federation Control Plane on one additional instance
  1. Create a Global Manager Cluster in VMware Cloud Foundation
  2. Replacing Global Manager Cluster Certificates in VMware Cloud Foundation

    You can skip this step if you are using self-signed cerificates.

  3. Set Standby Global Manager

Each additional instance
  1. Prepare Local Manager for NSX Federation in VMware Cloud Foundation
  2. Add Location to Global Manager

  3. Stretching Segments between VMware Cloud Foundation Instances:

    1. Delete Existing Tier-0 Gateways in Additional Instances
    2. Connect Additional VMware Cloud Foundation Instances to Cross-Instance Tier-0 Gateway
    3. Connect Local Tier-1 Gateway to Cross-Instance Tier-0 Gateway
    4. Add Additional Instance as Locations to the Cross-Instance Tier-1 Gateway