Around the Storage Block Blog
Find out about all things data storage from Around the Storage Block at HP Communities.

More on HP Insight Control for VMware vCenter

CJZ Headshot fixed 150 x 150.jpgBy Calvin Zito, @HPStorageGuy  vExpert 2011, 2012, 2013.png

 

With VMware Partner Exchange this week, I'm in a VMware state of mind!  My last blog post had a demo of the latest version of HP Insight Control Storage Module for VMware vCenter - in that video I showed you the installation and a flyby of some of the basic functions we have. 

 

In this blog I have another demo video that shows how you can use Insight Control Storage Module to solve a problem of over-provisioned storage that prevents a VM from starting (and solving that problem).  I also show how we can change the source and target with Peer Persistence. So here's that demo video:

 

 

I didn't have time to actually tell you about HP Insight Control for vCenter and HP Insight Control Storage Module - we were having a snow storm in Boise and I needed to get my son to basketball tournament with some hazardous roads - so let me give you that overview that I didn't last time.



What is HP Insight Control for vCenter?

HP Insight Control for VMware vCenter, which is available as a single download, seamlessly integrates the manageability features of HP ProLiant, HP BladeSystem, HP Virtual Connect and HP Storage into the VMware vCenter console. By integrating HP Converged Infrastructure management features directly into VMware vCenter, administrators gain insight and control of their HP infrastructure supporting their virtualized infrastructure  —reducing the time it takes to make important change decisions, manage planned and unplanned downtime and do lifecycle management.

 

We just announced a new release available today! - HP Insight Control for VMware vCenter Server and Storage Module 7.3 with support for HP OneView!

 

What's new in v7.3?


Here's a look at what's new in this version:

 

Enhanced Storage Management

  • Full HP 3PAR Recovery Manager for VMware Integration.
  • HP 3PAR StoreServ Peer Persistence management simplified through visualizations and integrated functionality simply accessed from the vSphere console.
  • Enhanced provisioning wizard for volumes with more options and better support for HP storage.

Simplified Storage Management

  • Visualization of peer persistence configuration of HP 3PAR StoreServ]
  • Graphical relationship representation between VMs and volumes delivers simpler configuration management

Other notable enhancements

  • HP OneView support: HP OneView and HP Insight Control licensed hosts are managed under one single VMware plug-in: HP Insight Control for VMware vCenter Server 7.3. All previous features are now available for HP OneView managed hosts.
  • Grow a cluster consistently and reliably with HP OneView profiles/HP OneView reference host in 5 easy steps.
  • Coordinated and schedulable firmware deployment.  Now uses HP OneView or HP SUM to deploy a firmware baseline. 
  • Cluster level host networking configuration.  Host networking configuration (introduced in 7.2) mitigates networking configuration differences between the host and Virtual Connect profiles, this feature is now expanded so that simple click yields the same effect at a VMware cluster level
  • New HP Enclosure view delivers greater simplification in understanding the relationship between the physical and virtual
  • Simplified initial configuration of the plug-in credentials aiming at reducing initial configuration errors

 You can learn more at www.hp.com/go/icvcenter.

 

Comments
Suken(anon) | ‎05-28-2014 07:42 PM

I created the datastore on a cluster with Name: 3PAR1000_TBS_L0133_SHR_VMware, but I check back on the 3par IMC its showing the different LUN# and Different LUN Name: 3PAR1000_TBS_SHR_VMware-1665747, so could you please explain me why its happing this.

| ‎06-04-2014 03:48 AM

Hi Suken,

From my engineering team, I heard this:

To generate a unique volume name, the following logic is applied. A number is appended to the end. If the name is longer than supported by the storage system, this name is truncated in the middle.

 

Your volume name has been generated by applying these rules to the specified datastore name:

3PAR1000_TBS_L0133_SHR_VMware

3PAR1000_TBS_SHR_VMware-1665747

 

Hope that helps - Calvin

Leave a Comment

We encourage you to share your comments on this post. Comments are moderated and will be reviewed
and posted as promptly as possible during regular business hours

To ensure your comment is published, be sure to follow the community guidelines.

Be sure to enter a unique name. You can't reuse a name that's already in use.
Be sure to enter a unique email address. You can't reuse an email address that's already in use.
Type the characters you see in the picture above.Type the words you hear.
Search
Showing results for 
Search instead for 
Do you mean 
About the Author
25+ years experience around HP Storage. The go-to guy for news and views on all things storage..


Follow Us
The opinions expressed above are the personal opinions of the authors, not of HP. By using this site, you accept the Terms of Use and Rules of Participation