VMware vCenter Server 5.5 Update 3f Release Notes

|

vCenter Server 5.5 Update 3f | 14  SEPTEMBER 2017 | Build 6516310

vCenter Server 5.5 Update 3f Installation Package | 14  SEPTEMBER 2017 | Build 6520252

vCenter Server Appliance 5.5 Update 3f | 14  SEPTEMBER 2017 | Build 6521191

Check for additions and updates to these release notes.

What's in the Release Notes

The release notes cover the following topics:

What's New

  • Update to the Oracle (Sun) JRE package. The JRE package is updated to version 1.7.0_141. VIMPatch can be used to update JRE without reinstalling vCenter products and vSphere Update Manager. For more information, see KB 2150845.

Earlier Releases of vCenter Server 5.5

Features and known issues of vCenter Server are described in the release notes for each release. Release notes for earlier releases of vCenter Server 5.5 are:

Internationalization

VMware vSphere 5.5 is available in the following languages:

  • English
  • French
  • German
  • Japanese
  • Korean
  • Simplified Chinese
  • Traditional Chinese

Compatibility and Installation

ESXi, vCenter Server, and vSphere Web Client Version Compatibility

The VMware Product Interoperability Matrix provides details about the compatibility of current and earlier versions of VMware vSphere components, including ESXi, VMware vCenter Server, the vSphere Web Client, and optional VMware products. Check the VMware Product Interoperability Matrix also for information about supported management and backup agents before you install ESXi or vCenter Server.

The vSphere Client and the vSphere Web Client are packaged on the vCenter Server ISO. You can install one or both clients by using the VMware vCenter™ Installer wizard.

vSphere Client Connections to Linked Mode Environments with vCenter Server 5.x

vCenter Server 5.5 can exist in Linked Mode only with other instances of vCenter Server 5.5.

Guest Operating System Customization Support

The Guest OS Customization Support Matrix provides details about the guest operating systems supported for customization.

Installation Notes for This Release

Read the  vSphere Installation and Setup documentation for guidance about installing and configuring vCenter Server.

Although the installations are straightforward, several subsequent configuration steps are essential. Read the following documentation:

Upgrades for This Release

For instructions about upgrading vCenter Server, see the vSphere Upgrade documentation.

For more information about the sequence in which vSphere environments need to be updated, see KB 2057795.

Open Source Components for VMware vSphere 5.5

The copyright statements and licenses applicable to the open source software components distributed in vSphere 5.5 are available at http://www.vmware.com/download/vsphere/open_source.html, on the Open Source tab. You can also download the source files for any GPL, LGPL, or other similar licenses that require the source code or modifications to source code to be made available for the most recent available release of vSphere.

Product Support Notices

  • vSphere Web Client.

    • Starting with vSphere 5.5 Update 2, Windows XP and Windows Vista are not supported as vSphere Client Operating System. You can find the complete list of operating system supported by vSphere Web Client in the VMware Compatibility Guide.
    • Because Linux platforms are no longer supported by Adobe Flash, vSphere Web Client is not supported on the Linux OS. Third party browsers that add support for Adobe Flash on the Linux desktop OS might continue to function.
  • VMware vCenter Server Appliance. In vSphere 5.5, the VMware vCenter Server Appliance meets high-governance compliance standards through the enforcement of the DISA Security Technical Information Guidelines (STIG). Before you deploy VMware vCenter Server Appliance, see the VMware Hardened Virtual Appliance Operations Guide for information about the new security deployment standards and to ensure successful operations.

  • vCenter Server database. vSphere 5.5 removes support for IBM DB2 as the vCenter Server database.

  • VMware Tools. Beginning with vSphere 5.5, all information about how to install and configure VMware Tools in vSphere is merged with the other vSphere documentation. For information about using VMware Tools in vSphere, see the vSphere documentation. Installing and Configuring VMware Tools is not relevant to vSphere 5.5 and later.

  • vSphere Data Protection. vSphere Data Protection 5.1 is not compatible with vSphere 5.5 because of a change in the way vSphere Web Client operates. vSphere Data Protection 5.1 users who upgrade to vSphere 5.5 must also update vSphere Data Protection to continue using vSphere Data Protection.

Resolved Issues

The resolved issues are grouped as follows.

Security Issues
  • Update to JRE package

    The Oracle (Sun) JRE package is updated to version 1.7.0_141.

  • Update to libxml library

    The vCenter Server service vmware-vpxd libxml2 library is updated to version 2.9.4.

  • Update to the OpenSSL library

    The OpenSSL library is updated to version openssl-1.0.1u.

  • vSphere Web Client creates a SerenityDB folder in the C: drive after an upgrade

    After you upgrade VMware vCenter Server from 5.5 Update 3a to 5.5 Update 3e and the vSphere Web Client starts, it creates a SerenityDB folder in the C: drive, which is the top level of the hard drive and poses a security compliance audit risk, while it normally sits under C:\ProgramData\VMware\vSphere Web Client\SerenityDB.

    This issue is resolved in this release.

