Technical white paper

Microsoft SC-VMM 2012 and HP 3PAR best

practices and reference architecture

Table of contents
Overview 2
Executive summary 2
Audience 2
Devices 2
Terminology 2
Architecture 3
Virtual Machine Manager 3
Provider and array 4
Setup and configuration 4
Storage device 4
SMI-S provider 5
Virtual Machine Manager 5
Test harness 43
Test case execution 45
Full test case list 45
Test case list for <PARTNERNAME> - <ARRAYMODEL> 46
Additional details and guidelines 47
Known issues and limitations 47
Frequently asked questions 47
For more information 47
Overview
Microsoft® System Center (MSC) 2012—Virtual Machine Manager (VMM) introduces new features to discover and manage
block-based SAN storage using Storage Management Initiative Specification (SMI-S) as the management protocol across
multiple arrays. The provider model introduces an additional layer of software between VMM and the array, which needs
to be tested and validated.
In order to validate Microsoft System Center 2012—Virtual Machine Manager support of HP 3PAR Storage,
a PowerShell-based test harness was created by the product team. This test harness validates that the provider
and array meet VMM’s functionality and scale requirements. The test harness is made up of core primitives that
can be combined into scenario and functionality test cases. It drives the full list of test cases that need to be
completed successfully.
Partners who want their array and SMI-S provider to be supported by VMM, need to complete validation using the test
harness and publish this best-practice document that captures the configuration of VMM, storage array, and SMI-S
provider. This document also captures best practices, software and hardware configuration, limitations, and known
issues. With this document, customers should be able to deploy the same configuration in their data center and/or lab
with a high confidence level that the configuration is correct.

Executive summary
Audience
This document is for customers of VMM and HP 3PAR Storage System who plan to deploy System Center 2012—Virtual
Machine Manager to manage storage.

Devices
Microsoft System Center 2012—Virtual Machine Manager supports iSCSI and Fibre Channel storage arrays.
This document covers the following storage arrays:

• HP P10000 3PAR V800 Storage System

• HP P10000 3PAR V400 Storage System
• HP 3PAR T800 Storage System
• HP 3PAR T400 Storage System
• HP 3PAR F400 Storage System
• HP 3PAR F200 Storage System

Terminology
VMM terms
VMM management server Server that manages virtual machines, hypervisor servers, storage, network, clouds,
and services
VMM library File server used to store virtual disks, ISOs, scripts, service template files, application
installation packages, and virtual machines definitions
VMM console UI management application that connects to VMM management server
VMM command shell Command Line Interface (CLI) that connects to VMM management server, offering over
450 cmdlets
Host agent Service installed on Hyper-V servers that communicates with VMM management server
Storage management service Service installed on the same server as the VMM management server, used to
communicate with SMI-S based providers to manage storage arrays

2
Storage provider Software developed by storage vendors to manage storage devices using SMI-S
Storage classification A string value associated with a storage pool that represents a level of service or quality
of service guarantee, defined as string
Storage array Storage provided to one or more hosts
Rapid provisioning Virtual machine creation using SAN snapshot or clone technologies
HP 3PAR Storage System terms

CPG Common provisioning group; a RAID-specific storage pool

Physical copy Clone
Virtual copy Snapshot
VLUN Virtual LUN; a volume that is exported to one or more hosts

Architecture
Virtual Machine Manager
Discovery of LUNs
Discovery of array, pool, Mask and unmask set
and LUNs iSCSI CHAP
Mask and unmask LUN VMM 2012 VDS
Clone/Snapshot
Storage VDS h/w
Service Deprecated
provider

• Discovery of portals and

targets log on and log off
• Enumerate
Host • Rescan
• Mount/Unmount
iSCSI initiator • Volume to Disk
• Port on LUN mappings mapping
HBA provider VDS • Disk to LUN mapping
Host
• Virtual to physical NPIV provider
port mappings
• Create and delete
Virtual Ports

SMI-S
provider

FC array/iSCSI Target
SAN admin
tool
LUN LUN LUN LUN

3
Provider and array

