Home > Storage > PowerMax and VMAX > Storage Admin > Dell PowerMax and VMware vSphere Configuration Guide > Optimizing for interoperability
The PowerMax supports VMware Virtual Volumes (vVols). vVols is an integration and management framework (known as the vVol framework) that moves management from the datastore to the virtual machine. vVols virtualize storage and enable a more efficient operational model that is optimized for virtualized environments and centered on the application instead of the infrastructure. vVols map virtual disks, configuration files, clones, and snapshots, directly to virtual volume objects on a storage system. This mapping allows VMware to offload more storage operations to the array, such as VM snapshots.
vVols virtualize SAN devices by abstracting physical hardware resources into logical pools of storage that are called Storage Containers which replace traditional storage volumes. These containers are created on the PowerMax. They are assigned storage capabilities which can be all, or a subset, of the SLs the particular PowerMax array supports. These storage containers are presented to the vCenter when a VASA Provider is registered. The VASA Provider runs on the storage side. It integrates with vSphere Storage Monitoring Service (SMS) and ESXi vvold service to manage all aspects of the storage in relation to vVols. All communication between VMware and the VASA Provider is out of band.
From the presented storage containers, the VMware Admin creates vVol datastores through the wizard, like a traditional datastore. A vVol datastore has a one-to-one relationship with a storage container and is its logical representation on the ESXi host. A vVol datastore holds VMs and can be browsed like any datastore. Each vVol datastore then inherits the capabilities of the container. Examples include SLs - Bronze, Silver, and so on. The VMware Admin creates Storage Policies that are mapped to these capabilities. When a VM is deployed, the user selects the pertinent capability and is presented with compatible vVol datastores in which to deploy the VM.
Unlike traditional devices, ESXi has no direct SCSI visibility to vVols on the PowerMax. Instead, ESXi hosts use a front-end access point that is called a Protocol Endpoint (PE). A Protocol Endpoint is a special device that is created on the PowerMax and mapped and masked to the ESXi hosts. Each ESXi host requires a single, unique PE. The ESXi host uses the PE to communicate with the volumes and the disk files the vVols encapsulate. By using PEs, ESXi establishes data paths from the virtual machines (VM) to the virtual volumes through binding.
Note: Boot from SAN is not supported.
vVols simplify the delivery of storage service levels to individual applications by providing finer control of hardware resources. Also, they enable the use of native array-based data services such as SnapVX at the VM level. vVols present the VMware Admin a granularity of control over VMs on shared storage that cannot be achieved with traditional architecture due ESXi server device limitations. PowerMax supports up to 64k vVols on a PowerMax system. As each vVol uses a host available address, each vVol counts toward the total number of devices on the array.
Note: The PowerMax can support up to 64k total devices depending on the configuration (for example, number of engines). Because of supporting devices such as PEs, the number of vVols would, by necessity, be less than 64k.
vVols are not covered in detail in this guide, as two extensive white papers exist which cover configuration and best practices: