VMware HA and vMotion with stretched IBM System Storage SAN Volume Controller Cluster (2000948)
Disclaimer: The partner products referenced in this article are hardware devices that are developed and supported by stated partners. Use of these products are also governed by the end user license agreements of the partners. You must obtain the application, support, and licensing for using these products from the partners. For more information, see Support Information.
Description of Stretched SAN Volume Controller cluster:
Supported use cases
- A stretched SAN Volume Controller cluster presenting an accessible VMware VMFS volume to vSphere hosts at two separate data center locations separated by a distance of up to 10 kilometers.
- Single stretched vSphere cluster leveraging VMware HA and DRS functions with hosts at two separate data center locations separated by a distance of up to 10 kilometers.
- vMotion between vSphere hosts at two separate data center locations separated by a distance of up to 10 kilometres (as per IBM recommendations for SVC clusters with longwave SFPs)
- Automatic HA fail over of virtual machines between data centers due to server, storage, or site failure.
This table outlines the tested and supported failure scenarios when using a stretched SAN Volume Controller cluster and VMware vSphere.
SAN Volume Controller Behavior
VMware HA Impact
Path Failure – SAN Volume Controller Back End Port
Path Failure – SAN Volume Controller Front End Port
Active SAN Volume Controller Quorum Disk Failure
Loss of storage subsystem
SAN Volume Controller Node Failure
vSphere Host Failure
vSphere Host Isolation
vSphere Cluster Failure
Complete Site Failure
- VMware vCenter server must be able to connect to vSphere hosts at both locations.
- An IP network with a minimum bandwidth of 622 Mbps for vSphere hosts participating in vMotion.
- Maximum latency of 5 milliseconds (ms) between hosts participating in vMotion.
- Source and destination vSphere hosts must have a network interface on the same IP subnet and broadcast domain.
- The same IP network on which the virtual machines reside must be accessible to vSphere hosts at both data center locations.
- Datastores on which the virtual machine boot drives must be accessible to vSphere hosts at both data center locations.
- The maximum number of vSphere hosts in a HA-enabled cluster must not exceed eight (8), with four (4) hosts residing at each site.
- IBM SAN Volume Controller cluster running software code 5.1 or later, and configured in a supported hardware configuration as outlined in the IBM System Storage SAN Volume Controller V6.1.0 Software Installation and Configuration Guide.
How the process works
- Provide VMware with all of your entitlement details with IBM (so that VMware can engage IBM via Technical Support Alliances; or
- File a Support Request with IBM directly and provide VMware with all relevant details, including the Support Request number and the appropriate contact information for IBM's support personnel.
- If an issue is encountered on a Failed Scenario that is not mentioned in this article under the Tested Scenarios section, both VMware and IBM will apply their best efforts to help the customer. However, a supported resolution cannot be guaranteed by either VMware or IBM.
Examples of a failed scenario include, but are not limited to:
- When two or more of the aforementioned scenarios occur at the same time.
- When a network interface goes down or causes latency to be higher than five milliseconds during a vMotion operation.
Caution: This article only applies to the vSphere 4.1 release. Consult the VMware vSphere 5 vMSC program for future configuration offerings and support.