You can associate an NSX-T cloud account to one or more vCenter cloud accounts to support various deployment objectives.

You can associate the same existing NSX-T network to network profiles for different vCenters and provision a deployment in either vCenter based on constraints. Several examples are listed below:
  • Cloud templates that contain a single machine with multiple NICs that use the same network profile, where that network profile contains an NSX-T network that spans multiple vCenters.
  • Cloud templates that contain a machine on a private network that uses a network profile with subnet-based isolation and that uses an NSX-T existing network that spans multiple vCenters.
  • Cloud templates that contain a single machine on a private network that uses a network profile with security group-based isolation and that uses an NSX-T network that spans vCenters.
  • Cloud templates that contain a single machine on a routed network that uses a network profile that contains an NSX-T network that spans multiple vCenters.
  • Cloud templates that contain an on-demand load balancer that is defined in a network profile where the load balancer is applied to all the vCenter machines on the network.
  • Cloud templates that contain an on-demand network that is defined in a network profile where the on-demand network is used by all the vCenters that use the network profile.
  • Cloud templates that contain an on-demand security group that optionally contains firewall rules and where the security group is associated to all the vCenters on the network.

You can configure vRealize Automation Cloud internal or external IPAM on the NSX-T network and share the same IP address for machines that are provisioned in different vCenters.

If no network profile is defined in your system, you can provision a cloud template that contains multiple machines on different vCenters that share a single existing NSX-T network.