VMware ESX software has been tested and deployed in a variety of storage network environments. This guide describes the storage devices currently tested by VMware and its storage partners.
ESX, ESXi Embedded and ESXi Installable are equivalent products from a storage compatibility perspective. In this guide we only explicitly list ESX compatibility information. If a product is listed as supported for ESX, the product is also supported for ESXi Embedded and ESXi Installable corresponding versions.
Note: Boot from SAN (Fibre Channel or iSCSI) is not supported with ESXi.
If you are having a technical issue with 3rd party HW/SW and it is not found on this list, please refer to our 3rd Party HW/SW support policy at http://www.vmware.com/support/policies/ThirdParty.html.
VMware works closely with each of its OEMs to drive towards mutual support of ESX at the time of announcement. Due to different product release cycles, levels of testing, and OEM agreements, not all OEM devices will be supported at the general availability date of a new version of ESX. We recommend contacting the OEM vendor for the best information on when their device is planned to be certified with Virtual Infrastructure.
For further details about array firmware, storage product configurations and best practices, please contact the storage vendor.
NOTE: The use of an external enclosure, or JBOD connected to a supported SAS/SCSI controller in a supported server is supported, as long as there is no disk sharing among multiple servers or SAS/SCSI cards.
This SAN HCL lists storage devices starting with ESX 3.0.x onwards. It does not include older ESX 2.5.x or earlier versions listed in http://www.vmware.com/pdf/esx_SAN_guide.pdf.
Please contact your storage vendors if you do not find devices certified in the SAN HCL list.
Microsoft Windows Failover Cluster with ESX
Windows Clustering refers Cluster Services in Windows operating systems in a shared disk configuration between two virtual machines or a virtual machine and a physical system. Such clustering is certified only with a subset of arrays listed in this guide.
Previously Failover Clustering was called MSCS.
Before installing VMware ESX software with your storage array, please examine the lists on the following pages to find out whether your array and configuration are supported. Please refer to your storage vendor for more information and configuration details.
Windows Failover Cluster support with ESX 3.0.x
Below table shows the supported list of Windows OS, FC HBA speed and drivers.
Windows Failover Cluster support with ESX 3.5.x
MSCS/Failover cluster is supported with ESX 3.5 with both 32 bit and 64 bit VMs running
- Windows 2000 SP4 and
- Windows 2003 (x86 and x64) up to and including SP2
Only 4Gb Emulex and Qlogic FC HBAs are supported.
Windows Failover Cluster support with ESX 4.0
With native multipathing (NMP), clustering is not supported when the path policy is set to round robin. Please see "Setup for Failover Clustering and Microsoft Cluster Services" for limitations on MSCS support with PSA.
1. Virtual SCSI adapter and Windows OS supported
- LSI Logic Parallel for Windows Server 2000 SP4
- LSI Logic Parallel for Windows Server 2003 RTM (x86 and x64) up to and including SP2
- LSI Logic SAS for Windows Server 2008 (x86 and x64) up to SP1
2. Only 4Gb Qlogic and Emulex Fibre Channel HBAs are supported.
The driver versions supported are as follows:
qla2xxx-400.821.kl.38vmw
qla4xxx-400.5.01.00.vml
lpfc820-400.2.0.30.49vmw
PSA Plug-ins with ESX 4.x
Array operating modes and path selection behavior are supported through the Pluggable Storage Architecture (PSA) framework. Storage partners may (1) provide their own Multi-Pathing Plug-ins (MPP), (2) use Storage Array Type Plug-ins (SATP) and Path Selection Plug-ins (PSP) offered by VMware 's Native Multi-pathing (NMP) or (3) provide their own SATP and PSP.
The plug-ins supported with a storage array are noted in the 'Mode' and 'Path Policy' columns of the 'Model/Release Details' page. The path policy of VMW_PSP_RR may also be supported but not be necessarily listed in the 'Mode' and 'Path Policy' columns of the 'Model/Release Details' page. Storage partner may recommend VMW_PSP_RR for path failover policy for certain storage array models. If desired, contact the storage array manufacture for recommendation and instruction to set VMW_PSP_RR appropriately.
With native multipathing (NMP), clustering is not supported when the path policy is set to round robin. Please see "Setup for Failover Clustering and Microsoft Cluster Services" for limitations on MSCS support with PSA.
Fibre Channel SANs
For Fibre Channel SANs, if listed, VMware supports the following configuration, unless footnoted otherwise:
* Basic Connectivity - The ability of ESX hosts to recognize and interoperate with the storage array. This configuration does not allow for multipathing or any type of failover.
* Multipathing - The ability of ESX hosts to handle multiple paths to the same storage device.
* HBA Failover - In this configuration, the ESX host is equipped with multiple HBAs connecting to one or more SAN switches. The server is robust to HBA and switch failure only.
* Storage Port Failover - In this configuration, the ESX host is attached to multiple storage ports and is robust to storage port failures.
* Boot from SAN - In this configuration, the ESX host boots from a LUN stored on the SAN rather than a local disk.
* Direct Connect - In this configuration, the ESX host is directly connected to the array (that is, no switch between HBA and the array). Windows Failover Clustering is not supported in this configuration.
NOTE: Windows Failover Clustering (MSCS) support applies to Windows 2000 SP4, Windows 2003 RTM, SP 1, R2 and SP 2. For ESX version requirements for these operating systems in cluster environment, please refer to http://kb.vmware.com/kb/2021. Windows Failover Clustering is supported only with a limited set of HBAs; please refer to the I/O Compatibility Guide (http://www.vmware.com/pdf/vi3_io_guide.pdf) for the list of HBAs not supported with Windows Failover Clustering.
NOTE: MSCS is not supported, unless footnoted.
NOTE: MSCS is not supported for Direct Connect.
NOTE: Only footnoted storage arrays are supported with Brocade 415 and 425 HBAs.
NOTE: Unless otherwise footnoted, all fibre channel arrays are supported with both 2Gb and 4Gb FC HBAs on ESX
NOTE: For ESX 3.5 U2 onwards unless otherwise footnoted, all fibre channel arrays are supported with 2Gb, 4Gb and 8Gb FC HBAs on ESX.
NOTE: For devices with external SAN storage support, please refer to Storage Virtualization Device (SVD).
NOTE: Unless otherwise noted, all fibre channel storage products are supported in a boot from SAN configuration.
NOTE: End-to-end connectivity at 8Gbps FC speed is supported with 8G FC arrays only if the product details has prefix of "8G FC" or is footnoted. Otherwise support for 8G FC arrays is limited to up to 4Gbps speed only.
Storage Virtualization Device (SVD)
VMware supports Storage Virtualization Devices (SVD) with ESX 3.0.2 or later and ESX 4.0.
* Gateways are included as part of SVDs.
* Backend storage arrays must be listed on both the ESX Storage/SAN Compatibility Guide and the SVD Vendor supported list. Back-end array and the SVD are both required to be certified with the same ESX release.
* Do not share the same LUN of the backend storage array between SVD and any other host.
* Only devices that are listed with Array Type SVD are allowed to connect to external Fibre Channel SAN storages.
* Only Fibre Channel protocol from SVD device to ESX is supported.
Storage Arrays supported with FCoE CNAs
Fibre Channel Over Ethernet (FCoE) Converged Network Adapters (CNAs) can be concurrently connected to Fibre Channel Fabrics and Ethernet networks, through FCoE capable switches. Only the Fibre Channel arrays that will be listed with this array type are certified to work and supported with FCoE CNAs. CNAs are not yet supported to connect with iSCSI and NFS storage arrays.
Network Attached Storage
The following Linux distributions are supported network attached storages
ESX 3.x
* Red Hat Enterprise Linux 5 NFS Server (Update 2).
* Red Hat Enterprise Linux 3 NFS Server (Update 5).
* Fedora Core 4 NFS Server (2.6.12-1.1456_FC4.9550smp).
* Fedora Core 6 NFS Server (2.6.18-1.2798.fc6 #1 SMP) for ESX 3.5 only.
ESX 4.0
Fedora Core 8 NFS Server
NOTE: Windows Clustering (MSCS) is not supported with NAS.
iSCSI
VMware supports connections to iSCSI arrays using either the software initiator in the kernel or a hardware initiator (iSCSI HBA). Please refer to the I/O Compatibility Guide for a list of hardware initiators that can be used with ESX.
The following maximums are in place when using iSCSI arrays with ESX hosts:
* Number of HBAs - software (1); hardware (1 dual port) or (2 single port)
* Maximum number of targets - both software and hardware initiator (64)
* Number of LUNs both software and hardware initiator (254)
* Number of paths to storage - software (4); hardware (8)
For iSCSI storage with the software initiator over a supported NIC, if listed, VMware supports the following configuration, unless footnoted otherwise:
* iSCSI Base Connectivity - The ability of an ESX host to recognize the target and interoperate with it.
* SP failover - In this configuration the ESX host is attached to multiple ports and is robust to storage port failover
* NIC failover for software initiator - If the Ethernet adapters are teamed and one fails, the other one takes over. Both adapters must be connected to the same physical switch and be on the same subnet (both NICs and iSCSI storage ports).
For iSCSI storage with hardware initiators, if listed, VMware supports the following configuration, unless footnoted otherwise:
* iSCSI Base Connectivity - The ability of an ESX host to recognize the target over an iSCSI HBA and interoperate with it.
* SP failover - In this configuration, ESX host is attached to multiple ports over an iSCSI HBA and is robust to storage port failover.
* Boot from iSCSI - In this configuration, ESX hosts boot from the target iSCSI array rather than from a local disk.
* iSCSI hardware initiator failover - The ESX host is equipped with multiple hardware initiators and is robust to hardware initiator failover.
NOTE: Windows Clustering is not supported with iSCSI.
NOTE: Software initiated iSCSI is supported fully in ESX 3.0 and later releases. Hardware initiated iSCSI is supported in experimental mode only in ESX 3.0. It is supported fully in ESX 3.0.1 and later with iSCSI arrays that have been qualified/certified for use with the hardware initiators.
SAS Arrays
For SAS Arrays, if listed, VMware supports the following configuration, unless footnoted otherwise:
* Basic Connectivity - The ability of ESX hosts to recognize and interoperate with the storage array. This configuration does not allow for multipathing, any type of failover, or sharing of LUNs between multiple hosts.
* Direct Connect - In this configuration, the ESX host is directly connected to the array (that is, no switch between HBA and the array). Windows Clustering is not supported in this configuration.
* LUN sharing - The ability of multiple ESX hosts to share the same LUN.
* Multipathing - The ability of ESX hosts to handle multiple paths to the same storage device.
* HBA Failover - In this configuration, the ESX host is equipped with multiple HBAs connecting directly to the array. The server is robust to HBA failure only.
* Storage Port Failover - In this configuration, the ESX host is attached to multiple storage ports on the same array and is robust to storage port failures.
* Boot from SAS - SAS boot is supported unless explicitly stated in a footnote for a specific array.
The detailed lists show actual vendor devices that are either physically tested or are similar to the devices tested by VMware or VMware partners. VMware provides support only for the devices that are listed in this document
Click on the 'Model' for details.