Guest OS Issues
  • Virtual machine console window might show error message Directory: /console/ WEB-INF/ 0 bytes

    When you use the vSphere Web Client to open a virtual machine console window, an error message might show Directory: /console/ WEB-INF/ 0 bytes in shadowed red text.

    This issue is resolved in this release.

Miscellaneous Issues
  • You might see an error message Hardware status error: querySpec.metricId on the Host Summary page of the vSphere Web Client

    When the vSphere Web Client connects to a vCenter Server which is in Enhanced Linked Mode, and you select an ESXi host, on the Host Summary page you might see an error message Hardware status error: querySpec.metricId.

    This issue is resolved in this release.

  • vCenter Server 5.5 might stop responding, when a privileged user attempts to add a host to an incorrect folder through the vSphere Web Services API

    When you have the proper privileges and you use the vSphere API to add an ESXi host to the vCenter Server, but instead of the hostFolder you use the rootFolder, this might cause the vCenter Server 5.5 to stop responding.

    This issue is resolved in this release.

  • Vpxa service might fail

    During the NFC operation, the vpxa service might fail due to an intermittent network problem.

    This issue is resolved in this release.

  • VMware Client Integration Plug-In might not work as expected if you log in to the vSphere Web Client using Google Chrome 58 and 59, or Internet Explorer 10 and 11

    When you log in to the vSphere Web Client using Google Chrome 58, Google Chrome 59, Internet Explorer 10 or Internet Explorer 11 and perform tasks related to the Client Integration Plug-In (CIP), you might encounter issues listed here:

    • Export or import OVF files (.ovf) is not enabled.
    • Upload or download files to datastores is not enabled.
    • Windows Session Authentication (SSPI) login is not enabled.

    This issue is resolved in this release.

  • vCenter Server might fail with error while using the OptionManager

    The vCenter Server might fail with an error similar to vpxd Panic: Assert Failed: "0 == _refCount" @ d:/build/ob/bora-1378903/bora/vim/lib-vsan/vmacore/main/object.cpp:157 when you attempt to use the OptionManager in vCenter Server.

    This issue is resolved in this release.

Networking Issues
  • Unable to add a virtual machine to a distributed virtual switch dvPort group on which IP traffic qualifier filters and marking are enabled

    When an IP traffic qualifier filter is configured on a distributed virtual switch (DVS) dvPort group, the source IP prefix length fails to load from the database after a reboot of the vpxd service. This source IP prefix length load failure prevents a virtual machine to be added to a DVS dvPort group on which IP traffic qualifier filtering and marking are enabled.

    This issue is resolved in this release.

    NOTE: If you are already not able to add VMs into a dvPort group, you must delete all the IP traffic qualifier filters from the DVS dvPort group as a workaround.

  • Unable to remove or modify a Port Mirroring session due to a missing destination port

    When the configured destination port for the Distributed Switch Port Mirroring session no longer exists, you cannot remove or modify the Port Mirroring session. This issue might occur when the port group, containing the destination port is deleted prior to the Port Mirroring session being removed.

    When the deleted destination ports are configured in the Port Mirroring session, the fix displays the errors: The resource "N" is in use and Distributed Port Group port N is in use by Distributed Port Mirroring session 
    ​(where N is the port number).

    This issue is resolved in this release. 

  • The error message Failed to read header on stream appears in the hostd.log file

    The CIM provider is not gracefully closing its connections to hostd, causing the error message Failed to read header on stream to be written too many times to the hostd.log file and making noise in vRealize Log Insight.

    The problem is fixed with decreasing the error log message from error to verbose level. 

    This issue is resolved in this release.

Server Configuration Issues
  • vCenter Server might get disconnected during a host profile operation

    When you use a host profile in which the security subprofile is absent, this might cause the vpdx service to become unresponsive. As a result, the vSphere Web Client cannot establish a connection to the vCenter Server to finish the operation.

    This issue is resolved in this release.

  • Attempts to unregister or remove a virtual machine from an ESXi host with vSphere Web Client might fail with error message An error occurred while communicating with the remote host

    Attempts to unregister or remove a virtual machine from an ESXi host on a vCenter Server with vSphere Web Client might fail with error message An error occurred while communicating with the remote host and you might not be able to complete the task.

    This issue is resolved in this release.