Management node
A CIM Client issues CIM Operation
requests and receives and processes
CIM Client CIM Operation responses
CIM Schema

CIM Server
A CIM Server receives and
CIM Providers processes CIM Operation requests
and issues CIM Operation responses
Other InFormOS Processes

HP 3PAR array

A CIM Server receives CIM Operation CIM Client

requests, coordinates the processing of
requests and responses among the
Providers and sends CIM Operation
CIM Schema

responses back to the CIM Client.

A CIM Provider translates

CIM formatted requests into resource
specific operations and translates
CIM Provider
resource-specific responses into
CIM formatted responses.

CIM Provider communicates with other

InFormOS Processes to gather the
necessary information or to perform
actual provisioning.
Other InFormOS Processes

Setup and configuration

Storage device
HP 3PAR InForm Operating System 3.1.1 Concept guide, Setup guide, User guides, and Patch 10 Release Notes can be
found here.
The HP 3PAR Virtual Copy Software feature must be enabled if you want to create writable snapshots of an existing
LUN to contain the virtual hard disk. You can use the HP 3PAR InForm CLI Software and the HP 3PAR InForm Management
Console Software to view the licenses currently enabled on your system.

4
Software Requirements
Firmware
InForm Operating System 3.1.1. Patch 10 at a minimum
Management
InForm Management Console 4.2.1 at a minimum

Configuration
Array
Required licenses HP 3PAR Virtual Copy Software— allows one to take instant virtual copy snapshots of
existing volumes.
Optional licenses There are other licensed optional features that you can purchase, please contact your
local service provider for details.

SMI-S provider
The HP 3PAR InForm OS 3.1.1 CIM API programming reference can be found here.
The SMI-S provider feature must be enabled. You can use the HP 3PAR InForm CLI Software to view the status and to
enable it if necessary.

Software requirements
Firmware (if required) Not required; provider is embedded and is part of the InForm Operating System
Management N/A

Configuration
Array N/A
Controllers N/A
Provider SMI-S feature must be enabled. If disabled, enable it via the CLI command “startcim”

Virtual Machine Manager

The instructions in this guide detail a simple installation of Virtual Machine Manager. For testing purposes,
this is sufficient. Full installation and configuration instructions are available on the TechNet website:
http://technet.microsoft.com/en-us/library/gg610610.aspx

Setup
Pre-requisites The full list of software requirements is available online:
http://technet.microsoft.com/en-us/library/gg610562.aspx
Active directory Single domain is sufficient
Windows® Server Windows Server 2008 R2 (full installation)
Edition: Standard, Enterprise, and Data center
Service Pack: Service Pack 1 or earlier
Architecture: x64
Domain joined: Yes
iSCSI access: Yes (initiator logged into target) (if applicable)
FC access: Yes (zoned to array) (if applicable)
SQL Server Install any version of SQL Server 2008 RTM or above

5
WAIK Windows Automated Installation Kit (WAIK) for Windows 7
microsoft.com/download/en/details.aspx?displaylang=en&id=5753
.NET 3.5 (SP1) At least Microsoft .NET Framework 3.5 Service Pack 1 (SP1)
On a computer running Windows Server 2008 R2, if the .NET Framework 3.5.1 feature is not installed
(it is not installed by default), the VMM setup wizard will install the feature
WinRM Windows Remote Management (WinRM) 2.0
WinRM 2.0 is included in Windows Server 2008 R2, and by default, the Windows Remote Management
(WS-Management) service is set to start automatically (delayed start)
VMM management server
Install 1. Double click on Setup.exe.

2. Click Install.

6
3. Select features to install.
4. Select the VMM management server option, which will automatically install VMM console.
5. Click Next.

You will now be at the Product registration information page:

1. All fields are optional. Click Next.

7
 Please read this license agreement:

1. Read license agreement, select the check box at bottom of screen to accept license agreement,
and click Next.

Join the Customer Experience Improvement Program (CEIP):

1. Select either Yes or No and then click Next.

8
Installation location:

1. Type in the folder path in the Location text window, and then click Next.

Please review these prerequisite warnings:

1. Fix any errors before proceeding. Warnings can be ignored, and then click Next.

9
 Database configuration:

1. Type in the server name, which has SQL Server installed in the Server name text window.
2. Provide credentials to the database server (if required) by checking the Use the following
credentials checkbox and filling in the User name and domain details.
3. Type in a desired name in the New database name text window.

Configure service account and distributed management:

1. Select Local System account.

2. Click Next.

10
Port configuration:

1. Click Next.

Library configuration:

1. Select Create a new library share.

2. Click Next.

11
 Installation summary:

1. Click Install.

Installing features:

Installation will complete in a few minutes

12
Setup completed successfully:

1. Click Close to complete installation.

Click Close.

13
Configuration
Add Hyper-V host
Add resources 1. Click on the Fabric workspace.
2. Click the Home tab.
3. Click the Add Resources icon.
4. Click the Hyper-V Hosts and Clusters option.

Indicate the Windows computer location:

1. Select the Windows Server computers in a trusted Active Directory domain radio button.
2. Click Next.

14
Specify the credentials to use for discovery:

1. Select the Use an existing Run As account radio button.

2. Click the Browse button.

Select a Run As account:

1. Click in the Select a Run As Account text window.

15
 Provide the details for this Run As account:

1. Type in a name for the Run As account.

2. Type in user name and password associated with a domain account in Active Directory that has local
Administrative access on the Hyper-V host.
3. Click OK.

Select a Run As account:

1. In the Create a Run As account window

2. Click OK.

16
Select a Run As account:

1. In the Select Run As Account text window, type in the account name.
2. Click OK.

Specify the credentials to use for this discovery:

1. Click Next.

17
 Specify the search scope for virtual machine host candidates:

1. Select the Specify Windows Server computers by names radio button.

2. Type in NETBIOS or FQDN of host.
3. Click Next.

Select the computers that you want to add as hosts:

1. Select the Computer Name from the list.

2. Click Next.

18
Specify a host group and virtual machine placement path settings for hosts:

1. Click Next.

Confirm the settings:

1. Click Finish.

19
Job status Check status of the job and wait for the job to complete.

Add Hyper-V cluster

Add resources 1. Click the Home ribbon tab.
2. Click the Add Resources icon.
3. Click the Hyper-V Host and Clusters option from the dropdown list that appears.

20
Indicate the Windows computer location:

1. In the Add Resource Wizard, under Resource location, select the Windows Server computers in a
trusted Active Directory domain radio button.
2. Click Next.

Specify the credentials to use for discovery:

1. Select the Use an existing Run As account option.

2. Click on the Browse button.

21
 Select a Run As account:

1. Select an option from the Run As account list.

2. Click OK.

Specify the credentials to use for this discovery:

1. In the Add Resource Wizard, under Credentials, select the Use an existing Run As account
radio button.
2. Click Next.

22
Specify the search scope for virtual machine host candidates:

1. Select the Specify Windows Server computers by names radio button.

2. Type in NETBIOS or FQDN of cluster.
3. Click Next.

Select the computers that you want to add as hosts:

1. Select the cluster Computer Name you want to add as a host.

2. Click Next.

23
 Specify a host group and virtual machine placement path settings for hosts:

1. Click Next.

Confirm the settings:

1. Under the Summary option, in the Confirm the settings window, click Finish.

24
Job status Check status of the job and wait for the job to complete.

Cluster 1. Click on the Fabric icon.

configuration

2. Right-click on Hyper-V cluster and select properties.

3. On the General tab, reduce the cluster reserve (nodes) to 0.
4. Click OK.

25
Add SMI-S provider
Add resources 1. Click the Fabric icon.
2. Click the Providers icon.

3. Select HOME ribbon tab.

4. Click the Add Resources icon drop-down list.
5. Choose the Storage Devices option, and click the Add Storage Devices button.

26
Specify the IP address or FQDN of the storage provider:

1. Type in the provider IP address or FQDN and specify the port as:
Default non-secure port is 5988
Default secure port is 5989
2. Check the Use Secure Sockets Layer (SSL) connection check box only if the provider has a secure port
configured using SSL.
3. Select a Run As account from the Browse window and click Next.

