Intel Xeon 5400 or 5200 Series Processors (CPUID Family 6, Model 23, steppings 6 and 10); LSI SAS IR controller; EQL array
Affected Software
QLogic driver; vmkernel iSCSI Driver
Related CVE numbers
N/A
Solution
Summaries and Symptoms
This patch fixes the following issues:
Fixes an issue where the Secondary VM starts and runs for a few seconds and then fails, which causes the following to occur:
The FT Status of the Primary VM is listed as Not Protected.
The reason for the preceding Not Protected FT status is listed as Need Secondary VM.
This issue occurs when the Primary or Secondary VM for FT is hosted on a machine with mixed steppings of Intel Xeon 5400 or 5200 Series Processors (CPUID Family 6, Model 23, steppings 6 and 10).
Fixes an issue where the esx.conf file can get truncated in certain situations when the vmkernel interface is configured as a DHCP client.
Fixes a memory leak issue with Openwsman in ESX/ESXi.
Fixes an issue where Qlogic driver waits for all I/Os to complete on a target during a LUN_RESET.
Fixes an issue where operations like Add or Clear of RAID configuration using storelib might fail in a machine with a LSI SAS IR controller.
Fixes an issue where SNMPWalk does not retrieve the latest virtual machine device table.
Fixes an issue where the esxupdate command might not preserve bulletin information in the esxupdate database. The affected bulletin (or bulletins) do not appear in the output of the esxupdate query command. This problem occurs after using the esxupdate stage command on a bulletin that has previously been installed.
Fixes an issue where the esxupdate query command displays an incorrect timestamp for previously installed bulletins.
Fixes an issue where the iSCSI initiator does not retry to connect to a target when it receives a service unavailable message while attempting to connect. Affected iSCSI targets will then be unavailable to the host until the connection is manually reestablished. This can occur if the target is temporarily unavailable and may be observed during a disk array controller upgrade or failover
Deployment Considerations
None beyond the required patch bundles and reboot information listed in the table, above.
