NSX environments containing more than one vCenter Server system can be managed centrally.

There are many reasons multiple vCenter Server systems may be required, for example:

  • To overcome scale limits of vCenter Server

  • To accommodate products that require dedicated or multiple vCenter Server systems, such as Horizon View or Site Recovery Manager

  • To separate environments, for example by business unit, tenant, organization, or environment type

In NSX 6.1 and earlier, if multiple vCenter NSX environments are deployed, they must be managed separately. In NSX 6.2 and later you can create universal objects on the primary NSX Manager, which are synchronized across all vCenter Servers systems in the environment.

Cross-vCenter NSX includes these features:

  • Increased span of NSX logical networks. The same logical networks are available across the vCenter NSX environment, so it's possible for VMs on any cluster on any vCenter Server system to be connected to the same logical network.

  • Centralized security policy management. Firewall rules are managed from one centralized location, and apply to the VM regardless of location or vCenter Server system.

  • Support of new mobility boundaries in vSphere 6, including cross vCenter and long distance vMotion across logical switches.

  • Enhanced support for multi-site environments, from metro distance to 150ms RTT. This includes both active-active and active-passive datacenters.

Cross-vCenter NSX environments have many benefits:

  • Centralized management of universal objects, reducing administration effort.

  • Increased mobility of workloads - VMs can be vMotioned across vCenter Servers without having to reconfigure the VM or change firewall rules.

  • Enhanced NSX multi-site and disaster recovery capabilities.

Note:

Cross-vCenter NSX functionality is supported with vSphere 6.0 and later.