VMware

VMware vCenter Server 4.1 Update 3a Release Notes

VMware Infrastructure Management Installer | 31 Jan 2013 (For all locales)
vCenter Server 4.1 Update 3a | 31 Jan 2013 | Build 925676
vSphere Client 4.1 Update 3a | 31 Jan 2013 | Build 925676

Last Document Update: 7 Feb 2013

What's in the Release Notes

The release notes cover the following topics:

What's New

This release delivers a security fix that has been documented in the Resolved Issues section.

Earlier Releases of VMware vSphere 4.1

Features and known issues from earlier releases of vSphere 4.1, are described in the release notes for each release. To view release notes for earlier releases of vSphere 4.1 components, click the following links:

Before You Begin

ESX/ESXi, vCenter Server, and vSphere Client Version Compatibility

The VMware Product Interoperability Matrix provide details on the compatibility of current and earlier versions of VMware vSphere components, including ESX, vCenter Server, the vSphere Client, and optional VMware products. In addition, check the vSphere Compatibility Matrixes for information about supported management and backup agents before installing ESX or vCenter Server.

Installation and Upgrade

You can install vCenter Server 4.1 on Windows 64-bit platforms only. If you have VirtualCenter 2.x installed, see the vSphere Upgrade Guide for instructions about installing vCenter Server on a 64-bit operating system and preserving your VirtualCenter database.

For step-by-step guidance on installing and configuring ESX and vCenter Server, see ESX and vCenter Server Installation Guide.

After successful installation, several configuration steps, particularly for licensing, networking, and security configuration are essential. Refer to the following guides in the vSphere documentation for guidance on these configuration tasks.

Later releases of VMware vSphere might not support VMFS version 2 (VMFS2). The best practice is to upgrade or migrate to VMFS version 3 or later. See the vSphere Upgrade Guide.

Before you install or upgrade to vCenter Server 4.1 Update 3a, verify that the database parameter options are set. For more information, see KB 1024449.

Upgrading or Migrating to vCenter Server 4.1 Update 3a

You can upgrade from VirtualCenter 2.5 Update 6b, vCenter Server 4.0, vCenter Server 4.0 Update 1, vCenter Server 4.0 Update 2, vCenter Server 4.0 Update 3, vCenter Server 4.0 Update 4, vCenter Server 4.1, vCenter Server 4.1 Update 1, vCenter Server 4.1 Update 2, and vCenter Server 4.1 Update 3 to vCenter Server 4.1 Update 3a.

To upgrade, first verify that your database is supported with vCenter Server 4.1 Update 3a, back up your supported database, SSL certificates, and VirtualCenter Server configuration, and then run the vCenter Server installer. The installer informs you that an earlier version of vCenter Server is on the computer and will be upgraded.

Plug-Ins Updates

This release of the vCenter Server 4.1 Update 3a does not include updates to VMware Update Manager ,VMware Guided Consolidation, or VMware Orchestrator.

Documentation

The VMware vSphere 4.1 documentation is applicable for the VMware vSphere 4.1 Update 3a release. See the following documentation pages:

Internationalization

VMware vSphere 4.1 Update 3a is available in the following languages:

  • English
  • French
  • German
  • Japanese
  • Simplified Chinese

vSphere Client Locale Forcing Mode

With vSphere 4.1 Update 3a, you can configure the vSphere Client to provide the interface text in English even when the operating system on which it is running is non-English. This configuration can be done for the duration of a single session by supplying a command-line switch. This configuration applies to the interface text and does not affect other locale-related settings such as date/time or numeric formatting.

The following vSphere Client command causes the individual session to appear in English:

vpxClient -locale en_US

Open Source Components for vSphere

Open source components and their respective licenses for the most recent generally available release of vSphere are available at http://www.vmware.com/download/vsphere/open_source.html, on the Open Source tab. From this link, you can also download the source files for any GPL or LGPL, or other similar licenses that require the source code or modifications to source code to be made available, for the most recent generally available release of vSphere.

Resolved Issues

vCenter Server and vSphere Client contain a vulnerability in the handling of the management authentication protocol. To exploit this vulnerability, an attacker must convince either vCenter Server or vSphere Client to interact with a malicious server as a client. Exploitation of the issue might lead to code execution on the client system.
To reduce the likelihood of exploitation, vSphere components should be deployed on an isolated management network.

The Common Vulnerabilities and Exposures Project (cve.mitre.org) has assigned the name CVE-2013-1405 to this issue.

This issue is resolved in this release.

Known Issues

The Known Issues section covers Functionality Caveats and provides a List of Known Issues.

Functionality Caveats

IPv6 Disabled by Default. IPv6 is disabled by default when installing ESX 4.1 Update 1.

Hardware iSCSI. Broadcom Hardware iSCSI does not support Jumbo Frames or IPv6. Dependent hardware iSCSI does not support iSCSI access to the same LUN when a host uses dependent and independent hardware iSCSI adapters simultaneously.

List of Known Issues

The following issues are known to occur. The known issues are grouped as follows:

Internationalization

  •  Drop-down menu items for DRS Rules UI screen improperly translated
    When you create a VM/Host DRS rule using a non-English UI, the drop-down menu options are incomprehensible.

    Workaround: None.

  • Help files of Performance Overview charts in the French localized vCenter Server are displayed in English
    When using the French localized vCenter Server, if you click the help icons of the Performance overview charts, the help files are displayed in English.

    Workaround: Change the URL of the help file from .../help/en/... to .../help/fr/....