Discover and import storage device information:

1. Wait for the Discovery and import storage device information bar to complete filling.
2. Click Next.

27
 Select Storage Pools:

1. Check the check boxes under the Select storage pools to place under management then assign a
classification list and assign classifications for them.
2. Click the Create classification button.

28
New Classification
Create a storage classification:

1. Type in the Name.

2. Click the Add button.

Select storage pools under management then assign a classification:

1. Select the Classification by ticking the relevant check box

2. Click the Next button.

29
 Confirm the settings:

1. Click the Finish button.

Pools under 1. Click the Classification and Pools icon.

management 2. Choose the Fabric option that appears.

30
 Expand classification:
Expand pool

Array configuration
Rapid provisioning 1. Click the Arrays icon.
default

2. Right-click on array under management. For this example you would click on PIT-s37.
3. Click the Properties option.

31
 4. Click Settings.
5. Select Use snapshots or select Clone logical units, as the case may be. And, click OK.

Note: License for Virtual Copy Software must be enabled to be able to select the Use snapshots option.

Storage Group 1. Click on the PowerShell icon in the ribbon.

Default

2. Change storage group per cluster policy by typing the following commands:
By setting CreateStorageGroupsPerCluster to TRUE, VMM will create a masking set per Hyper-V cluster
and add all of the host initiators to the masking set.
$array = Get-SCStorageArray -Name "PIT-s371"
Set-SCStorageArray -StorageArray $array -CreateStorageGroupsPerCluster $true

By setting CreateStorageGroupsPerCluster to FALSE, VMM will create a masking set per node in the
Hyper-V. The host initiators will be added to the respective masking set.
$array = Get-SCStorageArray -Name "PIT-s371"
Set-SCStorageArray -StorageArray $array -CreateStorageGroupsPerCluster $false

32
SAN copy-capable template
Array operations
Logical units Create two logical units 25 GB each
Unmask both logical units to the VMM management server
• Make sure iSCSI initiator is logged into targets (if applicable)
• Make sure FC HBA is zoned to array (if applicable)

Windows operations On the VMM management server, create two folders under Library share:
C:\ProgramData\Virtual Machine Manager Library Files\SATemplate
C:\ProgramData\Virtual Machine Manager Library Files\HATemplate
Open Disk management.
• Initialize new disks
• Create partitions that consume the entire disk
• Create a volume on each disk
• Use folder path to mount one disk to SATemplate folder

Use the folder path to mount one disk to HATemplate folder.

33
Copy VHDs Copy Windows OS VHD to each folder

Import VHDs
Refresh Library 1. Right-click on the Library share icon.
2. Select the Refresh option from the drop-down menu.

3. Wait for folders and VHDs to be displayed.

4. Verify that the SAN Copy-capable property is Yes.

Create Templates
Non-HA Template 1. Click the Create VM Template from the ribbon action to launch the Create VM Template wizard.

34
Select a source for the new VM Template:

1. Select the Use an existing VM Template or a virtual hard disk stored in the library radio button.
2. Click the Browse button.

Select VM Template Source:

1. Select a VHD in the SATemplate folder.

2. Click the OK button.

35
 3. Select a source for the new VM Template.
4. Click the Next button.

VM Template Identity:

1. Type in the VM Template name, for example SATemplate.

2. Click the Next button.

36
Configure Hardware:

1. Click Next.

Configure Operating System:

1. In the Guest OS profile text box, select the (None—customization not required) option.
2. Click Next.

37
 Summary:

1. Click the Create button.

HA Template 1. Click Create VM Template ribbon action to launch the Create VM Template wizard.

38
Select a source for the new VM Template:

1. Select the Use an existing VM Template or a virtual hard disk stored in the library radio button.
2. Click the Browse button.

Select VM Template Source:

1. Select the VHD in HATemplate folder.

2. Click the OK button.

39
 Select a source for the new VM Template:

1. Click the Next button.

VM Template Identity:

1. Type in the VM Template name.

2. Click the Next button.

40
Configure Hardware:

