Infrastructure Adventures


3Par VAAI Plug-In and VMware Auto Deploy

Filed under: Storage, Virtualization — Tags: , , , , , , — Joe Keegan @ 10:36 AM

Just a quick post on using the HP 3PAR Software Plug-In for VMware VAAI with VMware Auto Deploy. The process should be pretty much the same for adding any other plugin.

1.) Download the VAAI 2.2 Plugin form HP

Get it here – HP 3PAR Software Plug-In for VMware VAAI (If the link is dead just Google for it)

2.) Load your depot & add the FDM

I use an offline depot so I load it and the FDM (VMware’s Failover Domain Manager – i.e. VMware HA).

Add-EsxSoftwareDepot <Offline Depot Path>
Add-EsxSoftwareDepot http://<vCenter Server>/vSphere-HA-depot
Add-EsxSoftwarePackage -ImageProfile "<ImageProfile>" -SoftwarePackage vmware-fdm

3.) Add the 3Par VAAI Plug-in

The Plug-in is located in a zip file, the one I downloaded from HP is called, yours should have the same or similar name. Then add the zip as a depot and and add the plug-in to your image profile.

Add-EsxSoftwareDepot C:\Depot\
Add-EsxSoftwarePackage -ImageProfile "<ImageProfile>" -SoftwarePackage 3PAR_vaaip_InServ

4. Create Deploy Rule

Create the deploy rule to use the image profile that includes the Plug-in.

New-DeployRule -Name <Rule Name> -Item "<ImageProfile>",<Host Profile>,<Cluster> -Pattern <Patern>
Add-DeployRule -DeployRule <Rule Name>

5. Edit the Host Profile

The ESXi server needs to know to load the plug-in and this is accomplished through the host profile applied to server.

Edit the host profile and drill down to Storage configuration –> Pluggable Storage Architecture (PSA) configuration –> PSA claimrule number  and then select Add Profile. This will add a psa_psaProfile_PsaClaimrulesProfile.

Expand the psa_psaProfile_PsaClaimrulesProfile to show the Claim information and the Claim type. Click on the Claim information and enter the following information.

That’s 5001 for Rule Number, VAAI_Filter for PSA plugin name and filter for claimrule class.

The click on claim type and enter the following.

That’s 3PARdata for the Vendor name and * for the Model.

Now create another psa_psaProfile_PsaClaimrulesProfile by right clicking and selecting add profile again. Enter the following for the Claim information.

That’s 5001 for Rule Number, 3PAR_VAAIP_INSERV for PSA plugin name and VAAI for claimrule class.

Then enter the same info you entered above for the Claim type. That’s 3PARdata for the Vendor name and * for the Model.

As an aside, I got this information by creating a host profile from an ESXi host that had the plugin installed and working. I looked through that host profile and pulled out this info.

Now hit OK to save the host profile and you should be good to go. Once you provision another host via Auto Deploy using this host profile you should see VAAI working for your 3PAR LUNs. You can check this by validating that Hardware Acceleration for these LUNs show supported.

The Silver is the New Black Theme. Create a free website or blog at


Get every new post delivered to your Inbox.

Join 38 other followers

%d bloggers like this: