- vSAN = VMware’s Software Defined Storage Solution formerly known as Virtual SAN or VSAN. Now the only acceptible name is “vSAN” with the little “v”.
- SPBM = Storage Policy Based Management
- VASA = vSphere API’s for Storage Awareness
- VVol = Virtual Volume
- PE = Protocol Endpoint
- VAAI = vSphere API’s for Array Integration
- VAIO Filtering = vSphere API’s for IO Filtering
- VR = vSphere Replication
- SRM = Site Recovery Manager
- VDP = vSphere Data Protection
- vFRC = vSphere Flash Read Cache
- VSA = vSphere Storage Appliance (end of life)
- VMFS = Virtual Machine File System
- SvMotion = Storage vMotion
- XvMotion – Across Host, Cluster, vCenter vMotion (without shared storage)
- SDRS = Storage Distributed Resource Scheduler
- SIOC = Storage Input Output Control
- MPIO = Multi Path Input Output
Tag: VAAI
VMware vSphere 5 VAAI support for EMC CX4
In vSphere 4 the VAAI test harness only included functionality. So if a storage array supported the VAAI primitives and passed VMware’s functionality test then VAAI was listed as a feature of the supported array in the Storage/SAN Compatibility Guide. vSphere 5 added a VAAI performance test. This is due to some of the issues it discovered when it released their Thin Provision Reclaim VAAI feature in vSphere 5.
EMC’s CX4 did not pass VMware’s performance test harness for XCOPY/Block Zero. Atomic Test and Set (ATS) Hardware Offloading did pass the performance testing but since the XCOPY/Block Zero didn’t pass then VMware considers all VAAI as unsupported on the CX4.
Chad Sakac (Virtual Geek) lays it all out at the end of the PPT and recording in the post VNX engineering update, and CX4/VAAI vSphere scoop. In that he proposes the following EMC support model:
- Running with VAAI block acceleration on a CX4 with ESX5 is considered an unsupported configuration by VMware.
- EMC will support the use of VAAI block under ESX5 with CX4 arrays.
- If customers running this configuration have an issue, EMC recommends they turn off the VAAI features. If the condition persists, VMware will accept the case. If the problem is no longer occurring, contact EMC for support.
vSphere 4 did not have a performance test harness. So if they were happily running vSphere 4 with VAAI enabled then they can upgrade to vSphere 5, leave VAAI enabled, and likely enjoy the same experience they have now for their CX4 on vSphere 4.
Validate that the VAAI block primitives are enabled in vSphere
The hardware offloading and acceleration benefits of VAAI in vSphere are well documented. Check here for one of many explanations. I am frequently asked by customers how to know if VAAI is enabled and where to check.
Here are the instructions to validate that the VAAI block primitives are enabled in vSphere.
Verify Hardware Assisted (Accelerated) Locking is enabled
- From the vSphere Client click Home > Inventory > Hosts and Clusters
- Select a host, click the Configuration tab, and select Advanced Settings
- Select VMFS3 and note that the VMFS3.HardwareAcceleratedLocking parameter is set to 1
Verify Block Zeroing (Hardware Accelerated Zero) is enabled
- From the vSphere Client click Home > Inventory > Hosts and Clusters
- Select a host, click the Configuration tab, and select Advanced Settings
- Select DataMover and note that the DataMover.HardwareAcceleratedInit parameter is set to 1
Verify Hardware Accelerated Copy is enabled
- From the vSphere Client click Home > Inventory > Hosts and Clusters
- Select a host, click the Configuration tab, and select Advanced Settings
- Select DataMover and note that the DataMover.HardwareAcceleratedMove parameter is set to 1
Live Virtually 