Miscellaneous

  • vCenter Server tempDB grows excessively
    Certain third-party applications, such as Veeam's nWorks, connect to vCenter Server and issue search specifications with a very large search criteria. This results in a large query being run on the vCenter Server database. In some cases, this query continues to be parsed while it fills up the TempDB space of the database. The VMware VirtualCenter Server service might fail to start if the SQL Server disk space fills up as a result of this query running constantly on TempDB.
    The vpxd.log file contains entries similar to the following:
    BC error: (42000) - [Microsoft][SQL Native Client][SQL Server]Could not allocate a new page for database 'TEMPDB' because of insufficient disk space in filegroup 'DEFAULT'. Create the necessary space by dropping objects in the filegroup, adding additional files to the filegroup, or setting autogrowth on for existing files in the filegroup." is returned when executing SQL statement "SELECT EVENT_ID, CHAIN_ID, EVENT_TYPE, EXTENDED_CLASS, CREATE_TIME, USERNAME, CATEGORY, VM_ID, VM_NAME, HOST_ID, HOST_NAME, COMPUTERESOURCE_ID, COMPUTERESOURCE_TYPE, COMPUTERESOURCE_NAME, DATACENTER_ID, DATACENTER_NAME, DATASTORE_ID, DATASTORE_NAME, NETWORK_ID, NETWORK_NAME, NETWORK_TYPE, DVS_ID, DVS_NAME, CHANGE_TAG_ID FROM VPX_EVENT WHERE (EVENT_TYPE IN (?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,"
    Logs/vpxd/vpxd-9704.log.gz:[2011-08-15 05:56:11.343 06612 error 'App' opID=453570f1] vim.fault.DatabaseError
    Logs/vpxd/vpxd-9704.log.gz:[2011-08-15 05:57:08.856 06588 error 'App' opID=892090d5] [Vdb::IsRecoverableErrorCode] Unable to recover from 42000:1101


    To resolve this issue add the following parameter in the vpxd.cfg file:
    <event><maxVectorQuerySize>100</maxVectorQuerySize></event>
  •  VM/Host DRS Rules are still enforced if DRS is disabled
    If you specify a VM/Hosts DRS rule for a DRS cluster, and if DRS is disabled, this rule is still in effect. Accordingly, if you manually power on a virtual machine specified in this type of rule, an error might occur if this operation violates the rule.

    Workaround: Manually disable the rule in the cluster Settings dialog box.

  • Group ID length in vSphere Client shorter than group ID length in vCLI
    When you specify a group ID using the vSphere Client, only nine characters are allowed. In contrast, you can specify up to ten characters when you specify the group ID using the vicfg-user vCLI.

    Workaround: None.

Networking

  •  Clone operation fails on a virtual machine with invalid vDS backing
    If any of a virtual machine's network adapters are connected to an invalid or missing vDS or dvPort group, that virtual machine cannot be cloned.

    Workaround: Make sure that all of a virtual machine's network adapters have valid backing before cloning the virtual machine.

  • Newly added users with read-only role can add VMkernel NICs to ESX/ESXi hosts
    Newly added users with a read-only role should not be able to make changes to the ESX/ESXi host setup with the exception of adding VMkernel NICs, but are able to.

    Workaround: None. Do not rely on this behavior because read-only users will not be able to add VMkernel NICs in the future.

  • Memory problems occur when a host uses more than 1016 dvPorts on a vDS
    The maximum number of dvPorts allowed per host on vDS is 4096, but memory problems can start occurring when the number of dvPorts for a host approaches 1600. When this occurs, you cannot add virtual machines or virtual adapters to the vDS.

    Workaround: Configure a maximum of 1016 dvPorts per host on a vDS.

  •  Destroy operation fails on virtual machines with invalid vDS backing
    If any of a virtual machine's devices are connected to an invalid vDS, a destroy operation might not be completed successfully. The virtual machine is destroyed on the host, but remains visible in the vSphere Client inventory.

    Workaround: To remove the virtual machine from the vCenter inventory, right-click the virtual machine and select Remove from inventory.

  • Reconfiguring a VMXNET3 NIC while Wake-on-LAN is enabled and the virtual machine is asleep causes the virtual machine to resume

    Workaround: Put the virtual machine back into sleep mode manually after reconfiguring a VMXNET3 vNIC (for example, after performing a hot-add or hot-remove).

  •  Adding multiple hosts to a Cisco Nexus 1000v switch in one batch might fail
    If you try to add multiple hosts with different patch or update levels to a Cisco Nexus 1000v switch, the add hosts operation fails.

    Workaround: Add hosts with different patch or update levels to the switch individually.

  •  Virtual machine MAC address conflicts
    Each vCenter Server system has a vCenter Server instance ID. This ID is a number between 0 and 63 that is randomly generated at installation time but can be reconfigured after installation.
    vCenter Server uses the vCenter instance ID to generate MAC addresses and UUIDs for virtual machines. If two vCenter Server systems have the same vCenter instance ID, they might generate identical MAC addresses for virtual machines. This can cause conflicts if the virtual machines are on the same network, leading to packet loss and other problems.

    Workaround: If you deploy virtual machines from multiple vCenter Server systems to the same network, you must ensure that these vCenter Server systems have unique instance IDs.

    To view or change the vCenter Server instance ID:

    1. Log in to vCenter Server using the vSphere Client, and select Administration > vCenter Server Settings.
    2. Select Runtime Settings.
      The vCenter Server Unique ID text box displays the current vCenter Server instance ID.
    3. If this ID is not unique, type a new unique value between 0 and 63 in the vCenter Unique ID text box and click OK.
    4. If you changed the vCenter Server instance ID, restart vCenter Server for the change to take effect.

    If you have existing virtual machines with conflicting MAC addresses, edit the MAC addresses to make them unique:

    1. Ensure that the virtual machine is powered off.
    2. In the vSphere Client inventory, right-click the virtual machine and select Edit Settings.
    3. On the Hardware tab, select the virtual network adapter for the virtual machine.
    4. Under MAC Address, select Manual and specify a unique MAC address.
    5. Click OK.

    Alternatively, you can force vCenter Server to generate a new MAC address for the virtual network adapter by configuring the virtual network adapter to use a Manual MAC address, and then reconfiguring it to Automatic.

Server Configuration

  • Applying host profiles on hosts can swap the order of vmk numbers if the host uses both vNetwork Distributed Switch and vNetwork Standard Switch
    Applying a host profile might result in vmk numbers to be swapped between portgroups of vNetwork Distributed Switch and vNetwork Standard Switch, if the portgroup order on the host is different than the order in which folders and port groups are listed in the host profile. This issue occurs because vCenter creates port groups in the order the port group folders are listed in the host profile.
    For example, If the network configuration of the ESX/ESXi host is similar to the following:
    vmk0: vDS-MGMT
    vmk1: vDS-vMOTION
    vmk2: vSS-iSCSI-104
    vmk3: vSS-iSCSI-105


    And the folders under Networking Configuration of the profile is in the following order:
    Host Port Group
    vSS-iSCSI-104
    vSS-iSCSI-105

    Host Virtual NIC
    vDS-MGMT
    vDS-vMOTION


    After applying the host profile, the network configuration of the ESX/ESXi host looks like:
    vmk0: vSS-iSCSI-104
    vmk1: vSS-iSCSI-105
    vmk2: vDS-MGMT
    vmk3: vDS-vMOTION


    Workaround: Ensure that the vmk numbers on vNetwork Standard Switch are lower than the vmk numbers on vNetwork Distributed Switch.
  • Host Profiles compliance check displays non compliant when host is configured to join an organizational unit within a domain
    After you apply a host profile that configures a host to join an organizational unit (OU) in a domain, if you perform the host profile compliance check on the host with the same host profile, the result shows the host as non compliant.

    Workaround: Disable compliance check for directory services in the host profile.
  • Applying a host profile to an ESX host sometimes fails, resulting in an error about operation not being supported
    For this issue, the following error appears in the vSphere Client:

    Operation not supported: Operation not supported


    This problem occurs because the host profile attempts to configure settings on a pseudo physical NIC vusb0 on the ESX host. However, the pseudo NIC does not allow changes to the configuration settings.

    Workaround:
    1. Right-click the profile and select Edit Profile.
    2. Navigate to the Physical NIC configuration of the Network configuration.
    3. Find the physical NIC configuration profile for vusb0 by checking the name of the physical NIC.
    4. Right-click that physical NIC configuration profile and click Remove Profile.
  • Operations that involve applying profiles and checking profile compliance fail for host profiles after you update PnicsByName policy within DvsProfile
    After updating the PnicsByName policy of DvsProfile, the host profile application and compliance check fails. This failure occurs when multiple physical NICs are entered. While the user interface allows multiple physical NICs, only one physical NIC can be added for the PnicsByName policy within DvsProfile.

    Workaround: Ensure that only one physical NIC is added for this policy.

  • Host profile compliance checks fail to detect non-compliance when a host has different portgroups or NAS datastores
    When a host profile is checked for compliance against a host that has different portgroups or NAS datastores than the ones specified in the host profile configuration settings, the compliance check incorrectly displays the result as Compliant.
    Workaround: User can still apply the host profile by using the Apply Profile option, which detects the differences and applies the configurations correctly.

Storage

  • Newly created virtual hard disks are incorrectly placed at the same location as an existing virtual hard disk located in a different directory
    For a virtual machine whose virtual hard disk is in the same datastore as its .vmx files but is in a directory different from that of the .vmx files, when you create a virtual hard disk, the new virtual hard disk is placed in the directory where the existing virtual hard disk is placed and not in the default .vmx directory.

    Workaround: Move the newly added virtual hard disk to the same desired location as the virtual machine's .vmx file by using Data Browser, then remove the virtual disk by using the Edit Settings option for the virtual machine and then re-add the virtual hard disk selecting the Use an existing virtual disk option.

    Note: When an existing virtual disk is located on a different datastore/LUN, any newly created disk drive is created in the same directory as the .vmx file.
  •  After you upgrade a storage array, the hardware acceleration status in the vSphere Client changes to Supported after a short delay
    When you upgrade a storage array's firmware to a version that supports VAAI functionality, vSphere 4.1 does not immediately register the change. The vSphere Client temporarily displays Unknown as the status for Hardware Acceleration.

    Workaround: This delay is harmless. The hardware acceleration status changes to Supported after a short period of time.

Upgrade and Installation

  • You cannot install Orchestrator in a custom location containing underscore in the path name
    When you install Orchestrator 4.1.3, both with the vCenter Server installer or with the standalone installer, you can select to install Orchestrator in a custom location. If the custom installation path you select contains underscore characters, the installation fails.

    Workaround: Use custom installation paths without underscore characters.

  • vCenter Orchestrator 4.1 Update 3 (4.1.3) resets the default Orchestrator login password
    After you upgrade to Orchestrator 4.1.3, you can log in to the Orchestrator configuration interface with the default password
    If you change the default password in Orchestrator 4.0.x or 4.1.x configuration interface and you upgrade Orchestrator to version 4.1.3, your password is reset and you must use the default password to log in to the Orchestrator instance.
  • The Hardware Status tab and the vCenter Service Status screen might not display any information if the HTTP and HTTPS ports are changed while upgrading vCenter Server
    If you change the port settings of HTTP and HTTPS ports (value other than the default 8080 and 8443) while upgrading vCenter Server, the Hardware Status tab and the vCenter Service Status screen might not display any information.

    Workaround: After upgrading vCenter Server, change the port value of HTTPS in the extension.xml files and the port value of HTTP in the proxy.xml file.
    For example if the port for HTTP is 8087 and HTTPS is 8444, perform the following steps:
    1. Stop the VMware Virtual Center Server service.
    2. Open the extensions.xml file available at \Program Files\VMware\Infrastructure\VirtualCenter Server\extensions\cim-ui and replace the line <url>https://*:8443/cim-ui/scriptConfig.xml</url> with <url>https://*:8444/cim-ui/scriptConfig.xml</url>.
    Where 8444 is the configured port for HTTPS.
    3. Similarly update the extension.xml file in the com.vmware.vim.stats.report, health-ui, and license-ui folders.
    4. Open the proxy.xml file available at \Documents and Settings\All Users\Application Data\VMware\VMware VirtualCenter and replace all 8080 values with 8087.
    Where 8087 is the configured port for HTTP.
    5. Start the VMware Virtual Center Server service.
    6. In the vCenter Server navigate to Administration -> vCenter Server Settings -> Advanced Settings and replace the default 8443 port of VirtualCenter.VimWebServicesUrl to 8444.
    7. Restart the VMware Virtual Center Server service.

  • Microsoft SQL Server 2008 Express (x32 and x64) and Microsoft SQL Server 2008 R2 Express (x32 and x64) databases are compatible with vCenter Server 4.1 Update 2 for a maximum of 5 hosts and 50 virtual machines
  • vCenter Server 4.1 database upgrade might fail if the default schema is not dbo
    If you do not use the default dbo schema when using Microsoft SQL database for your vCenter Server repository, attempts to upgrade to vCenter Server 4.1 might fail with a message similar to the following:
    Exception thrown while executing SQL script

    The vcdatabaseupgrade.log file might display errors messages similar to the following:
    SET IDENTITY_INSERT dbo.vpx_device_tmp ON
    [11/5/2010 11:51:50 AM] Error: Failed to execute command: SET IDENTITY_INSERT dbo.vpx_device_tmp ON
    [11/5/2010 11:51:50 AM] Got exception: ERROR [42000] [Microsoft][SQL Native Client][SQL Server]Cannot find the object "dbo.vpx_device_tmp" because it does not exist or you do not have permissions.


    Workaround: Restore the backed up database, change the default schema for the SQL login to dbo, and then upgrade the vCenter database.
  • Cannot uninstall vCenter Server running on Windows Server 2008 Release 2 by using the All Programs menu
    When you uninstall vCenter Server running on Windows Server 2008 Release 2 by selecting Start > All Programs > VMware > vCenter Server Linked Mode Configuration, an error similar to the following might be displayed:
    Error 280135: setup failed to copy LDIFDE.EXE from system folder to '%windr%\ADAM' folder

    Workaround: To uninstall vCenter Server, use Add/Remove Programs.
  •  Installation of vCenter Server 4.1 using an existing IBM DB2 database sometimes fails with a DB2 error message
    When you install vCenter Server 4.1 using an existing vCenter Server DB2 database, you might see an error message similar to the following:
    A database error occurred: "ODBC error: (5UA01) - [IBM][CLI Driver][DB2/NT64] SQL20453N The task "RULE_TOPN1_DB2USER1" cannot be removed because it is currently executing. SQLSTATE=5UA01" is returned when executing SQL statement "CALL CREATE_TOPN_JOB1_PROC()"

    This message appears when DB2 encounters an known IBM issue. This issue indicates that a DB2 task is running and the vCenter Server installer cannot initialize the vCenter database.

    Workaround: To eliminate the conflict so you can install vCenter Server, perform the following steps:
    1. If vCenter Server is running, shut it down.
    2. Use the Services control panel to stop and restart the db2 service.
    3. Restart the installation process, being sure to select the option to overwrite the existing database.
  •  Installation of the vSphere Client might fail with the error, The Microsoft Visual J# 2.0 Second Edition installer returned error code '4113'
    When you install the vSphere Client, the installer might attempt to upgrade an out-of-date Microsoft Visual J# runtime. The upgrade will be unsuccessful and the vSphere Client installation fails.

    Workaround: Uninstall all previous versions of Microsoft Visual J# and install the vSphere Client. The installation includes an updated Microsoft Visual J# package.

  •  After you install or upgrade to vCenter Server 4.1 with an Oracle database using an Oracle 64-bit ODBC driver, vCenter Server might fail to start
    When you perform a new installation or upgrade to vCenter Server 4.1 with an Oracle database using an Oracle 64-bit ODBC driver, you might see the error message, Database version id '0' is incompatible with this release of VirtualCenter, and the vCenter Server service fails to start.

    Workaround: Upgrade to the 10.2.0.4 or 11.1 Oracle 64-bit ODBC driver.

  •  When you uninstall vCenter Server 4.1 without stopping the vCenter Server service, the local ADAM instance might not be removed
    You must stop the vCenter Server service before you uninstall vCenter Server 4.1. Otherwise, the ADAM instance might remain on the system. This applies to both vCenter Server 4.1 installations and upgrades, and to standalone or linked vCenter Server systems.

    Workaround: Stop the VMware VirtualCenter Server service before you uninstall vCenter Server 4.1.

  •  vCenter Server installation or upgrade silently changes Microsoft SQL Server settings to enable named pipes
    When you install vCenter Server 4.1 or upgrade vCenter Server 4.0.x to vCenter Server 4.1 on a host that uses Microsoft SQL Server with a setting of "Using TCP/IP only," the installer changes that setting to "Using TCP/IP and named pipes" and does not present a notification of the change.

    Workaround: The change in setting to Using TCP/IP and named pipes does not interfere with the correct operation of vCenter Server. However, you can use the following steps to restore the setting to the default of Using TCP/IP only.

    1. Select Start > Programs > Microsoft SQL Server 2005 > Configuration Tools > SQL Server Surface Area Configuration.
    2. Select Surface Area Configuration for Services and Connections.
    3. Under the SQL Server instance that you are using for vCenter Server, select Remote Connections.
    4. Change the option under Local and Remote Connections and click Apply.
  •  Cannot create vCenter Server directory services during vCenter Server or vSphere Client installation
    When you select a compressed folder as the installation path for vCenter Server or vSphere Client, vCenter Server Directory Services is not created.

    Workaround: Perform one of the following tasks:

    • Uncompress the disk and retry the installation.
    • Run the installation on an uncompressed disk.
  •  vCenter Server installation fails with the error, Setup cannot create vCenter Directory Services instance
    If you remove the Everyone permission from the HKLM registry, vCenter Server installation fails with the error Setup cannot create vCenter Directory Services instance.

    Workaround: Add the Everyone permission to the HKLM registry:

    1. From the Windows command line, type regedit and press Enter.
    2. In the Registry Editor, right-click HKEY_LOCAL_MACHINE and select Permissions.
    3. Click Add.
    4. Click Advanced.
    5. Select Everyone from the list and click OK.
    6. Click Apply and click OK.
  • vCenter Server instances that use a DB2 9.5.0 database does not allow for addition of hosts
    If you are using a vCenter Server system with an IBM DB2 9.5.0 64-bit ODBC driver, you cannot manage hosts for that vCenter Server.

    Workaround: Apply DB2 9.5 Fix Pack 5.

  • Upgrading from vCenter Server 4.0 to 4.1 unregisters vCenter Guided Consolidation service (GCS)
    This issue only occurs when GCS is a registered extension (plug-in).

    Workaround: To establish the registration information with vCenter Server 4.1, reinstall GCS.
  •  vCenter Server upgrade proceeds despite changing Web Services HTTP or HTTPS port using established port
    When changing the Web Services HTTP or HTTPS port by using an established port on the Configure Ports page, the vCenter Server upgrade proceeds and does not produce an error.

    Workaround: None.

  • Install process fails when you uninstall and reinstall vCenter Server
    Installation fails with the error Cannot create vCenter Server Directory Services when you uninstall and reinstall vCenter Server on the same system.

    Workaround: After you uninstall vCenter Server, reboot the system before you reinstall vCenter Server.

  • Upgrading vCenter Server with the VM Total Disk Latency (ms) trigger set might lead to error messages
    This issue occurs after upgrading vCenter Server when the VM Total Disk Latency(ms) trigger and at least one other trigger are set at the same time. In such a scenario, using vSphere Client to edit the Alarm in Trigger section causes the following error message to appear in vSphere Client:

    The triggers for this alarm cannot be displayed or changed through the vSphere Client. Use the vSphere API to modify these alarm triggers.

    Workaround:

    1. Before upgrading vCenter Server, delete the VM Total Disk Latency(ms) trigger.
    2. Upgrade both vCenter Server and vSphere Client.
    3. Add the VM Max Total Disk Latency(ms) trigger.
  •  vCenter Server installation fails if the user account used to install vCenter Server and overwrite an existing DB2 database is not member of the db2user group or the db2admin group
    Error 25003: Cannot create repository is displayed when the user account used to install vCenter Server and overwrite an existing DB2 database is not a member of the db2user group or the db2admin group. Clicking OK in the error message dialog box closes the dialog box and rolls back the installation.

    Workaround: Add the database user to the db2user or db2admin group. Consult your database administrator.

  • Installation of vCenter Server 4.1 Update 2 with IBM DB2 9.7.2 Express C database might fail
    When installing vCenter Server 4.1 Update 2 with IBM DB2 9.7.2 Express C database, a warning message error similar to the following might be displayed:
    Warning 25205 : Error loading licensekey to LDAP server

    When you click OK, vCenter Server is installed successfully, but the VMware VirtualCenter Server service is not started. If you manually start the VMware VirtualCenter Server service, a message similar to the following is displayed:
    Windows could not start the VMWare VirtualCenter Server on Local Computer. For more information, review the System Event Log. If this is a non-Microsoft service, contact the service vendor, and refer to service-specific error code 2.

    Workaround: Create DB2USERS and DBSYSMON groups and assign to DB2 user. Restart the VMware VirtualCenter Server service.

vCenter Server, vSphere Client, and vSphere Web Access

  • Hardware Status tab might not display host health status when vSphere Client is connected to vCenter Server in linked mode group
    When different versions of vCenter Servers form a linked mode group, the Hardware Status tab might not display any information for some hosts. If these hosts are moved from one vCenter Server inventory to another, the Hardware Status tab might display their health status.

    Workaround: Connect vSphere Client to a standalone vCenter Server to view host health status in the Hardware Status tab.
  • The Hardware Status tab might not display health statuses of ESX 4.1 and ESX 4.0 hosts
    If the latest patches are not applied to ESX/ESXi 4.0 and ESX/ESXi 4.1 hosts managed by vCenter Server, the Hardware Status tab might fail to display the statuses of the hosts.

    To resolve this issue apply ESX400-201203001 patch on ESX 4.0 hosts, ESXi400-201203001 patch on ESXi 4.0 hosts, ESX410-201204001 patch on ESX 4.1 hosts, and ESXi410-201204001 patch on ESXi 4.1
  • Performance counters are shown to be at Stat-level 2 while they are actually moved to Stat-level3
    In vCenter Server, some performance counters are actually moved to Stat-level 3, but appear to be available at Stat-level 2 in the vSphere Client.The vSphere Client is not updated correctly to reflect the changes to CPU and disk related information, which have been moved to stat-level 3.

    Workaround: Move to Stat-level 3 to use those counters.
  • Reconfiguring an alarm that monitors hosts or virtual machines might reset another alarm
    If you reconfigure an alarm that monitors hosts or virtual machines, another alarm that is affected by the host or virtual machine might reset for a brief period and then returns back to its previous state.
    For example, consider that two alarms are configured in vCenter Server, one based on Host CPU Usage(%) and another based on Host Memory Usage(%). If you reconfigure the alarm based on Host CPU Usage(%), the alarm based on Host Memory Usage(%) is reset for a brief period of time and then the alarm returns back to its previous state.

    Workaround: None
  • Scheduled Tasks might display incorrect next run time if the vSphere Client system time is not set according to the UTC time zone
    If task is scheduled by using a vSphere client whose system time is not set according to the UTC, vCenter System might incorrectly schedule the task ahead or later than the actual desired time.
    The issue is caused by vCenter Server storing and processing scheduled task times in UTC. 

    For example, consider the scenario when a task is scheduled in the JST time zone with frequency and start time similar to the following:
    Frequency: Monthly
    Starting Time:1:00(JST)
    The last Wednesday of the month

    Now, at 1:00 (JST), the last Wednesday of the month according to UTC time zone might be the first Wednesday of the next month according to the JST time zone. This might cause the scheduled task to run on the first Wednesday of the next month. This issue occurs when the starting  time is between 0:00 and 8:59(JST).
  • Hardware Status tab might not display the health status
    vCenter Server might fail to display the health status in the Hardware Status tab.
    The vws.log file contains entries similar to the following:
    [2010-08-19 13:43:36,128 pool-8-thread-7 ERROR com.vmware.vim.security.vcauthorize.AuthorizeMgr] Parent chain incomplete or: group-d1

    When you check the vCenter database and run the following query, the resulting ID should be 1:
    select ID from VPX_ENTITY where TYPE_ID=7

    If the resulting ID is of any value other than 1, then Hardware Status does not display the status.

    Workaround: None
  • Event related to the accounts event category might not trigger alarms
    Alarms created in the vCenter Server with any of the following event triggers do not generate an alarm, when the trigger conditions are met:
    • Account created
    • Account removed
    • Account updated

    Workaround: None.

  • Hardware Status tab does not refresh automatically
    The hardware health status properties for a host that are displayed in the Hardware Status tab are not refreshed automatically, because such refreshes caused performance issues.

    Workaround: Click Update in the Hardware Status tab to view the latest hardware health status properties of hosts.
  • vCenter Server reports incorrect value for provisioned space on datastores
    The vCenter Server reports incorrect value for provisioned space on a datastore if you refresh the datastore immediately after powering on or powering off a virtual machine.

    Workaround: None
  • License key might not get migrated after vCenter Server is upgrade to vCenter Server 4.1
    After installing vCenter Server 4.0 in the evaluation mode, if you assign a license to the vCenter Server system after the evaluation period expires and you then upgrade to vCenter Server 4.1, the vCenter Server license key is not migrated after the upgrade. All hosts might get disconnected from the vCenter Server system. This issue occurs when the vCenter Server license key that is assigned after the evaluation period expires does not reflect in the database registry when backup operations are run.

    Workaround:
    • Before upgrading to vCenter Server 4.1, ensure that the vCenter Server license key is assigned correctly to vCenter Server by clicking Home > Licensing.
    • When upgrading to vCenter Server 4.1, enter the vCenter Server license key in the license screen of the installation wizard.
  • Advanced performance chart views does not display data for virtual machines if data counters not applicable to virtual machines are selected
    When customizing advanced performance chart views, if you use the per-virtual-machine stacked graph chart type for virtual machines and select data counters that are not applicable for virtual machines, the resulting chart does not display any performance data for the virtual machine. The Performance Chart Legend pane also does not show any data for the virtual machine.

    Workaround: When customizing advanced performance chart views, do not select data counter that are not applicable for virtual machines. To know the list of counters applicable for virtual machines, select a virtual machine in the vCenter Server inventory, click the Performance tab, and navigate to Advanced > Chart Options.
  • Users with Administrator privileges might not be able to obtain complete logs by running the Generate vCenter Server log bundle utility if vCenter Server is installed on Windows Server 2008 Release 2
    If vCenter Server is installed on Windows Server 2008 Release 2 and a vCenter Server system user with Administrator privileges runs the Generate vCenter Server log bundle utility, the complete logs are not obtained in the vcsupport folder. This issue is dose not occur for built-in Administrator user accounts.

    Workaround: As a user with administrator privileges, log into the Windows Server 2008 Release 2 vCenter Server System, navigate to Start -> All Programs -> VMware, right-click Generate vCenter Server log bundle and select Run as Administrator
  • ESX/ESXi hosts stop responding to vCenter Server if they are added using IPv6 link local address
    If ESX/ESXi hosts are added to vCenter Server using IPv6 link local address, the hosts enter a nonresponsinve state a few seconds after they are added.
    Workaround: None
  •  In Windows Vista, all Help buttons in the Update Manager Client open the default Update Manager help page
    If you are using Internet Explorer 7 browsers on Windows Vista machines, the vCenter Update Manager context-sensitive help does not display the required help pages. Instead, the help displays the Introducing Update Manager help page.

    Workaround: Apply Service Pack 2 to Windows Vista. For more details, see the following Microsoft knowledge base article http://support.microsoft.com/kb/942172.

  • Error occurs while trying to restart the VMware VirtualCenter service or the VMware Web service from Windows services panel
    While you are trying to restart the VMware VirtualCenter service or the VMware Web service from Windows Control Panel, you see the following message:
    Error 1053: The service did not respond it the start or control request in a timely fashion.

    Workaround: Modify two registry keys on the affected vCenter Server host as follows:

    1. Start regedit and locate the following key in the registry:
      HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\
      vctomcat\Parameters
    2. Add the following (DWORD) registry values:
      Value Name: WaitHintStart
      Value: <Time to wait for service to start in milliseconds>
      Value Name: WaitHintStop
      Value: <Time to wait for service to stop in milliseconds>
      In both cases, the wait time should be greater than 40 seconds.
    3. Locate the following key in the registry:
      HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\
      vpxd\Parameters
    4. Add the following (DWORD) registry values:
      Value Name: WaitHintStart
      Value: <Time to wait for service to start in milliseconds>
      Value Name: WaitHintStop
      Value: <Time to wait for service to stop in milliseconds>
      In both cases, the wait time should be greater than 40 seconds.
  •  Problems installing or running vCenter Server, VMware Update Manager, or VMware Converter on an operating system using the Czech locale
    If you attempt to install vCenter Server, Update Manager, or VMware Converter on an operating system that is using the Czech locale, you either cannot install the product or might experience functional problems when trying to use the product.

    Workaround: No workaround exists for Czech locale operating systems. Use English locale operating systems to evaluate the product.

  • Changing the network settings of an ESXi host prevents some hardware health monitoring software from auto-discovering it
    After you change the network settings of an ESXi host, third-party management tools that rely on the CIM interface (typically hardware health monitoring tools) are unable to automatically and dynamically discover the host through the Service Location Protocol (SLP) service.

    Workaround: Manually type the hostname or IP address of the host in the third-party management tool. Alternatively, restart slpd and sfcbd-watchdog using one of the following methods:

    • Log in to Technical Support Mode and run the following commands:

    • /etc/init.d/slpd restart
      /etc/init.d/sfcbd-watchdog restart

    • Restart management agents on the Direct Console User Interface (DCUI). This restarts other agents on the host in addition to the agents affected by this defect and may be more disruptive.
  • When using DB2, the vCenter Server service does not restart automatically after network connectivity is restored
    If you lose network connectivity to a vCenter Server system that is configured to use an IBM DB2 database, you will be unable to start the vCenter Server service after network connectivity is restored.

    Workaround:

    1. Close all existing connections from the vCenter Server machine to the IBM DB2 database using the Application List utility.
    2. Log in to the DB2 UDB database as dbadm, as the instance owner, or as the database owner.
    3. Run the following command to obtain information about the user you want to disconnect from the database: db2 list applications

      An output similar to the following appears:
      Auth Id   Application     Appl.       Application Id
                Name            Handle
      --------  --------------  ----------  --------------------------
      VPX       db2bp.exe       3428        *LOCAL.DB2.100225221240
    4. Note the application handle number and use it to run the following disconnect command:

      force application <application_handle_number>
  • Performance data older than one day is not available for some entities when vCenter Server is configured to use DB2
    Performance data older than one day is not available for some entities when vCenter Server is configured to use DB2.

    Note: The UTIL_HEAP_SZ parameter allocates memory. This parameter can be tuned to increase memory allocation to DB2. Reduce diaglevel to 3 to reduce diag.log size and excessive log generation. This allows DB2 to process jobs in the background. Refer to the following IBM Infocenter page for DB2 specific parameters.

    Workaround: If you are using DB2 9.5, upgrade to DB2 9.5 Fix Pack 5.

  •  Hot-plug operations fail after the swapfile is relocated
    Hot-plug operations will fail for powered-on virtual machines in a DRS cluster, or on a standalone host, with an error failed to resume destination; VM not found after the swap file location is changed.

    Workaround: Do one of the following:

    • Reboot the affected virtual machines to register the new swap file location with them, then perform the hot-plug operations.
    • Migrate the affected virtual machines using vMotion.
    • Suspend the affected virtual machines.
  • Accented and composite characters are not displayed in the index of French-language Help
    Accented and composite characters, such as Æ and Œ are not displayed in the indexes of French-language versions of the vSphere Client Help, DRS Troubleshooting Help, Overview Performance Charts Help, and Web Access Help.

    Workaround: None.

  • Failure when attempting to join a vCenter Server instance that is hosted on a system running Windows Server 2008 with User Account Control enabled with Linked Group
    If you are joining or isolating a Windows Server 2008 system that has User Account Control (UAC) to a Linked Mode group, the operation fails without an error message.

    Workaround: Perform the following steps:

    1. Turn off User Account Control (UAC) before joining the system to a Linked Mode group as follows:

      1. Open Windows Control Panel.
      2. Select Start > Setting > Control Panel > User Accounts.
      3. Select Turn User Account control on or off.
      4. Deselect User Account Control (UAC) to help protect your computer and click OK.
      5. Restart the machine.

    2. Start the Linked Mode configuration as follows:
      1. Select Start > All Programs > VMware > vCenter Server Linked Mode Configuration and click Next.
      2. Select Modify Linked-Mode configuration and click Next.
      3. Click Join this vCenter Server instance to an existing Linked-Mode group or another instance and click Next.
      4. Type the server name and LDAP port information and click Next.
      5. Click Finish.
      6. Click Continue and follow the installation prompts.

    3. Log in to one of the vCenter Servers and verify that the servers are linked together.

    4. After the vCenter Servers are linked, turn on UAC.
      1. Select Start > Settings > Control Panel > User Accounts.
      2. Select Turn User Account control on or off.
      3. Select User Account Control (UAC) to help protect your computer and click OK.
      4. Restart the machine.
  •  Datastore performance chart shows incorrect data
    If you open the Performance tab from the the vSphere Client Datastore inventory view, the tab shows four graphs. The titles of these graphs are not correct and should read as follows:

    • Max Latency per Host
    • Max Queue Depth per Host
    • Number of Reads per Host
    • Number of Writes per Host

    In some cases the graphs might not show all the hosts, which is a known problem.

    Workaround: To view the correct information for each host associated with a datastore, switch to the Host and Clusters inventory view, select the Performance tab, and look at the corresponding counter.

  • Upgrading vCenter Server that is running with Oracle 10g or Oracle 11g database might cause the vCenter Server to stop responding


    If vCenter Server that is running with Oracle 10g database or Oracle 11g database (version 10.2.0.4 to 11.2.01), is upgraded to vCenter Server 4.1 or later, vCenter Server stops responding with an error message similar to the following:
    Got exception: Arithmetic operation resulted in an overflow.
    This issue is caused by Oracle ODBC client bug 9793452.

    Workaround: None. To fix the issue, upgrade Oracle client. Contact Oracle support to acquire the patch.
  • vCenter Service Status displays error citing exception in locale detection
    When you log in to vCenter Server through vSphere Client and navigate to Administration > vCenter Service Status, the vCenter Service Status might display an Unexpected exception in locale detection, using default: [object Error]error message. Clicking OK for this message might result in a dialog box displaying the An error has occurred in the script on this page Internet Explorer script error. Clicking Yes in the dialog box results in a blank vCenter Service Status screen. If you right-click on the blank screen and select Refresh, vCenter Service Status appears correctly.
    Note: In some cases the Internet Explorer script error reappears even after you click Yes repeatedly, and the blank screen is not displayed. When this happens, stop the vSphere Client application in Task Manager, and log in again.
  • Connecting vSphere Client 4.0 or 4.1 to a Linked Mode vCenter Server fails and results in an error message
    If you put three or more vCenter Servers with mixed versions, such as 4.0 update with 4.1, into a Linked Mode group, then connecting vSphere Client 4.0 or 4.1 to the vCenter Server might fail. The following error message appears in vSphere Client:
    There are issues communicating with the following vCenter Server(s) xyz.servername.com: Failure to authenticate with the server

    Workaround: Use vSphere Client 4.1 Update 2 to connect to a vCenter Server 4.1 Update 2 system that is a part of the Linked Mode group to view and manage the inventories of all the vCenter Server systems that are linked.

Virtual Machine Management

  • Virtual machine clone operations might fails with the error: Invalid configuration for device '4'
    When cloning virtual machines, if the host running the virtual machine and the host that is selected to run the cloned virtual machine are on the same vNetwork Distributed Switch, vCenter Server might fail to perform the clone operation.
    The vpxa log files might contain messages similar to the following:
    vpxapi.VpxaService.createVm: vim.fault.InvalidDeviceSpec:
    Result:
    (vim.fault.InvalidDeviceSpec) {
    dynamicType = <unset>,
    faultCause = (vmodl.MethodFault) null,
    property = "virtualDeviceSpec.device.backing",
    deviceIndex = 4,
    msg = "Invalid configuration for device '4'.",
    }


    This issue occurs if the timeout value for dvPorts is changed from its default value in the vpxd.cfg file.

    Workaround: To resolve the issue, re-assign default timeout values to the dvPorts by removing the following parameter from the vpxd.cfg file:
    <vpxd><dvs><portReserveTimeout>Changed_Time_Value</portReserveTimeout></dvs></vpxd>
    Restart the VMware Virtual Center Server Service for the values to take affect.
  •  Migrating a powered-off or suspended ESX 3.x virtual machine with snapshots to another datastore might make the target virtual machine unusable
    When you attempt to migrate a powered-off or suspended ESX 3.x virtual machine with snapshots to another datastore, you might see the following warning message:

    This virtual machine has snapshots enabled. Under certain conditions, some virtual disk files might not copy automatically to the target datastore. You will be unable to power on this virtual machine until the remaining virtual disk files are copied manually from the source datastore. To learn more, search the VMware Knowledge Base for "migrating 3.x snapshots."

    If you have completed the migration of the virtual machine, you might see the following error message when you attempt to power on the virtual machine:
    File was not found

    Workaround: See KB 1020709.

VMotion and Storage VMotion

  • Virtual machine directory is not removed from the destination datastore when the advanced storage vMotion task is cancelled
    When you choose to migrate the hard disk file of a virtual machine to another datastore by using the advanced storage vMotion option and cancel the storage vMotion task before it is complete, the virtual machine directory remains on the destination datastore. The next time you choose to migrate the virtual machine's storage to the datastore, another directory with the virtual machine's name suffixed by _1 is created on the destination datastore.

    Workaround: None

VMware High Availability and Fault Tolerance

  • Custom VM Monitoring Settings are applied incorrectly to virtual machines if you sort the VirtualMachine column by clicking the heading
    If VM Monitoring is enabled on a VMware HA cluster and custom VM Monitoring settings are applied to the virtual machines, the virtual machines might not be assigned the values set for them if the Virtual Machine column is sorted.

    Workaround: Do not sort the VirtualMachine column before applying the custom VM monitoring settings.