VMware

vSphere Management Assistant 6.0 Release Notes

vSphere Management Assistant | 12 Mar 2015 | Build 2503728

Last Document Update: 12 Mar 2015

The release notes cover 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.

About vSphere Management Assistant

vSphere Management Assistant is a Linux-based virtual machine that is pre-installed using a command-line interface and select third-party agents needed to manage your vSphere infrastructure. Administrators and developers can use vSphere Management Assistant to run scripts and agents to manage ESXi 5.0 and later systems, including ESXi 6.0. vSphere Management Assistant includes the vSphere SDK for Perl and the vSphere Command-Line Interface (vSphere CLI). vSphere Management Assistant also includes an authentication component named vi-fastpass. You can use vi-fastpass to directly connect to the established target servers. vSphere Management Assistant 6.0 also includes DCLI commands which allow you to manage services that are new in vSphere 6.0 and are presented by the vCloud Suite SDK interface.

For information about vSphere CLI, refer to the vSphere Command-Line Interface Documentation.

What's New

  • New options to the vifp listservers management command allow you to list target systems.

    Usage

    listservers [-l | --long]
    [--sortby <name | ptype | apolicy | version | build>]
    [--listby ptype [esx | esxi | vcenter] apolicy [adauth | fpauth] version
    [v1-v2 | v] build [b1-b2| b] and [Repeat any of the above listby parameters]]

    Examples

    vifp listservers List all the servers
    vifp listservers -- l List all the servers in long format.
    vifp listservers --listby ptype esx List servers of ptype ESX.
    vifp listservers --listby ptype esxi List servers of type ESXi.
    vifp listservers --listby ptype vcenter List servers of type vCenter.
    vifp listservers --listby ptype esxi --sortby version List servers of type ESXi and sort by version.
    vifp listservers --listby ptype esxi version 5.5.0 --sortby version List servers of type ESXi with 5.5.0 and sort by version.
    vifp listservers --listby ptype esxi version 5.5.0 --sortby name List servers of type ESXi and version 5.5.0 and sort by name.
  • You might not be able to log in to vSphere Management Assistant client by using Active Directory credentials. This change has been incorporated to further secure the vSphere Management Assistant appliance. You must use the less privileged vi-user account, navigate to su active directory/user, and then log in to active directory/user to perform all your management tasks.

    If you want direct SSH access to the appliance with Active Directory credentials, then comment out the AllowGroups line in the sshd_config file.

  • vSphere Management Assistant supports ESXi hosts and vCenter Sever targets with IPv6, but without Active Directory user authentication. However, the local user mode works with IPv6 targets.

  • vSphere Management Assistant Welcome page format is updated according to the security compliance.

  • vSphere Management Assistant supports DCLI commands for managing services that are new in vSphere 6.0 and presented by the vCloud Suite SDK.

  • Important changes made in vCLI. For more information, see https://www.vmware.com/support/developer/vcli/vcli60/vsp6_60_vcli_relnotes.html

Hardware and Software Requirements

To set up vSphere Management Assistant, you need the hardware listed in the following table.

Hardware Description
ESXi host Because vSphere Management Assistant runs a 64-bit operating system, the ESXi host on which vSphere Management Assistant is to be deployed must support 64-bit virtual machines.
CPU AMD Opteron Rev E or later. AMD-V hardware virtualization is not required.

VT enabled Intel processors with EM64T support.

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, vSphere Management Assistant uses one virtual processor, and requires 3 GB of storage space for the vSphere Management Assistant virtual disk. The recommended memory for vSphere Management Assistant is 600 MB.

You must have the following software to deploy vSphere Management Assistant.

Software Description
vSphere 5.0 and later You can deploy vSphere Management Assistant to an ESXi host by using a vSphere Client connected directly to the ESXi host or using a vSphere Client connected to a vCenter Server system.
vSphere Client You need a vSphere Client to deploy vSphere Management Assistant.

You can use vSphere Management Assistant to target ESXi 5.0 and later systems, including ESXi 6.0.

For information about setting up vSphere Management Assistant for a non-English keyboard, see KB 1007551.

Installing vSphere Management Assistant

You can deploy the vSphere Management Assistant 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 vSphere Management Assistant to vSphere Management Assistant 6.0. You need to perform a fresh installation of vSphere Management Assistant 6.0.

  1. Download and unzip the vSphere Management Assistant ZIP archive.

  2. In the vSphere Client, select File > Deploy OVF Template.

  3. When prompted by the wizard, click Deploy from a file or URL, select the OVF in the folder to which you have extracted the ZIP file, and follow the instructions in the wizard.

When you start vSphere Management Assistant, perform the following steps:

  1. Select an option from the menu and configure the selected network setting.

  2. When prompted, specify a password for the vi-admin user for logging in to vSphere Management Assistant. The password must conform to the vSphere Management Assistant password policy. The password must have at least the following attributes:

    • Nine characters
    • One upper case character
    • One lower case character
    • One numeral character
    • One symbol such as #, $

    The vi-admin user has root privileges on vSphere Management Assistant. The root user is disabled.

    Note: If the password contains any blank spaces, then logging in to vSphere Management Assistant through the Web UI fails.

