7.1

Table 3‑3. CSV File Fields and Their Order for Importing Endpoints (Continued)
Field Description
Credentials
(Required) Name you gave the user credentials when you stored them in
vRealize Automation.
Name
(Required) Provide a name for the endpoint. For OpenStack, the address is used as the
default name.
Description
(Optional) Provide a description for the endpoint.
OpenstackProject
(Required for OpenStack only) Provide the project name for the endpoint.
Troubleshooting Attached vSphere Endpoint Cannot be Found
When data collection fails for a vSphere endpoint, it is often due to a mismatch between the proxy name and
the endpoint name.
Problem
Data collection fails for a vSphere endpoint. The log messages return an error similar to the following:
This exception was caught: The attached endpoint
'vCenter' cannot be found.
Cause
The endpoint name you congure in vRealize Automation must match the endpoint name provided to the
vSphere proxy agent during installation. Data collection fails for a vSphere endpoint if there is a mismatch
between the endpoint name and the proxy agent name. Until an endpoint with a matching name is
congured, the log messages return an error similar to the following:
This exception was caught: The attached endpoint
'expected endpoint name' cannot be found.
Solution
1 Select Infrastructure > Monitoring > Log.
2 Look for an Aached Endpoint Cannot be Found error message.
For example,
This exception was caught: The attached endpoint
'expected endpoint name' cannot be found.
3 Edit your vSphere endpoint to match the expected endpoint name shown in the log message.
a Select Infrastructure > Endpoints > Endpoints.
b Click the name of the endpoint to edit.
c Enter the expected endpoint name in the Name text box.
d Click OK.
The proxy agent can commute with the endpoint and data collection is successful.
Configuring vRealize Automation
174 VMware, Inc.