ESXi 5.0 boot delays when configured for Software iSCSI (2007108)
This issue occurs because ESXi 5.0 attempts to connect to all configured or known targets from all configured software iSCSI portals. If a connection fails, ESXi 5.0 retries the connection 9 times. This can lead to a lengthy iSCSI discovery process, which increases the amount of time it takes to boot an ESXi 5.0 host.
- VMware ESXi 5.0, Patch Release ESXi500-201111001 (2008017)
- VMware ESXi 5.0 Patch ESXi500-201111401-BG: Updates esx-base (2008018)
- When you are upgrading to ESXi 5.0, there are two ISO files: one for systems without software iSCSI configured and one for systems with software iSCSI configured. If you have configured software iSCSI devices, or if you think you might use software iSCSI in the future, ensure that you choose the ISO image for systems with software iSCSI.
- This express patch ISO contains all of the fixes in ESXi 5.0 Patch 01, plus the software iSCSI fix.
VMware is delivering an ISO file for this patch release due to the nature of this issue. This is not common practice and is only done in special circumstances.
Note: The ISO containing ESXi 5.0 Patch 01 is only available to licensed customers, and is not available for download without an entitlement. However, non-licensed customers can download Patch 01 to upgrade an existing version of ESXi 5.0 to resolve this issue.
To list the current number and configuration of an ESXi host's network portals, run this command:
esxcli iscsi networkportal list
The output is similar to this:
MAC Address: xx:xx:xx:xx:xx:xx
MAC Address Valid: true
IPv4 Subnet Mask: 255.255.255.0
Vlan Supported: true
Vlan ID: 10
Reserved Ports: 63488~65536
TCP Checksum: false
Link Up: true
Current Speed: 10000
Rx Packets: 656558
Tx Packets: 111264
NIC Driver: ixgbe
NIC Driver Version: 184.108.40.206.2-10vmw-NAPI
NIC Firmware Version: 0.9-3
Compliant Status: compliant
VswitchUuid: 26 46 30 50 c0 cf df 1e-52 ef ab d7 a2 ab 96 f9
Path Status: active
Note: This is an example of one network portal (HBA34).
To list currently running targets, run this command:
vmkiscsi-tool -T vmhba##