Storage Issues
  • vSphere Web Client fails with error #1009 when user navigates to Storage Devices view

    When you navigate to an ESXi host > Manage > Storage > Storage Devices view, using the vSphere Web Client, the client might fail with error #1009 and prompt you to reload the page.

    This issue is resolved in this release.

vCenter Server, vSphere Web Client, and vSphere Client Issues
  • VMware vCenter Server might fail due to excessive memory consumption for serialization of VMware DRS dependent recommendations

    When VMware Distributed Resource Scheduler (DRS) generates recommendations, there might be dependent recommendations represented as Directed Acyclic Graphs and DRS attempts to serialize these dependent recommendations into an array. However, DRS does not check duplicates during this serialization, which may result in large memory consumption and cause vCenter Server to fail.

    This issue is resolved in this release.

Virtual Machine Management Issues
  • Generating Storage DRS recommendations might take too long

    vSphere Storage vMotion might stop working with enabled Storage DRS recommendations. As a result, you cannot migrate the virtual machine to the Storage DRS cluster. 

    This issue is resolved in this release.

Known Issues

The known issues are grouped as follows.

Miscellaneous Issues
  • VMware Client Integration Plug-In might not work as expected if you log in to the vSphere Web Client using Firefox 54

    When you log in to the vSphere Web Client using Firefox 54 and perform tasks related to Client Integration Plug-In, you might encounter issues listed here:

    • Export or import OVF files (.ovf) is not enabled.
    • Upload or download files to datastores is not enabled.
    • Windows Session Authentication (SSPI) login is not enabled.

     

    Workaround:
    To work around this issue, you must update the vmware-localhost certificate. Follow these steps:

    1. Backup the following files:

    • C:\ProgramData\VMware\CIP\csd\ssl\cert.der
    • C:\ProgramData\VMware\CIP\csd\ssl\cert.pem
    • C:\ProgramData\VMware\CIP\csd\ssl\server.pem 

    2. Add section [v3_req] with content subjectAltName = DNS:vmware-localhost, DNS:vmware-plugin at the end of the configuration file. You must add "vmware-plugin" in case both the Client Integration Plugin and the Enhanced Authentication Plugin are installed.

    3. Create a new Certificate Signing Request from an elevated Command Prompt, vmware-csd.exe --install from C:\Program Files (x86)\VMware\Client Integration Plug-in 6.0 or C:\Program Files\VMware\Client Integration Plug-in 6.0.

    4. Remove the vmware-localhost certificate from the Trusted Root Certification Authorities store for the local computer, and import the new one you created (C:\ProgramData\VMware\CIP\csd\ssl\cert.pem).

    5. Add the friendly name "VMware-CSD Cert" to the new vmware-localhost certificate.

    NOTE: As a workaround you can also use alternative browsers like the latest versions of Google Chrome or Internet Explorer.

  • Syslog of vCSA does not collect logs over ssl when VMware vCenter Server 5.0 or VMware vCenter Server 5.1 upgrade to VMware vCenter Server 5.5 Update 3f

    Syslog of the VMware vCenter Server Appliance (vCSA) does not collect logs over ssl when the ESXi server version is build 6480324 and you upgrade from VMware vCenter Server 5.0 or VMware vCenter Server 5.1 to VMware vCenter Server 5.5 Update 3f. This issue occurs due to a SSL handshake failure between the ESXi syslog client and the vCenter Server syslog collector, which is due to an Elliptic curve cryptography mismatch. TCP and UDP are not affected from this issue.

    Workaround: After you upgrade to VMware vCenter Server 5.5 Update 3f, you must:

    1. Backup the file /etc/syslog-ng/stunnel.conf.

    2. Edit the file to add the parameter curve = secp256k1 under the [syslog_ssl_tunnel] section.

    3. Restart the syslog services, using the commands service syslog-collector stop and service syslog-collector start

Networking Issues
  • Unable to remove or modify a Port Mirroring session due to a missing destination port

    When the configured destination port for the Distributed Switch Port Mirroring session no longer exists, you cannot remove or modify the Port Mirroring session. This issue might occur when the port group containing the port is deleted before the Port Mirroring Session is removed.

    Apply the following workaround in case you cannot remove or modify Port Mirroring sessions because the configured ports from the Port Mirroring sessions are already deleted from the vSphere Distributed Switch.

    Workaround:

    1. Take a good, working backup from the vCenter Server database.
    2. Stop the vCenter Server service.
    3. Locate the table called dbo.VPX_DVS_VSPAN_PORTS.
    4. Locate the row with the PORT_USE value of DestinationPort.
    5. Change the PORT_IDENTIFIER_VALUE to the number of a port that exists in the Distributed Switch.
    6. Once the value has been modified, restart the vCenter Server service.

    From the Networking view in the vSphere Client, you should now be able to successfully remove or modify the Port Mirroring session.