Earlier Releases of vSphere Management Assistant

Features and known issues from earlier releases of vSphere Management Assistant 6.0 are described in the release notes for each release. To view release notes for earlier releases of vSphere Management Assistant, go to the following links:

Resolved Issues

  • resxtop command is not working

    After you successfully log in to an ESXi host, the command prompt is returned immediately and resxtop is not loaded.

    This issue has been resolved in this release.

  • Unexpected error occurs if you query the status of service /etc/init.d/vmware-tools-services

    If you attempt to query the status of the service /etc/init.d/vmware-tools-services, the following errors occur:

    Error: Unable to open the installer database /etc/vmware-tools/locations in append-mode
    Error: Unable to open the installer database /etc/vmware-tools/locations in append-mode
    Error: Unable to open the installer database /etc/vmware-tools/locations in append-mode

    This issue has been resolved in this release.

  • For ESXi 6.0 targets, resxtop does not display the process CPU usage statistics correctly

    When you run the resxtop command, information about the process CPU is missing. The information is displayed correctly if you run the esxtop command in the local console.

    This issue has been resolved in this release.

  • SCP or SSH session to another machine from vSphere Management Assistant appliance fails

    If you try to establish an SCP or SSH session to another machine from the vSphere Management Assistant appliance, a /usr/bin/ssh: symbol lookup error: /usr/bin/ssh: undefined symbol: FIPS_mode error message is displayed.

    This issue has been resolved in this release.

  • No NTP client is preinstalled with vSphere Management Assistant

    If you try to run NTP related commands in vSphere Management Assistant, command not found error is displayed.

    This issue has been resolved in this release.

  • ESXCLI command displays SSH thumbprint error

    When you run an ESXCLI command in each ESX target, SSH thumbprint error is displayed. Add the thumbprint against each ESX target using credstore_admin.pl utility. Run the following command:

    /usr/lib/vmware-vcli/apps/general/credstore_admin.pl add -s <ServerName> -T <Thumbprint>

    where : ServerName is the ESX target name and Thumbprint is the value that is received in the error while running the esxcli command.

    For example:

    vi-admin@sin2-pek-esxplatdhcp156:/> /usr/lib/vmware-vcli/apps/general/credstore_admin.pl add -s sin2-pek-esxplatdhcp211.eng.vmware.com -t E2:FA:96:09:FC:18:C8:19:07:3F:78:12:74:46:66:1E:C8:3B:84:8C

    vi-admin@sin2-pek-esxplatdhcp156:/> /usr/lib/vmware-vcli/apps/general/credstore_admin.pl add -s 10.111.8.211 -t E2:FA:96:09:FC:18:C8:19:07:3F:78:12:74:46:66:1E:C8:3B:84:8C

    This issue has been resolved in this release.

Known Issues

Other than the known issues reported in the vSphere Management Assistant 5.5 release, this release includes the following known issues.

  • vSphere Management Assistant fails to operate Windows based vCenter Server 6.0 with Active Directory authentication

    After adding Windows based vCenter Server into an Active Directory domain as a target of vSphere Management Assistant, you cannot log in to Windows based vCenter Server with Active Directory domain credentials.

    Workaround:Use the less privileged vi-user account, navigate to su active directory/user, and then login to active directory/user to perform all your management tasks.
  • vSphere Management Assistant cannnot add ESXi host as target by using Active Directory mode with IPv6 address

    vSphere Management Assistant cannot add ESXi host as target by using Active Directory mode with IPv6 address because ESXi host cannot join the domain.

    Workaround: Perform the following steps:
    1. Add the ESXi host to a vCenter Server instance.
    2. Join vCenter Server to the Active Directory domain.
    3. Add the vCenter Server target by using fastpass mode with the Active Directory account.
    4. Use the ESXi host through the vCenter Server.
  • vSphere Management Assistant configured with IPv6 prompts for credentials for targets that have both IPv4 and IPv6 configuration enabled

    When vSphere Management Assistant is configured with IPv6 only, it prompts for credentials for targets that have both IPv4 and IPv6 configuration enabled.

    Workaround: Configure targets with only IPv6 enabled and then add the targets to vSphere Management Assistant. It will not prompt for credentials.
  • DCLI command is not set in the default path in vSphere Management Assistant

    DCLI is not part of the path in vSphere Management Assistant and you must run it with the full path. Navigate to the path and execute DCLI or add the location to the appliance path.

    DCLI is available at /usr/lib/vmware-vcli/bin/vmware-dcli/.

    Workaround: Navigate to the dcli directory and then run the /usr/lib/vmware-vcli/bin/vmware-dcli/dcli command. OR

    Set the dcli to the vSphere Management Assistant appliance path and then run the export PATH=$PATH:/usr/lib/vmware-vcli/bin/vmware-dcli/ command directly.