VMware

VMware Infrastructure Management Assistant (VIMA) 1.0
Release Notes

Released 27-October-2008

Build 124830 is the release of the VMware Infrastructure Management Assistant 1.0.

VMware Infrastructure Management Assistant (VIMA) 1.0 Release Notes

Welcome to the VIMA 1.0 release.

VIMA allows developers and administrators to run agents and scripts to manage ESX and ESXi systems.

This document contains the following information:

About VIMA

VIMA is a virtual machine that includes prepackaged software. Administrators and developers can use VIMA to run scripts and agents to manage ESX and ESXi systems. VIMA includes the VI Perl Toolkit and the VMware Infrastructure Remote CLI. VIMA also includes the vi-fastpass authentication component and the vi-logger logging component. vi-fastpass allows direct connection to established target servers. vi-logger allows you to collect logging information from ESX and ESXi hosts and store the information on VIMA for analysis.

You can import VIMA as a virtual appliance into a VMware ESX/ESXi version 3.5 system. See the VMware Infrastructure Management Assistant Administrator's and Developer's Guide for installation information.

Supported Platforms

You can import VIMA 1.0 into VMware ESX/ESXi version 3.5 (or later) and VirtualCenter 2.5 (or later) systems.

Because VIMA runs a 64-bit operating system, the ESX/ESXi host on which it runs must support 64-bit virtual machines.

For running 64-bit virtual machines, the hardware of the ESX/ESXi host must have a 64-bit processor with virtualization support.

  • For AMD Opteron CPUs, the processor must be Rev E or later. AMD-V hardware virtualization is not required.
  • For Intel CPUs, the processor needs EMT64 (or x86-64) support and Intel-VT hardware virtualization.

For additional information, see VMware Knowledge Base article 1901 at http://kb.vmware.com/kb/1901.

512MB of memory is recommended for VIMA.

When you run scripts and commands from VIMA, you can choose ESX/ESXi version 3.5 (or later) targets.

Installing VIMA

You import VIMA as a virtual appliance, as discussed in the VMware Infrastructure Management Assistant Administrator's and Developer's Guide.

You have two choices:

  • Downloading and importing the VIMA ZIP file
    1. Download the VIMA ZIP file from http://www.vmware.com/download/download.do?downloadGroup=VIMA and unzip the ZIP file.
    2. In the VI Client, choose Virtual Appliance > Import.
    3. When prompted by the Wizard, click Download from File and point to the OVF included in the ZIP file.
  • Importing from URL
    1. In the VI Client, choose Virtual Appliance > Import.
    2. When prompted by the Wizard, click Download from URL and enter the following URL:

      http://www.vmware.com/go/importvima/vima1.ovf

When you start up VIMA, proceed as follows:

  • In the Linux Network Configuration tool, use the Tab and Space keys to either specify custom network settings, or exit the tool to continue with the start-up process.
  • When prompted, supply a host name for VIMA.
  • When prompted, specify a password for VIMA to use for the vi-admin user. This user has root privileges on VIMA. When using sudo, specify the vi-admin user's password. The root user is disabled.

See the VMware Infrastructure Management Assistant Administrator's and Developer's Guide for more information.

Known Issues

The VIMA release has the following known issues:

  • Some Remote CLI commands do not support vi-fastpass
    The svmotion, vmware-cmd, and resxtop Remote CLI commands do not support vi-fastpass.

    Workaround: You can still execute the commands as Remote CLIs. Set up a connection to the target server using a session file or environment variable. For svmotion and vmware-cmd, you can specify the --username and --password options when you execute the command. See the next issue for using these options in conjunction with resxtop.

  • After vi-fastpass has been set up, resxtop does not work correctly with other servers
    If you set up some target servers for VIMA and run resxtop.sh --server myTarget, the command succeeds with a minor error that you can ignore. However, if you attempt to run resxtop using the --server, --username, --password options supported for all Remote CLIs, the command fails.

    Workaround:

    1. Login to VIMA
    2. Unset the following variables by issuing the following commands:

      unset LD_PRELOAD
      unset LD_LIBRARY
    3. Now run resxtop.sh
  • Cannot run resxtop in replay mode using VIMA
    Running resxtop in replay mode using VIMA is not supported.

    Workaround: No workaround. Note, however, that resxtop is supported in interactive mode.

  • No warning when importing OVF into unsupported ESX hosts
    You can successfully import the VIMA OVF into a 64-bit ESX host that does not meet the requirements. However, when you power on VIMA, an incompatibility message is displayed.

    Workaround: Use one of the supported platforms, listed in Supported Platforms.

  • When vi-user runs vicfg-snmp.pl Remote CLI incorrect error message results
    If you log in to VIMA as vi-user and run vicfg-snmp.pl the following error message results: system does not have SNMP agent configuration supported. This error message is incorrect. It should explain that vi-user does not have privileges for running the command.

    Workaround: Log in to VIMA as vi-admin to run the command.

  • Bad VI Client performance because of VIMA log collection
    If the performance of a VI Client connected to an ESX host is bad, and if VIMA is collecting logs from that ESX host, check the VIMA vilogd log file for authentication failure errors. If there are errors, the authentication credentials for the ESX host have become out of sync with the VIMA credentials, and the VIMA connection attempts slow down the VI Client.

    Workaround: Remove the ESX host from VIMA using vifp removeserver, then add the server again using vifp addserver.

  • vima-update error message confusing
    If you call vima-update, a message The format of the metadata is invalid results. That message indicates either that the URL provided in the /etc/vmware/esxupdate/vimaupdate.conf file is incorrect, or that a networking issue (proxy required) prevents access to the URL.

    Workaround: Check the URL and supply one that points to VIMA updates. If a proxy server is required, add it to the /etc/vmware/esxupdate/vimaupdate.conf file, as discussed in the VMware Infrastructure Management Assistant Administrator's and Developer's Guide.

  • vima-update help message confusing
    As documented in the VMware Infrastructure Management Assistant Administrator's and Developer's Guide, vima-update, supports only the check, scan, and update options. Running vima-update --help lists additional options, which are not supported.

    Workaround: No workaround needed

  • vima-update uses HTTP
    For VIMA 1.0, vima-update uses the HTTP protocol.

    Workaround: No workaround.

  • Cannot clone VIMA
    Cloning the VIMA 1.0 virtual machine is not supported.

    Workaround: No workaround.

  • VI Perl Toolkit included in VIMA does not support CIM
    VI Perl Toolkit 1.6 includes the Web Services for Management component, which supports CIM. This component is not included with VIMA 1.0.

    Workaround: No workaround.

Last updated 29-Oct-2008 4 pm