Troubleshooting vMA

You can find troubleshooting information for all VMware products in VMware Knowledge Base articles and information about vMA known issues in the release notes. Troubleshooting vMA explains a few commonly encountered issues that are easily resolved.

Troubleshooting vMA 

Issue	Resolution
You can deploy vMA but when you start up the virtual machine, an error occurs.	Check whether your setup meets the hardware and software requirements listed in Hardware Requirements.
You add a server but the vSphere CLI command or Perl script still prompts for authentication.	Run viftarget for the target server.
You have added multiple servers. You do not know where vMA runs vSphere CLI commands if you do not specify --server.	After a call to vifptarget, your prompt changes to include the current target.
You want to enable DNS resolution in vMA.	You can configure the DNS resolution name server for vMA by updating the /etc/resolv.conf file. Add the following line for each DNS server in your network: nameserver <dns server ip address> Type man resolv.conf for details on that file. If vMA is set up for DHCP, and the network is restarted, changes you made to /etc/resolv.conf are lost.
Problems while adding Active Directory target or configuring vMA for Active Directory.	If you are unable to authenticate from vMA or cannot add vMA to the domain controller, check the following: ■ Your DNS server setup in vMA resolves the IP address or host name of the vCenter server to an FQDN and the FQDN contains the domain name to which vMA is added. ■ The vifp listserver command shows the name of vCenter as the FQDN that contains the domain name to which vMA is added as the suffix. ■ The date and time settings on vMA, the domain controller and vCenter Server are identical. Check the time zone as well. The time may not exactly be the same but may vary by an hour. However, a large skew in the time may cause authentication problems.

This release of vMA provides the vma-support script that enables you to collect various system configuration information and other logs. You can run this script by issuing the following command:

> sudo vma-support

The script generates the information and log bundle and appends it to the vmware.log file on the ESXi host on which vMA is deployed.