You can create vSphere endpoints in vRealize Automation that communicate with vCenter to discover compute resources, collect data, and provision machines. You can also associate NSX settings to the vSphere endpoint by associating to an NSX for vSphere endpoint, one or more NSX-T endpoints, or both NSX endpoint types.
- An IaaS administrator can associate a vSphere endpoint with both an NSX for vSphere endpoint and an NSX-T endpoint.
- A fabric administrator can create an NSX for vSphere or NSX-T reservation depending on the compute resource.
- A blueprint architect can author blueprints that are either NSX for vSphere specific or NSX-T specific. Both types of blueprints can be deployed in the same vCenter environment.
- 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.
For information about creating NSX endpoints that are associated with a vSphere endpoint, see Create an NSX for vSphere Endpoint and Associate to a vSphere Endpoint in vRealize Automation or Create an NSX-T Endpoint and Associate to a vSphere Endpoint in vRealize Automation.
For information about validating the endpoint connection and certificate trust, see Considerations When Using Test Connection.
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.
Log in to vRealize Automation as an IaaS administrator.
You must install a vSphere proxy agent to manage your vSphere endpoint. The agent name and endpoint name must match. For information about installing the agent, see Installing and Configuring the Proxy Agent for vSphere.
- If you plan to use a vSphere endpoint to deploy VMs from OVF templates, verify that your credentials include the vSphere privilege VApp.Import in the vCenter Server that is associated with the endpoint.
The VApp.Import privilege allows you to deploy a vSphere machine by using settings imported from an OVF. Details about this vSphere privilege are available in the vSphere SDK documentation.
If the OVF is hosted on a Web site, see Create a Proxy Endpoint for OVF Host Web Site.
- Configure the vSphere Agent.
- To configure additional NSX network and security settings for the vSphere endpoint, create an NSX for vSphere or NSX-T endpoint. You can associate to your NSX endpoint when you create or edit the vSphere endpoint.
- Select .
- Select .
- Enter a name in the Name text box.
The name must match the endpoint name provided to the vSphere proxy agent during installation. If the name does not match, data collection fails.
- (Optional) Enter a description in the Description text box.
- Enter the URL for the vCenter Server instance in the Address text box.
The URL must be of the type: https://hostname/sdk or https://IP_address/sdk.For example, https://vsphereA/sdk.
- Enter your vSphere administrator-level user name and password or use your vSphere integrated credentials.
Provide credentials that have permission to modify custom attributes.
The user name format is domain\username.
To use the vSphere proxy agent's service account to connect to the vCenter Server, select Use Integrated Credentials.
If you use your vSphere integrated credentials, you do not need to enter a user name and password.
- (Optional) Click Properties and add supplied custom properties, property groups, or your own property definitions for the endpoint.
- (Optional) To configure your NSX network and security settings for the endpoint, click Associations and associate to an existing NSX for vSphere or NSX-T endpoint.
You must have at least one NSX endpoint to create an association.
- (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 more information, 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.