- #MD3220I VMWARE 6.0 IO CHARACTERISTICS TYPE SOFTWARE#
- #MD3220I VMWARE 6.0 IO CHARACTERISTICS TYPE WINDOWS#
#MD3220I VMWARE 6.0 IO CHARACTERISTICS TYPE WINDOWS#
Windows Failover Cluster support with ESX 3.0.xīelow table shows the supported list of Windows OS, FC HBA speed and drivers. Please refer to your storage vendor for more information and configuration details.
#MD3220I VMWARE 6.0 IO CHARACTERISTICS TYPE SOFTWARE#
Previously Failover Clustering was called MSCS.īefore 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. Such clustering is certified only with a subset of arrays listed in this guide. 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. Microsoft Windows Failover Cluster with ESX Please contact your storage vendors if you do not find devices certified in the SAN HCL list. It does not include older ESX 2.5.x or earlier versions listed in. This SAN HCL lists storage devices starting with ESX 3.0.x onwards. 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. We recommend contacting the OEM vendor for the best information on when their device is planned to be certified with Virtual Infrastructure.įor further details about array firmware, storage product configurations and best practices, please contact the storage vendor. 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. VMware works closely with each of its OEMs to drive towards mutual support of ESX at the time of announcement. 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. Note: Boot from SAN (Fibre Channel, Fibre Channel over Ethernet, SAS, or iSCSI) is not supported with ESXi version 4.0 and earlier. If a product is listed as supported for ESX, the product is also supported for ESXi Embedded and ESXi Installable corresponding versions. In this guide we only explicitly list ESX compatibility information. This guide describes the storage devices currently tested by VMware and its storage partners.ĮSX, ESXi Embedded and ESXi Installable are equivalent products from a storage compatibility perspective. When VASA provider(VP) is distributed in a package along with other non-VP components, VMware will only assist with triaging customer issues that are due to a failure in the VP-vSphere API.VMware ESX software has been tested and deployed in a variety of storage network environments. Please refer to the Hardware Compatibility List for all partner related VASA providers. Storage DRS, another new vSphere 5.0 feature, includes recommendations from VASA providers in its load balancing logic and also monitors for Thin Provisioning alarm status which avoids moving VMs to datastores that are in danger of running out of space on the backing storage.
In addition to capability discovery, VASA also offers capacity and health monitoring. One of the cool features of VASA is that it lends itself to the creation of VM Storage Profiles (aka Profile Driven Storage), another new feature of vSphere 5.0. This attribute can take many forms as we are leaving this format decision to the storage vendors. In this first release of the VASA framework, vendor providers will surface a single 'attribute' per LUN from the storage array to vCenter server.
Admins can now see storage array capabilities from the vSphere client, giving them a single window into both the virtualization & storage infrastructures. storage array informs the vendor provider of capabilities & then the vendor provider informs vCenter.
For the first time VMware has an end to end story, i.e. VASA may also provide information about storage health status, configuration info & capacity. Vendor providers retrieve the storage capabilities from the array and pass these onto vCenter, which in turn can display these capabilities in the UI. Our storage array partners are creating plugins called vendor providers, which is the integration 'glue' that sits between vCenter and the storage array. VASA can display the features of the physical storage devices, allowing vSphere administrators insight into storage capabilities. VSphere Storage APIs for Storage Awareness, commonly referred to as VASA, is a set of APIs that permits storage arrays to integrate with vCenter for management functionality.