To register or add a new vCenter Server connection, do the following steps:
Prerequisites
The VLA Service connects to one or more vCenter Servers to gather inventory and metrics. The VLA Service can hence connect to one or more vCenter Servers. You can use commands to register (or add), modify, remove, test, and list vCenter Server connections. You must add at least one vCenter Server connection. When you add a vCenter Server connection, you associate a VMware vRealize Orchestrator with the vCenter Server that you are adding. This lets the LaMa service know which VMware vRealize Orchestrator to use to process actions on the vCenter Server objects.
Procedure
Go to the VLA console window.
Execute the sudo command to get administrative access and enter the console user password that you provided when deploying the VLA (Step 9 of Deploy VLA)
sudo -s
Add an entry to the credentials database for the vCenter Server. To do this, enter the following command at the prompt:
vla_credentials –a –s vcenter –n <vcenter-fqdn> -u <vcenter-user> -A <vco-id>
where:
<vcenter-fqdn> is the fully-qualified domain name of the vCenter Server you wish to connect to the VLA
<vco-id> is the ID for the VMware vRealize Orchestrator server you added in section (Connecting to VMware vRealize Orchestrator). If you don't know the ID of the VMware vRealize Orchestrator Server, use the command vla_credentials -l, which returns output similar to the following:
For example:
# vla_credentials -a -s vco -n sapi-vco.example.com -u [email protected] -A vco0
when prompted, enter the password for the user you specified.
Look for a success message. If a failure message mentions a certificate checker error, you can override the certificate checker (See Certificate check completes with errors)
Refresh the browser window and look for the server in the VLA Server Dashboard. You should see an entry to the vCenter Server that you connected to in step 3 above.
You can also type the following command at the prompt on the VLA console.
vla_credentials -l
For each additional vCenter Server repeat steps 3 through 6 in this section.