You can create an NSX-T endpoint and associate it to an existing vSphere endpoint.

When you deploy a blueprint that contains an NSX-T endpoint, the deployment assigns a tag to all the NSX-T components in the deployment, including NSX-T network, security, and load balancer components and the NSX-T endpoint's associated vSphere machine component. The tag is unique to the deployment and is associated with the components in the initial deployment and any subsequent actions that you later make in the deployment. The name of the tag is the same as the name of the deployment.

An NSX-T endpoint can be associated with multiple vSphere endpoints in vRealize Automation. However, a vSphere endpoint can only be associated with one NSX, either NSX for vSphere or NSX-T, endpoint.

For information about validating the NSX connection and certificate trust when you create the endpoint, see Considerations When Using Test Connection.

Prerequisites

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.

vRealize Automation uses basic authentication to connect with the NSX-T endpoint.

Procedure

  1. Select Infrastructure > Endpoints > Endpoints.
  2. Select New > Network and Security > NSX-T.
  3. Enter a name in the Name text box.
  4. (Optional) Enter a description in the Description text box.
  5. Enter the URL for the NSX-T instance 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.

  6. Enter the NSX administrator-level user name and password that are stored for the NSX-T endpoint.
  7. (Optional) Click Properties and add supplied custom properties, property groups, or your own property definitions for the endpoint.
  8. 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. This allows one NSX-T instance to manage multiple ESX clusters on difference vCenters.

    When the association is finished, the Description column on the page indicates the association type of NSX-T.

  9. (Optional) Click Test Connection to validate the credentials, host endpoint address, and certificate trust. 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 thumbprint. If you do not accept the thumbprint, 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.

    • Timeout

      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 thumbprint.

  10. Click OK to save the endpoint.

    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.

Results

vRealize Automation collects data from your endpoint and discovers your compute resources.

What to do next

Add the compute resources from your endpoint to a fabric group. See Create a Fabric Group.