Release Notes

Dell systems management monitoring applications fail to

authenticate to an ESXi host after a few days of use

Description: Dell OpenManage Software Administrator and OpenManage Essentials are not

responsive after running in the ESXi environment for several days.

Applies to: ESXi 5.x

Solution: The failure is due to insufficient memory allocated for the process and a memory

leak in the WSMan daemon in ESXi. Restart the WSMan service. For more

information, refer to the VMware Knowledge Base article 2043464.

VMware vCenter service stops responding when fibre

channel LUN is attached to ESXi host via software FCoE

adapter

Description: When a Fibre Channel (FC) Logical Unit Number (LUN) is attached to the ESXi host

via software Fibre Channel over Ethernet (FCoE) adapter, VMware vCenter vpxa

service stops responding for that ESXi host. The failure occurs due to the Virtual

LAN (VLAN) ID used in the fabric and also when the connection to the vCenter is

made after software FCoE configuration via vSphere client.

Applies to: ESXi 5.x

Solution: To resolve this issue, do not use a VLAN ID in the range of 32xn -1 where n=1, 2,...

For more information, refer to the VMware Knowledge Base article 2033385..

Unable to install and configure VMware vShield on Dell

customized ESXi image

Description: Unable to install and configure VMware vShield on Dell customized ESXi image.

The vShield vSphere Installation Bundle (VIB) fails to install with the following error

message: ERROR: DependencyError: File path of '/VIB/postinst' is

claimed by multiple non-overlay VIBs.

Applies to: ESXi 5.x

Solution: For the earlier version of ESXi images, complete the following tasks to resolve this

issue:

1. Download the latest ESXi image ima-qla4xxx (file name :

qla4xxx-624.01.43-771651.zip) from vmware.com and upgrade the driver

using the following command: esxcli software vib update -d <

absolute path to offline vib>qla4xxx-624.01.43-

offline_bundle-771651.zip

2. After driver installation, restart the system and start the vShield installation.

NOTE: This issue is fixed in the latest Dell customized ESXi image.