Documenti di Didattica
Documenti di Professioni
Documenti di Cultura
Contents
Overview .......................................................................................................................................................................................................................................................................................................................................................... 3
Executive summary................................................................................................................................................................................................................................................................................................................................ 3
Audience.................................................................................................................................................................................................................................................................................................................................................... 3
Devices ........................................................................................................................................................................................................................................................................................................................................................ 3
Terminology..................................................................................................................................................................................................................................................................................................................................................4
Architecture .................................................................................................................................................................................................................................................................................................................................................. 5
Virtual Machine Manager ........................................................................................................................................................................................................................................................................................................... 5
Provider and array ............................................................................................................................................................................................................................................................................................................................6
Setup and configuration .................................................................................................................................................................................................................................................................................................................... 7
Storage device...................................................................................................................................................................................................................................................................................................................................... 7
SMI-S provider...................................................................................................................................................................................................................................................................................................................................... 7
Virtual Machine Manager ...........................................................................................................................................................................................................................................................................................................8
Test harness........................................................................................................................................................................................................................................................................................................................................46
Test case execution ............................................................................................................................................................................................................................................................................................................................48
Full test case list ..............................................................................................................................................................................................................................................................................................................................48
Test case list for <PARTNERNAME> - <ARRAYMODEL> .........................................................................................................................................................................................................................49
Additional details and guidelines ...........................................................................................................................................................................................................................................................................................50
Known issues and limitations ..............................................................................................................................................................................................................................................................................................50
Frequently asked questions..................................................................................................................................................................................................................................................................................................50
For more information.........................................................................................................................................................................................................................................................................................................................50
Technical white paper Page 3
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 HPE 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 HPE 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:
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 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
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
Rapid provisioning Virtual machine creation using SAN snapshot or clone technologies
Architecture
Virtual Machine Manager
Technical white paper Page 6
The HPE 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 HPE 3PAR InForm CLI Software and the HPE 3PAR InForm Management Console Software to view the licenses
currently enabled on your system.
SOFTWARE REQUIREMENTS
Firmware
Management
CONFIGURATION
Array
Required licenses HPE 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 HPE 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 HPE 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”
Technical white paper Page 8
SETUP
Pre-requisites The full list of software requirements is available online:
technet.microsoft.com/en-us/library/gg610562.aspx
SQL Server Install any version of SQL Server 2008 RTM or above
Technical white paper Page 9
.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
2. Click Install.
Technical white paper Page 10
1. Read license agreement, select the check box at bottom of screen to accept license agreement, and click Next.
Installation location:
1. Type in the folder path in the Location text window, and then click Next.
1. Fix any errors before proceeding. Warnings can be ignored, and then click Next.
Technical white paper Page 13
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.
Port configuration:
1. Click Next.
Library configuration:
Installation summary:
1. Click Install.
Installing features:
Click Close.
Technical white paper Page 17
CONFIGURATION
Add Hyper-V host
1. Select the Windows Server computers in a trusted Active Directory domain radio button.
2. Click Next.
Technical white paper Page 18
1. In the Select a Run As Account text window, type in the account name.
2. Click OK.
1. Click Next.
Technical white paper Page 21
Specify a host group and virtual machine placement path settings for hosts:
1. Click Next.
1. Click Finish.
Technical white paper Page 23
Job status Check status of the job and wait for the job to complete.
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.
1. In the Add Resource Wizard, under Credentials, select the Use an existing Run As account radio button.
2. Click Next.
Technical white paper Page 26
Specify a host group and virtual machine placement path settings for hosts:
1. Click Next.
1. Under the Summary option, in the Confirm the settings window, click Finish.
Technical white paper Page 28
Job status Check status of the job and wait for the job to complete.
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.
1. Wait for the Discovery and import storage device information bar to complete filling.
2. Click Next.
Technical white paper Page 31
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.
Technical white paper Page 32
New Classification
Create a storage classification:
Expand classification:
Expand pool
Array configuration
2. Right-click on array under management. For this example you would click on PIT-s37.
3. Click the Properties option.
Technical white paper Page 35
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.
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
Technical white paper Page 36
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
Import VHDs
Create Templates
Non-HA Template 1. Click the Create VM Template from the ribbon action to launch the Create VM Template wizard.
Technical white paper Page 38
1. Select the Use an existing VM Template or a virtual hard disk stored in the library radio button.
2. Click the Browse button.
VM Template Identity:
Configure Hardware:
1. Click Next.
1. In the Guest OS profile text box, select the (None—customization not required) option.
2. Click Next.
Technical white paper Page 41
Summary:
HA Template 1. Click Create VM Template ribbon action to launch the Create VM Template wizard.
Technical white paper Page 42
1. Select the Use an existing VM Template or a virtual hard disk stored in the library radio button.
2. Click the Browse button.
VM Template Identity:
Configure Hardware:
Summary:
Test harness
SETUP
Test Harness Package The test harness is available for download on TechNet blogs
Script Configuration Input The test harness reads Storageconfig.xml when it starts up to get configuration information
Providername Name to be given to the provider while adding to VMM management server
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)
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)
OutputCSVFile Name of the csv file that holds the results of the tests with time it took for completing the operation
LibServerLocation Path of the share on the library server where the LUN’s are mounted (for creating san copy capable template)
VHDName Name of the disk that will be copied on to the san copy capable LUN
Install PowerGUI Script Editor You can download this tool from PowerGUI.org
Enable VMM tracing Use instruction in the article on: support.microsoft.com/kb/970066. You will need traces from the VMM management server in this case
(not client or host)
Technical white paper Page 47
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.
Technical white paper Page 48
Fix available No
Details of fix Workaround is to define a VM with name that is equal to or less than 10 characters.
Fix available No
Answer HPE 3PAR SMI-S provider is embedded, and so this question is not applicable.
Answer SCVMM 2012 cluster setup requires a minimum of 4 nodes and can extend to a max of 16 nodes.
Rate this document © Copyright 2012, 2016 Hewlett Packard Enterprise Development LP. The information contained herein is subject to change without
notice. The only warranties for Hewlett Packard Enterprise 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. Hewlett Packard
Enterprise shall not be liable for technical or editorial errors or omissions contained herein.