vSphere Management Assistant 5.1 Release Notes
vSphere Management Assistant| 10 September 2012 | Build 782391
Last Document Update: 10 September 2012
The release notes covers the following topics:
Note: The topics in which this documentation uses the product name "ESXi" are applicable to all supported releases of ESX and ESXi.
vMA is a Linux-based virtual machine that is pre-installed with a command-line interface and select third-party agents needed to manage your vSphere infrastructure. Administrators and developers can use vMA to run scripts and agents to manage vSphere 5.1, vSphere 5.0 and later, and vSphere 4.1 and later systems. vMA includes the vSphere SDK for Perl and the vSphere Command-Line Interface (vSphere CLI). vMA also includes an authentication component named vi-fastpass. vi-fastpass allows direct connection to established target servers without user intervention.
For information about vSphere CLI, refer to the vSphere Command-Line Interface Documentation.
Whats New in vMA 5.1?
vMA 5.1 includes the following changes and enhancements:
- VAMI tool is upgraded to version 2.5.
- The vMA password policy is updated. The password must now contain at least nine characters.
- The network configuration during the first-boot is enhanced.
Hardware and Software Requirements
To set up vMA, you need the hardware listed in the following table.
||Because vMA runs a 64-bit operating system, the ESXi host on which vMA is to be deployed must support 64-bit virtual machines.
AMD Opteron, Rev E or later. AMD-V hardware virtualization is not required.
Intel processors with EM64T support with VT enabled.
|Note: Opteron 64-bit processors earlier than rev E and Intel processors that have EM64T support but not VT support enabled, do not support a 64-bit guest operating system. For detailed hardware requirements, see the Hardware Compatibility List on the VMware Web site.
By default, vMA uses one virtual processor, and requires 3GB of storage space for the vMA virtual disk. The recommended memory for vMA is 600MB.
You must have the following software to deploy vMA.
vSphere 5.0 and later
vSphere 4.1 later
|You can deploy vMA to an ESXi host using a vSphere Client connected directly to the
ESXi host or using a vSphere Client connected to a vCenter Server system.
||You need a vSphere Client to deploy vMA.
You can use vMA to target vSphere 5.1, vSphere 5.0 and later, and vSphere 4.1 and later systems.
For information on setting up vMA for a non-English keyboard, see KB 1007551.
You can deploy the vMA OVF from your vSphere Client connected to a vCenter Server system or ESXi host, as described in the vSphere Management Assistant Guide.
Important: You cannot upgrade from an earlier version of vMA to vMA 5.1. You need to do a fresh installation of vMA 5.1.
When you start vMA, proceed as follows:
- Download and unzip the vMA ZIP archive.
- In the vSphere Client, choose File > Deploy OVF Templating.
- When prompted by the wizard, click Deploy from a file or URL and select the OVF in the folder to which you have extracted the ZIP file and follow the instructions in the wizard.
- Select an option from the menu and configure the selected network setting.
- When prompted, specify a password for the vi-admin user for logging in to vMA. The password must conform to the vMA password policy. The password must have at least:
The vi-admin user has root privileges on vMA. The root user is disabled.
- Nine characters
- One upper case character
- One lower case character
- One numeral character
- One symbol such as #, $
Note: If the password contains any blank spaces, then logging in to vMA through the Web UI fails.
Prior Releases of vMA 5.1
Features and known issues from prior releases of vMA 5.1 are described in the release notes for each release. To view release notes for prior releases of vMA, go to the following links:
This release of vMA includes few usability-related fixes.
Other than the known issues reported in the vMA 5.0 release, this release includes the following known issues.
Removing and re-adding a target, whose IP address is changed, to a vMA instance fails with an error
You have added an ESXi host as a target to a vMA instance with the authentication policy set to fastpass authentication.
vifp addserver myesxihost.example.com --authpolicy fpauth
You then change the IP address of the target and modify the IP address to FQDN association record in /etc/hosts. Now, if you try to remove this target by using the vifp removeserver command, the following error is thrown:
Error: Invalid response from the host.
You can, however, remove the target by using the --force option. If you then try to re-add this forcefully removed target to the same vMA instance, an error is thrown. The removed target cannot be added even if its IP address is reverted to the original one.
Logging in to vMA through the Web UI fails
If the password contains any spaces, then logging in to vMA through the Web UI fails. You can, however, successfully log in to vMA through SSH and vSphere Client using the same user credentials.
Resxtop fails to run against vSphere 5.1 targets with error SSL Exception: Verification parameters
When you run resxtop against vSphere 5.1 targets, the following error might occur:
Login failed, reason: HTTPS_CA_FILE or HTTPS_CA_DIR not set
If SSL certification is set in the vCLI client of the vSphere 5.1 target, then resxtop might fail with the following error:
SSL Exception: Verification parameters
Workaround: No workaround.
Configuring an IPv6 address for vMA fails
When configuring an IPv6 address for vMA, the network configuration fails with an error similar to the following:
[ERROR] Attempted translation of an Invalid IPv6 address
This error occurs for both DHCP and static IPv6 configuration. However, you can successfully configuring an IPv4 address for vMA.