This post was edited/updated on April 5, 2015.
In This Article
In Part I and Part II of this series we covered the deployment of HP StoreVirtual VSA including the Centralized Management Console (CMC) on Hyper-V, and the configuration of the StoreVirtual VSA Cluster and Failover Manager, Part III this post we will create our Hyper-V Cluster using Virtual Machine Manager.
So without further ado, let’s get started.
As we mentioned in Part I, HP StoreVirtual integrated very well with Microsoft Hyper-V such as HP Insight Control for Microsoft System Center, HPE Management Pack for SCOM, VSS provider and requestor functions, LeftHand DSM for MPIO, Application-Aware Snapshot Manager, Recovery Manager for Windows, Windows Active Directory and SMI-S Support for System Center Virtual Machine Manager.
For streamlined workflows in Hyper-V environments, the storage presented by StoreVirtual VSA can be managed from within Microsoft System Center Virtual Machine Manager (SCVMM) 2012 SP1. Using VMM provision new storage for a virtual machine or rapid deployment of a virtual machine template with SAN Copy. HP StoreVirtual does not require a proxy agent, instead, SCVMM communicates directly with the StoreVirtual Cluster.
Once the StoreVirtual cluster has been set up as described in Part II, the cluster virtual IP address of the VSA can be added as a storage provider into Virtual Machine Manager. When adding StoreVirtual, make sure you use SSL encryption for the communication, default port (TCP 5989), and protocol SMI-S CIM-XML as shown in the below screenshots:
The storage resources need to be associated with a storage classification (administrator-defined class of storage, such as Bronze, Silver, Gold).
After the provider has been added successfully, all clusters in your StoreVirtual management group will be listed in the Classification and Pools list. New volumes can be provisioned from the available storage pools, used by new virtual machines, and presented to Hyper-V hosts that are managed by Virtual Machine Manager via iSCSI.
Note: After you successfully registered the VSA in VMM via SMI-S, there is no information shown other than the device name. No Vendor, No Model, and even No storage information!!!
Unfortunately, Microsoft System Center Virtual Machine Manager 2012 R2 is not supported yet by HP VSA SAN IQ11 only VMM 2012 SP1 is qualified, and hopefully, this will be fixed in the near future.
So let’s go back to the traditional way and present the LUN manually on each Hyper-V node via the iSCSI initiator.
After the LUN is mapped on each node, we will create Windows Server 2012 R2 Failover Cluster using the Hyper-V hosts in VMM. Any VMs that are deployed on the cluster will be made highly available, so after a host failure, the VMs would automatically restart on another node in that cluster, providing resiliency to both planned and unplanned downtime.
Here are the steps to create the Cluster in VMM fairly simple:
1) Select the Fabric workspace in VMM.
2) Select the Home tab above the ribbon.
3) Click Create, and select Hyper-V Cluster.
4) In the Create Cluster Wizard, on the General page, type your desired “Cluster Name” in the Name field.
5) Next to Use an existing Run As account, click Browse, select an admin account in order to create the cluster, and then click OK. Click Next.
6) On the Nodes page, multi-select HV01 and HV02, click Add, and then click Next.
7) On the IP Address page, check the box next to 172.16.20.0/24, select LAN IP Pool from the Static IP Pool dropdown. VMM will automatically allocate an IP address to the Cluster from that pool of IP Addresses. Click Next.
8) On the Storage page, select the disks you want to cluster, in my case the first disk will be selected as witness disk and the second one as Cluster Shared Volume (CSV).
9) On the Networks page, click Next. The Virtual Switches and Logical Switches for these hosts were already created.
10) On the Summary page, ensure the settings match below and then click Finish.
11) Observe the running job in the Jobs window. Maximize the Jobs window. In the results pane at the bottom, select the Validate Cluster job, and click the Details tab. Observe the job through to completion.
12) This will take a few minutes to complete.
And here you go the Hyper-V Cluster is created!
Hope this blog series demonstrated the full picture of how to deploy HPE StoreVirtual VSA on Hyper-V and the integration with VMM.
Thanks for reading.
Until then, enjoy your day!