What is it?

The HP StoreFront Analytics for VMware vCenter Operations Manager, an adapter for vCenter Operations Manager from VMware, relates virtual machines and datastores to volumes from HP 3PAR StoreServ storage systems. Administrators using HP StoreFront Analytics are able to visualize and analyze data from their HP 3PAR StoreServ storage array directly within vCenter Operations Manager.

What does it do?

HP StoreFront Analytics reports detailed health, capacity, and performance metrics for HP 3PAR StoreServ components including volumes, CPGs, storage systems, controllers, drive cages, disk drives, ports, and fans.  It is distributed as a management pack that installs directly in VMware vCenter Operations.

Why is it full of goodness?

StoreFront Analytics includes preconfigured dashboards enabling the vSphere administrator to quickly get started monitoring, troubleshooting, and optimizing their HP 3PAR StoreServ storage systems from within vCenter Operations Manager. These dashboards clearly show relationships between virtual machines, datastores, and the underlying HP storage. This visibility increases the VMware administrator’s productivity and ability to deliver improved quality of service.

Licensing?

Ahh licensing, I always forget to write licensing considerations and end up getting emailed lots about it.  HP StoreFront Analytics includes a 60 day instant-on evaluation license. After 60 days the product will provide basic array health information at no charge, but requires a license for capacity and performance metrics.

Where can I get it?

Download from HP Software Depot

https://h20392.www2.hp.com/portal/swdepot/displayProductInfo.do?productNumber=vCOPS

For more information

HP StoreFront Analytics for VMware vCenter Operations Manager web page

www.hp.com/go/vcops

 

 

 

When using 3PAR VVSet, 3PAR InForm OS does not allow the removal of a Single Active VLUN if the VLUN template is created with a VV set originally. For those who arent familiar,  a VVSet is generally used for cluster configurations when a set of hosts all need to see the same VLUNS.

Using the IMC or CLI, removing a VLUN from a VLUN template created a VV set will result in all active VLUNs created by the template being removed which is not a desired result.
But alas, there is a work around as explained here.

 

Work Around:

Remove a single VV from the vvset. This will leave all the VV through the VV set VLUN template exported except the VV that is removed from the VV set.

 

Let’s jump into the CLI:

CLI%   removevvset  vvsetname volume_name

To find the setname, please run the showvvset command.

 

You can use the 3PAR InForm Management Console (IMC) interface for this as well. Please make sure you are using the latest 3PAR GUI (IMC) which you can download @ http://www.hp.com/go/hpsoftwareupdatesupport

 

The High-level GUI steps are:

 1)      Click on provision

2)      Click on vvset to edit

3)      Right click on the vvset

4)      Remove

 

HP 3PAR InForm OS 3.1.2 Command Line Interface:

http://sawpro.atlanta.hp.com/km/saw/view.do?docId=emr_na-c03618134&hsid=53975427&sz=3369226

 

HP 3PAR VMware ESX Implementation Guide:

http://sawpro.atlanta.hp.com/km/saw/view.do?docId=emr_na-c03290624&hsid=53975481&sz=4151286

 
css.php