8/30/2019 Hp 3par Software Plug-in For Vmware Vaai
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 – (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.
Add-EsxSoftwareDepot Add-EsxSoftwareDepot Add-EsxSoftwarePackage -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 VMwareVAAI2.2QL22710502.zip, 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 VMwareVAAI2.2QL22710502.zip Add-EsxSoftwarePackage -ImageProfile ' -SoftwarePackage 3PARvaaipInServ 4. Create Deploy Rule Create the deploy rule to use the image profile that includes the Plug-in. New-DeployRule -Name -Item ', -Pattern Add-DeployRule -DeployRule 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 psapsaProfilePsaClaimrulesProfile. Expand the psapsaProfilePsaClaimrulesProfile 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, VAAIFilter 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 psapsaProfilePsaClaimrulesProfile by right clicking and selecting add profile again. Enter the following for the Claim information. That’s 5001 for Rule Number, 3PARVAAIPINSERV 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.
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 – (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. Add-EsxSoftwareDepot Add-EsxSoftwareDepot Add-EsxSoftwarePackage -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 VMwareVAAI2.2QL22710502.zip, 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 VMwareVAAI2.2QL22710502.zip Add-EsxSoftwarePackage -ImageProfile ' -SoftwarePackage 3PARvaaipInServ 4. Create Deploy Rule Create the deploy rule to use the image profile that includes the Plug-in.
New-DeployRule -Name -Item ', -Pattern Add-DeployRule -DeployRule 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 psapsaProfilePsaClaimrulesProfile. Expand the psapsaProfilePsaClaimrulesProfile 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, VAAIFilter for PSA plugin name and filter for claimrule class.
Green Screen Software Plugin For Photoshop
The click on claim type and enter the following. That’s 3PARdata for the Vendor name and. for the Model. Now create another psapsaProfilePsaClaimrulesProfile by right clicking and selecting add profile again.
Translate a short text fragment from English to Chinese or the other way around. Only Chinese characters are accepted for translations from Chinese to English, Mandarin. Reverso English- Chinese dictionary: discover hundreds of thousands of words and phrases translated from English to Chinese, idiomatic expressions, slang. Convert English to Chinese instantly and for free at the click of a button with SDL FreeTranslation.com. Free english to chinese translation. Google's free service instantly translates words, phrases, and web pages between English and over 100 other languages.
Selamat hari raya font jawi. Enter the following for the Claim information. That’s 5001 for Rule Number, 3PARVAAIPINSERV for PSA plugin name and VAAI for claimrule class.
Magicfeatures Software Plugin For Magicjack
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.
Attention, Internet Explorer User Announcement: VMware Communities has discontinued support for Internet Explorer 7 and below. In order to provide the best platform for continued innovation, VMware Communities no longer supports Internet Explorer 7. VMware Communities will not function with this version of Internet Explorer. Please consider upgrading to Internet Explorer 8, 9, or 10, or trying another browser such as Firefox, Safari, or Google Chrome. (Please remember to honor your company's IT policies before installing new software!).
Attention, Internet Explorer User Announcement: VMware Communities has discontinued support for Internet Explorer 7 and below. In order to provide the best platform for continued innovation, VMware Communities no longer supports Internet Explorer 7. VMware Communities will not function with this version of Internet Explorer. Please consider upgrading to Internet Explorer 8, 9, or 10, or trying another browser such as Firefox, Safari, or Google Chrome.
(Please remember to honor your company's IT policies before installing new software!).
Hi Everyone, I am hoping that someone could clarify something for me. In an ongoing support case with HP 3PAR the engineer has advised us that on ESXi5.5 we should be disabling the VAAI on the ESXi5.5 hosts because the 3PAR OS is 3.1.1 or above and so uses the T10 plugin built in to VMware. He has provided the 'HP 3PAR VMware ESX/ESXi Implementation Guide' which after detailed reading I found has confirmed that the HP 3PAR VAAI Plugin 2.2.0 for ESXi 5.x should not be used on HP 3PAR OS 3.1.1 or later because it uses T10 instead.
That is fine I have not installed this plugin, but I can't find in that document it going on to say that we need to turn off the VAAI in VMware. He specifically wants me to make the below changes: vicfg-advcfg connectionoptions -s 0 /DataMover/HardwareAcceleratedMove vicfg-advcfg connectionoptions -s 0 /DataMover/HardwareAcceleratedInit vicfg-advcfg connectionoptions -s 0 /VMFS3/HardwareAcceleratedLocking In my mind as a VCP this would disable all VAAI including the built in T10 and I would get no benefit whatsoever. I can't find any other documentation or forum anywhere suggesting that VAAI should be turned off in the way so I can only assume that the HP engineer has made a mistake. Furthemore the hosts are built with HPs own ESXi5.5 image and so I would have expected that if it was recommended to disable these then it would be done in the image.
It isn't, they are enabled by default. Is anyone been able to confirm which way is correct?
Comments are closed.
|
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |