VMware ESXi 5.5, Patch ESXi550-201406401-SG: Updates esx-base (2077360)
Release date: June 10, 2014
|Build||For build information, see KB 2077359.|
|Host Reboot Required||Yes|
|Virtual Machine Migration or Shutdown Required||Yes|
|PRs Fixed||1242103, 1256520|
|Related CVE numbers||CVE-2014-0224|
Summaries and Symptoms
This patch updates the esx-base VIB to resolve these issues:
- PR1242103: When you run ESXi 5.5 Update 1, the ESXi host intermittently loses connectivity to NFS storage and an All Paths Down (APD) condition to NFS volumes is observed. During the duration of the APD condition and after, the array still responds to ping and the netcat tests are also successful. There is no evidence to indicate a physical network or a NFS storage array issue.
Entries similar to the following are logged in the vobd.log file for volume named 12345678-abcdefg0 as an example:
YYYY-04-01T14:35:08.075Z: [APDCorrelator] 9414268686us: [esx.problem.storage.apd.start] Device or filesystem with identifier [12345678-abcdefg0] has entered the All Paths Down state.
YYYY-04-01T14:36:55.274Z: No correlator for vob.vmfs.nfs.server.disconnect
YYYY-04-01T14:36:55.274Z: [vmfsCorrelator] 9521467867us: [esx.problem.vmfs.nfs.server.disconnect] 192.168.1.1/NFS-DS1 12345678-abcdefg0-0000-000000000000 NFS-DS1
YYYY-04-01T14:37:28.081Z: [APDCorrelator] 9553899639us: [vob.storage.apd.timeout] Device or filesystem with identifier [12345678-abcdefg0] has entered the All Paths Down Timeout state after being in the All Paths Down state for 140 seconds. I/Os will now be fast failed.
- PR1256520: The OpenSSL library is updated to version openssl-1.0.1h to address CVE-2014-0224.
Patch Download and Installation
The typical way to apply patches to ESXi hosts is through the VMware Update Manager. For details, see the Installing and Administering VMware vSphere Update Manager.
ESXi hosts can be updated by manually downloading the patch ZIP file from the VMware download page and installing the VIB by using the esxcli software vib command. Additionally, the system can be updated using the image profile and the esxcli software profile command. For details, see the vSphere Command-Line Interface Concepts and Examples and the vSphere Upgrade Guide.
Note: This problem began in build number 1623887 and affected all subsequent builds.