1. Click on Availability, under Advanced.

2. Select the Make the virtual machine highly available option.
3. Click the Next button.

Configure Operating System:

1. For Guest OS profile, select the (None—customization not required) option.

2. Click the Next button.

41
 Summary:

1. Click the Create button.

List templates 1. Under Library, click Templates.

2. Click the VM Templates icon.

42
Test harness
Setup
Test Harness Package The test harness is available for download on TechNet blogs
Create folder on VMM management server C:\toolbox\testharness
Unzip content of package to C:\toolbox\testharness
Script Configuration The test harness reads Storageconfig.xml when it starts up to get configuration information
Input
Vmmserver Name of the machine on which VMM management server is installed
Providername Name to be given to the provider while adding to VMM management server
Username Username for adding the provider to VMM management server
Password Password for adding the provider to VMM management server
Netname Provider machine to which to connect to
Port Port on which provider is listening
Poolname Name of the storage pool to be managed
Array name Array name from which the pool should be selected
(optional—use only if provider manages multiple arrays and they all have same pool name)
classificationname Any name to be used for classifying the storage type
hostname1 Host name—against which the tests will be added
clustername1 Cluster name—against which the tests will be added
Node Names of nodes in the cluster (add as many of these as there are nodes in the cluster)
lunDescPrefix Prefix to be used for all LUNs that are created by test—this will help in clean-up in case the tests fail to
complete
ParallelLunsCount Number of parallel operations for create LUNs—can be overwritten in the test function
ParallelSnapshotCount Number of parallel operations for creating snapshots—can be overwritten in the test function
ParallelCloneCount Number of parallel operations for creating clone—can be overwritten in the test function
vmNamePrefix Prefix to be used for the new VM’s that are created
vmTemplate Prefix to be used for the new VMs that are created (e.g. SATemplate)
havmTemplate Name of the pre-created VM Template (for deploying to stand-alone hosts) (e.g. HATemplate)
Vmlocation Path for new VM’s—for SAN deployments this will not be used. (Provide any valid path)
Domainusername Domain credentials to add/remove hosts and clusters—user name
Domainpassword Domain credentials to add/remove hosts and clusters—password
OutputCSVFile Name of the csv file that holds the results of the tests with time it took for completing the operation
LibServer Name of the library server—can be the standalone host
LibServerLocation Path of the share on the library server where the LUN’s are mounted (for creating san copy capable
template)
LibShareName Name of the library server share
VHDName Name of the disk that will be copied on to the san copy capable LUN
Install PowerGUI Script You can download this tool from PowerGUI.org
Editor
Configure trace log collection
Enable VMM tracing Use instruction in the article on: http://support.microsoft.com/kb/970066. You will need traces from
the VMM management server in this case (not client or host)

43
Enable SCX CIM-XML 1. Add registry subkey HKLM\Software\Microsoft\Storage Management\CIMXMLLog.
command tracing 2. Add registry DWORD value LogLevel, value 4.
3. Add registry String value LogFileName and assign it to the full path and file name to use for logging.
Make sure the directory exists and that the Network Service account has read/write access.
4. Stop and start Microsoft Storage Management Service.

Traceview ETL 1. Download WDK 7.1 at microsoft.com/download/en/details.aspx?displaylang=en&id=11800 and

install on VMM management server.
2. Download traceview.zip from TechNet blog and unzip to a local folder on VMM management
server.
3. Copy traceview.exe from WDK folder to this folder.
4. Run traceview.exe as administrator.
5. File->Open Workspace, select scx and click OK.
Traceview UI will start to display trace information when the next storage operation executes.
This information also gets logged to storageservice.etl file in same folder.

44
Test case execution
The test harness is made up of multiple test cases that exercise functionality and scale.

Full test case list

