7.3

Table Of Contents
Cause
The UPN entered must adhere to a yourname.admin@yourdomain format, for example if you log in using
jsmith.admin@sqa.local as the user name but the UPN in the Active Directory is only set as jsmith.admin,
the login fails.
Solution
To correct the problem change the userPrincipalName value to include the needed @yourdomain
content and retry login. In this example the UPN name should be jsmith.admin@sqa.local. This
information is provided in the log file in the log/vcac folder.
Log In Fails with High Availability
When you have more than one vRealize Automation appliance, the appliances must be able to identify
each other by short hostname. Otherwise, you cannot log in.
Problem
You configure vRealize Automation for high availability by installing an additional vRealize Automation
appliance. When you try to log in to vRealize Automation, a message about an invalid license appears.
The message is incorrect though, because you determined that your license is valid.
Cause
The vRealize Automation appliance nodes do not correctly form a high availability cluster until they can
resolve the short host names of the nodes in the cluster.
Solution
To allow a cluster of high availability vRealize Automation appliances to resolve short host names, take
any of the following approaches. You must modify all appliances in the cluster.
Procedure
n
Edit or create a search line in /etc/resolv.conf. The line should contain domains that hold
vRealize Automation appliances. Separate multiple domains with spaces. For example:
search sales.mycompany.com support.mycompany.com
n
Edit or create domain lines in /etc/resolv.conf. Each line should contain a domain that holds
vRealize Automation appliances. For example:
domain support.mycompany.com
n
Add lines to the /etc/hosts file so that each vRealize Automation appliance short name is
mapped to its fully qualified domain name. For example:
node1 node1.support.mycompany.com
node2 node2.support.mycompany.com
Installing vRealize Automation
VMware, Inc. 173