You can create endpoints that allow vRealize Automation to communicate with the vSphere environment and discover compute resources, collect data, and provision machines.
About this task
If your vSphere environment is integrated with NSX, see Create a vSphere Endpoint with Network and Security Integration.
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 exactly the same name for your endpoint and agent. For information about installing the agent, see Installing and Configuring the Proxy Agent for vSphere.
If your system administrator did not configure the proxy to use integrated credentials, you must store administrator-level credentials for your endpoint. See Store User Credentials.
- Select .
- Select .
- Enter a name in the Name text box.
This must match the endpoint name provided to the vSphere proxy agent during installation or 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 the administrative-level user name and password that you stored for this endpoint.
If your system administrator configured the vSphere proxy agent to use integrated credentials, you can select the Integrated credentials.
- Do not select Specify manager for network and security platform unless your configuration supports NSX.
This setting is for implementations that use NSX and requires additional configuration.
- (Optional) Click Properties and add endpoint properties that are meaningful to the specific IPAM solution provider.
Each IPAM solution provider, for example Infoblox and Bluecat, use unique extensible attributes that you can emulate by using vRealize Automation custom properties. For example, Infoblox uses extensible attributes to differentiate primary and secondary endpoints.
- Click OK.
vRealize Automation collects data from your endpoint and discovers your compute resources.
Do not rename vSphere data centers after the initial data collection or provisioning might fail.
What to do next
Add the compute resources from your endpoint to a fabric group. See Create a Fabric Group.