Single operations Test102_CreateDeleteOneLun -LunSizeinMB 10240
Test103_CreateOneSnapshotOfLun -LunSizeinMB 10240
Test104_CreateOneCloneOfLun -LunSizeinMB 10240
Test105_RegisterUnRegisterOneLunToHost
Test155_RegisterUnRegisterOneLunToCluster
Test106_RegisterOneLunAndMountToHost -LunSizeinMB 10240
Test107_RapidCreateOneVMToHost
Test157_RapidCreateOneVMToCluster
End-to-end scenarios Test101_AddRemoveProvider
(Baseline scale test) Test202_CreateDeleteMultipleLun -Count 10 -LunSizeinMB 10240
Test203_CreateMultipleSnapshotsOfLun -Count 10 -LunSizeinMB 10240
Test204_CreateMultipleClonesOfLun -Count 10 -LunSizeinMB 10240
Test205_RegisterUnRegisterMultipleLunsToHost -Count 10 -LunSizeinMB 10240
Test255_RegisterUnRegisterMultipleLunsToCluster -Count 10 -LunSizeinMB 10240
Test206_MountMultipleLunsToHost -LunSizeinMB 1024 -Count 10
Test256_MountMultipleLunsToCluster -Count 10 -LunSizeinMB 10240
Test207_RapidCreateMultipleVMsToHost -Count 10
Test257_RapidCreateMultipleVMsToCluster -Count 10
Test501_MigrateMultipleVMFromHost2Cluster -VMCount 10
Test502_MigrateMultipleVMFromCluster2Host -VMCount 10
Test400_PerformAllClusterTests
End-to-end scenarios Test101_AddRemoveProvider
(Full scale test) Test202_CreateDeleteMultipleLun -Count 10 -LunSizeinMB 10240
Test203_CreateMultipleSnapshotsOfLun -Count 10 -LunSizeinMB 10240
Test204_CreateMultipleClonesOfLun -Count 10 -LunSizeinMB 10240
Test205_RegisterUnRegisterMultipleLunsToHost -Count 10 -LunSizeinMB 10240
Test255_RegisterUnRegisterMultipleLunsToCluster -Count 10 -LunSizeinMB 10240
Test206_MountMultipleLunsToHost -LunSizeinMB 1024 -Count 10
Test256_MountMultipleLunsToCluster -Count 10 -LunSizeinMB 10240
Test207_RapidCreateMultipleVMsToHost -Count 10
Test257_RapidCreateMultipleVMsToCluster -Count 10
Test207_BatchRapidCreateMultipleVMsToCluster -BatchSize 10 -NumberofBatches 25
Test501_MigrateMultipleVMFromHost2Cluster -VMCount 10
Test502_MigrateMultipleVMFromCluster2Host -VMCount 10
Test400_PerformAllClusterTests

