Configuring VMware Virtual Volumes (VVols) on HP 3PAR StoreServ
Article ID: 319539
Updated On:
Products
VMware vSphere ESXi
Issue/Introduction
This article provides information on configuring VMware Virtual Volumes (VVols) on HP 3PAR StoreServ.
Environment
VMware vSphere ESXi 6.0
Resolution
Virtualization has led to a major transformation in the data center over the past ten years; however, the benefits of virtualization could be amplified through more granular control of applications and tighter alignment with the software defined data center (SDDC). The challenge with server virtualization today is the disconnect between what a hypervisor wants to control, a specific virtual machine, and what storage systems today control, which is an entire LUN or datastore that usually contains many virtual machines.
In response to this disconnect, VMware and key storage vendors like HP have designed and developed a new storage architecture for VMware vSphere. VMware's new storage architecture, called VMware Virtual Volumes (VVols), is designed to provide simplified storage management and more-granular virtual machine control.
HP has partnered with VMware for over four years to define, develop, and test VVol. HP 3PAR StoreServ Storage was selected as the Fibre Channel (FC) reference platform for VMware’s engineering team. Through that partnership, HP 3PAR StoreServ Storage provides a tightly integrated experience that does not require an additional plug-in or software piece to enable VVol and to support VMware’s VASA 2.0 specification. HP 3PAR delivers unique capabilities, like ASIC-based zero detect for space reclamation, which can be assigned on a per-virtual machine basis through VMware’s Storage Policy Based Management (SPBM).
VVol also eliminate the need to provision large datastores; storage provisioning now happens automatically through the integration on a per-virtual machine basis. Each virtual machine, and specifically each part of a virtual machine, is assigned its own unique VVol, which is equivalent to a storage LUN. With the tight integration with HP 3PAR StoreServ Storage, customers will be able to deploy VVol, in parallel with VMware’s Virtual Machine File System (VMFS) where necessary, with confidence.
Note: If you run into any issues with the HP/3PAR Virtual Volumes (VVols), ensure that the HP 3PAR OS 3.2.1 MU2 Patch 12 is installed. For more information, see the HP 3PAR OS 3.2.1 MU2 Patch 12 Release Notes.
In response to this disconnect, VMware and key storage vendors like HP have designed and developed a new storage architecture for VMware vSphere. VMware's new storage architecture, called VMware Virtual Volumes (VVols), is designed to provide simplified storage management and more-granular virtual machine control.
HP has partnered with VMware for over four years to define, develop, and test VVol. HP 3PAR StoreServ Storage was selected as the Fibre Channel (FC) reference platform for VMware’s engineering team. Through that partnership, HP 3PAR StoreServ Storage provides a tightly integrated experience that does not require an additional plug-in or software piece to enable VVol and to support VMware’s VASA 2.0 specification. HP 3PAR delivers unique capabilities, like ASIC-based zero detect for space reclamation, which can be assigned on a per-virtual machine basis through VMware’s Storage Policy Based Management (SPBM).
VVol also eliminate the need to provision large datastores; storage provisioning now happens automatically through the integration on a per-virtual machine basis. Each virtual machine, and specifically each part of a virtual machine, is assigned its own unique VVol, which is equivalent to a storage LUN. With the tight integration with HP 3PAR StoreServ Storage, customers will be able to deploy VVol, in parallel with VMware’s Virtual Machine File System (VMFS) where necessary, with confidence.
Note: If you run into any issues with the HP/3PAR Virtual Volumes (VVols), ensure that the HP 3PAR OS 3.2.1 MU2 Patch 12 is installed. For more information, see the HP 3PAR OS 3.2.1 MU2 Patch 12 Release Notes.
Additional Information
You can verify the installation of Patch 12 from an interactive Command Line Interface (CLI) session.
To verify the installation of Patch 12, run this command on the HP 3PAR Management Console:
cli% showversion -a -b
For example:
cli% showversion -a -b
Release version 3.2.1.200 (MU2)
Patches: P12
Component Name Version
CLI Server 3.2.1.200 (MU2)
CLI Client 3.2.1.200
System Manager 3.2.1.200 (MU2)
Kernel 3.2.1.200 (MU2)
TPD Kernel Code 3.2.1.200 (MU2)
CIM Server 3.2.1.200 (MU2)
.
.
.
VASA Provider 2.1.4 (P12)
To verify the installation of Patch 12, run this command on the HP 3PAR Management Console:
cli% showversion -a -b
For example:
cli% showversion -a -b
Release version 3.2.1.200 (MU2)
Patches: P12
Component Name Version
CLI Server 3.2.1.200 (MU2)
CLI Client 3.2.1.200
System Manager 3.2.1.200 (MU2)
Kernel 3.2.1.200 (MU2)
TPD Kernel Code 3.2.1.200 (MU2)
CIM Server 3.2.1.200 (MU2)
.
.
.
VASA Provider 2.1.4 (P12)
Feedback
Yes
No
Powered by
