You can create an NSX endpoint and associate its NSX settings to an existing vSphere endpoint.
About this task
If you upgraded or migrated a vSphere endpoint that was using an NSX manager, a new NSX endpoint is created that contains an association between the source vSphere endpoint and a new NSX endpoint.
For information about validating the NSX connection and certificate trust, see Considerations When Using Test Connection.
For related information about creating an NSX endpoint, see public articles such as this vmwarelab blog post.
Log in to the vRealize Automation console 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 network settings. See Configuring Network and Security Component Settings.
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 instance in the Address text box.
The URL must be of the type: https://hostname or https://IP_address.
For example, https://nsx-manager.local.
- Enter the NSX administrator-level user name and password that are stored for the NSX endpoint.
- (Optional) Click Properties and add supplied custom properties, property groups, or your own property definitions for the endpoint.
- To associate the NSX 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.
You can only associate an NSX endpoint to one vSphere endpoint. This association constraint means that you cannot provision a universal on-demand network and attach it to vSphere machines that are provisioned on different vCenters.
- (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:
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.
The associated vSphere agent is not found. The agent must be running for the test to succeed.
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.
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 thumbprint.
- 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.
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.