For network and security purposes, you can create an NSX-T cloud account and associate it with one or more vCenter cloud accounts.
An NSX-T cloud account can be associated to one or more vCenter cloud accounts. However, an NSX-V cloud account can only be associated to one vCenter cloud account.
The association between NSX-T and one or more vCenter cloud accounts must be configured outside of vRealize Automation, specifically in your NSX application. vRealize Automation doesn't create the association between NSX and vCenter. In vRealize Automation, you specify one or more configuration associations that already exists in NSX.
When you create an NSX-T cloud account in vRealize Automation, you specify a manager type and an NSX mode. These selections cannot be changed after you create the cloud account.
You can connect to an NSX-T Global Manager and configure an association between an NSX-T Global Manager and local managers in the context of the NSX-T federation.
For related information about NSX-T options and capabilities in general, see NSX-T Data Center product documentation.
- vRealize Automation can point to one of the NSX Managers. Using this option, one NSX Manager receives the API calls from vRealize Automation.
- vRealize Automation can point to the Virtual IP of the cluster. Using this option, one NSX Manager assumes control of the VIP. That NSX Manager receives the API calls from vRealize Automation. In case of failure, another node in the cluster assumes control of the VIP and receives the API calls from vRealize Automation.
For more information about VIP configuration for NSX, see Configure a Virtual IP (VIP) Address for a Cluster in the NSX-T Data Center Installation Guide at VMware NSX-T Data Center Documentation.
- vRealize Automation can point to a load balancer VIP to load-balance the calls to the three NSX Managers. Using this option, all three NSX Managers receive API calls from vRealize Automation.
You can configure the VIP on a third-party load balancer or on an NSX-T load balancer.
For large scale environments, consider using this option to split the vRealize Automation API calls among the three NSX Managers.
For a detailed look at using NSX-T 3.2 with vRealize Automation, see VMware blog post VMware Network Automation with NSX-T 3.2 and vRealize Automation.
Prerequisites
- Verify that you have the required administrator credentials and have enabled HTTPS access on port 443. See Credentials required for working with cloud accounts in vRealize Automation.
- Verify that you have the cloud administrator user role. See What are the vRealize Automation user roles.
- Verify that you have a vCenter cloud account to use with this NSX cloud account. See Create a vCenter cloud account in vRealize Automation.
- Verify that you have properly configured your ports and protocols to support the cloud account. See the Ports and Protocols for vRealize Automation topic in Installing vRealize Automation with vRealize Easy Installer and the Port Requirements topic in vRealize Automation Reference Architecture Guide in the vRealize Automation product documentation.
Procedure
What to do next
You can create or edit a vCenter cloud account to associate with this NSX cloud account. See Create a vCenter cloud account in vRealize Automation.
Create and configure one or more cloud zones for use with the data centers that are used by this cloud account. See Learn more about Cloud Assembly cloud zones.
Configure infrastructure resources for this cloud account. See Building your Cloud Assembly resource infrastructure.
For samples of using NSX-T options in vRealize Automation cloud templates, see Networks, security resources, and load balancers in vRealize Automation.