45
Test case list for <PARTNERNAME> - <ARRAYMODEL>
Single operations Test102_CreateDeleteOneLun -LunSizeinMB 10240 Passed
Test103_CreateOneSnapshotOfLun -LunSizeinMB 10240 Passed
Test104_CreateOneCloneOfLun -LunSizeinMB 10240 Passed
Test105_RegisterUnRegisterOneLunToHost Passed
Test155_RegisterUnRegisterOneLunToCluster Passed
Test106_RegisterOneLunAndMountToHost -LunSizeinMB 10240 Passed
Test107_RapidCreateOneVMToHost Passed
Test157_RapidCreateOneVMToCluster Passed
End-to-end Test101_AddRemoveProvider Passed
scenarios (Baseline Test202_CreateDeleteMultipleLun -Count 10 -LunSizeinMB 10240 Passed
scale test)
Test203_CreateMultipleSnapshotsOfLun -Count 10 -LunSizeinMB 10240 Passed
Test204_CreateMultipleClonesOfLun -Count 10 -LunSizeinMB 10240 Passed
Test205_RegisterUnRegisterMultipleLunsToHost -Count 10 -LunSizeinMB 10240 Passed
Test255_RegisterUnRegisterMultipleLunsToCluster -Count 10 -LunSizeinMB 10240 Passed
Test206_MountMultipleLunsToHost -LunSizeinMB 1024 -Count 10 Passed
Test256_MountMultipleLunsToCluster -Count 10 -LunSizeinMB 10240 Passed
Test207_RapidCreateMultipleVMsToHost -Count 10 Passed
Test257_RapidCreateMultipleVMsToCluster -Count 10 Passed
Test501_MigrateMultipleVMFromHost2Cluster -VMCount 10 Passed
Test502_MigrateMultipleVMFromCluster2Host -VMCount 10 Passed
Test400_PerformAllClusterTests Passed
End-to-end Test101_AddRemoveProvider Passed
scenarios (Full Test202_CreateDeleteMultipleLun -Count 10 -LunSizeinMB 10240 Passed
scale test)
Test203_CreateMultipleSnapshotsOfLun -Count 10 -LunSizeinMB 10240 Passed
Test204_CreateMultipleClonesOfLun -Count 10 -LunSizeinMB 10240 Passed
Test205_RegisterUnRegisterMultipleLunsToHost -Count 10 -LunSizeinMB 10240 Passed
Test255_RegisterUnRegisterMultipleLunsToCluster -Count 10 -LunSizeinMB 10240 Passed
Test206_MountMultipleLunsToHost -LunSizeinMB 1024 -Count 10 Passed
Test256_MountMultipleLunsToCluster -Count 10 -LunSizeinMB 10240 Passed
Test207_RapidCreateMultipleVMsToHost -Count 10 Passed
Test257_RapidCreateMultipleVMsToCluster -Count 10 Passed
Test207_BatchRapidCreateMultipleVMsToCluster -BatchSize 10 -NumberofBatches 25 Passed
Test207_BatchRapidCreateMultipleVMsToCluster -BatchSize 20 –NumberofBatches 12 Passed
Test501_MigrateMultipleVMFromHost2Cluster -VMCount 10 Passed
Test502_MigrateMultipleVMFromCluster2Host -VMCount 10 Passed
Test400_PerformAllClusterTests Passed

46
Additional details and guidelines
Known issues and limitations
Based on the results of the test harness, this section details any issues encountered with the array or provider.
This section also calls out any scale or functionality limitations.

Maximum length of 31 characters for StorageVolume ElementName

Description HP 3PAR array limits StorageVolume ElementName to 31 characters. VMM during rapid VM provisioning
creates snapshots with format like LU1_4065825e343c1f7f_<vmname>. This limit <vmname> to
10 characters in length.
Fix available No
Details of fix Workaround is to define a VM with name that is equal to or less than 10 characters.
Applicable to HP 3PAR SMI-S provider | HP 3PAR array

Empty SPC not supported

Description HP 3PAR array does not support empty SPC’s, (SPC without any volumes.) On a hide path operation of
the last volume of an SPC, the SPC itself is automatically removed. This exposes a race condition in VMM
when doing multiple exposes or hide path operations in parallel where the SPC is not removed from its
cache. This will cause unmask operation failure in subsequent test cases.
Fix available No
Details of fix Workaround is to refresh the provider on VMM in between tests.
Applicable to HP 3PAR SMI-S provider | HP 3PAR array

Frequently asked questions

Question Can I install the SMI-S provider and VMM management server on the same machine?
Answer HP 3PAR SMI-S provider is embedded, and so this question is not applicable.
Question What is the minimum size of Hyper-V based cluster configuration?
Answer SCVMM 2012 cluster setup requires a minimum of 4 nodes and can extend to a max of 16 nodes.
Question Can the Hyper-V nodes be configured on a VM?
Answer This configuration is not supported.

For more information

If you currently deploy VMM and HP 3PAR Storage System in your IT and plan to deploy Microsoft System Center 2012—
Virtual Machine Manager to manage storage, visit: hp.com/storage/windows.

Get connected
hp.com/go/getconnected
Current HP driver, support, and security alerts
delivered directly to your desktop

© Copyright 2012 Hewlett-Packard Development Company, L.P. The information contained herein is subject to change without notice. The only
warranties for HP products and services are set forth in the express warranty statements accompanying such products and services. Nothing herein
should be construed as constituting an additional warranty. HP shall not be liable for technical or editorial errors or omissions contained herein.

Microsoft and Windows are U.S. registered trademarks of Microsoft Corporation.

4AA4-2876ENW, Created September 2012

47