You can create an NSX-T endpoint and associate it to an existing vSphere endpoint in vRealize Automation.
vRealize Automation uses basic authentication to connect with the NSX-T endpoint.
- vRealize Automation can point to one of the NSX managers. With this option, one NSX manager receives the API calls from vRealize Automation.
- vRealize Automation can point to the Virtual IP of the cluster. With this option, one NSX manager assumes control of the VIP. That 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, 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.
You can associate an NSX-T endpoint with one or more vSphere endpoints.
- One vSphere endpoint associated with a single NSX for vSphere endpoint.
- One vSphere endpoint associated with multiple NSX-T endpoints.
- One NSX-T endpoint associated with multiple vSphere endpoints.
- One NSX for vSphere endpoint associated with a single vSphere endpoint.
- One vSphere endpoint associated with one NSX for vSphere endpoint and with one NSX-T endpoint.
When a vSphere endpoint is associated to both an NSX for vSphere endpoint and an NSX-T endpoint, the cluster is managed by NSX for vSphere or by NSX-T. The NSX manager is determined by vRealize Automation when endpoints are data-collected and relationship is established. You can see the type of NSX platform that manages a specific cluster by inspecting the NSX type column on the Compute Resources page.
When you deploy a blueprint that contains an NSX-T endpoint, the deployment assigns a tag to NSX-T components in the deployment. The tag name and the deployment name match.
For information about validating the endpoint connection and certificate trust, see Considerations When Using Test Connection.
Log in to vRealize Automation as an IaaS administrator.
You must install a vSphere proxy agent to manage your vSphere endpoint, and you must use the same exact name for your endpoint and agent. For information about installing the agent, see Installing and Configuring the Proxy Agent for vSphere.
- Configure your NSX-T network settings. See Configuring Network and Security Component Settings in vRealize Automation.
- Create a vSphere Endpoint in vRealize Automation and Associate to NSX.
In preparation for using NSX network, security, and load balancing capabilities in vRealize Automation, when using NSX Manager credentials you must use the NSX Manager administrator account.
- Select .
- Select .
- Enter a name in the Name text box.
- (Optional) Enter a description in the Description text box.
- Enter the URL for the NSX-T endpoint manager instance or VIP (see above) in the Address text box.
The URL must be of the type: https://hostname or https://IP_address.For example, https://abx-nsxt3-manager.local.
- Enter the NSX administrator-level user name and password that are stored for the NSX-T endpoint.
- (Optional) Click Properties and add supplied custom properties, property groups, or your own property definitions for the endpoint.
- To associate the NSX-T network and security settings to an existing vSphere endpoint, click Associations and select an existing vSphere endpoint.
You must create the vSphere endpoint before you can create the association.
A vSphere endpoint can be associated with only one type of network and security platform - either NSX for vSphere or NSX-T.
You can associate an NSX-T endpoint to more than one vSphere endpoint. One NSX-T instance can manage multiple ESX clusters on different vCenters.
When the association is finished, the Description column on the page indicates the association type of NSX-T.
- (Optional) To validate the credentials, host endpoint address, and certificate trust, click Test Connection. The action also checks that the manager service and agent are running so that endpoint can be data-collected. The OK action tests for these same conditions.
The Test Connection action returns information about any of the following conditions:
- Certificate error
If the certificate is not found, trusted, or has expired, you are prompted to accept a certificate thumb print. If you do not accept the thumb print, you can still save the endpoint but machine provisioning might fail.
- Agent error
The associated vSphere agent is not found. The agent must be running for the test to succeed.
- Host error
The specified endpoint address is not reachable or the associated manager service is not running. The manager service must be running for the test to succeed.
- Credentials error
The specified user name and password combination is invalid for the endpoint at the specified address.
The test action could not complete in the allowed two-minute time period.
If the Test Connection action fails, you can still save the endpoint but machine provisioning might fail.
If there is a trusted certificate issue, for example the certificate has expired, you are prompted to accept a certificate thumb print.
- Certificate error
- To save the endpoint, click OK.
The OK action tests for the same conditions as the Test Connection action. If it finds any of the preceding conditions, it returns a message. If it can save, it leaves the error on the screen for you to review.
vRealize Automation collects data from your endpoint and discovers your compute resources.
For information about running data collection for existing endpoints after initial data collection, see Viewing Compute Resources and Running Data Collection.
What to do next
Add the compute resources from your endpoint to a fabric group. See Create a Fabric Group.