Hello everyone,

In today’s blog post, I’ll show you how you can manage StarWind Virtual SAN with System Center Virtual Machine Manager 2012 R2.

Before we begin, we first draw up an action plan.

1- Installing and Configuring the StarWind SMI-S Agent
2- Connecting an SMI-S service provider to SCVMM 2012 R2
3- Creating a logical unit in SCVMM
4 – Distribution of storage pools and logical units
5- Attaching storage to a Hyper-V cluster

As you can see, we have a series of steps that need to be configured before we present the storage space Hyper-V cluster.

In this presentation I use the following products:

StarWind Virtual SAN V8.0 Version 7929
System Center Virtual Machine Manager 2012 R2 UR6
– 2 X Windows Server 2012 R2 Hyper-V hosts

Step 1. Install and configure the StarWind SMI-S Agent

Storage Management Initiative – Definition (SMI-S) is a disk storage management standard.

Warehouse manufacturers must ensure SMI-S support with their products. They typically offer so-called An SMI-S service provider or “agent” that mediates communications between an SMI-S client and a server storage group. The SMI-S client (SCVMM) is connected to the SMI-S service provider via the CIM-XML protocol, while the SMI-S service provider itself can use its own interfaces to manage disk space.

StarWind Software, Inc.. provides a SMI-S service provider called StarWind SMI-S Agent for storage management. In the current build version of StarWind, the SMIS-S provider is included in the executable program.

You can install StarWind SMI-S Agent on any server.

When the installation of the StarWind SMI-S Agent is complete, you must configure it StarWindSMISConfigurator utility.

To configure the StarWind SMI-S Agent:

1. Open Run window.
2. Write StarWindSMISConfigurator.
3. Click ALRIGHT.


4. StorageSystemName field specifies the name of the disk group, e.g. Storage.

5. Configure StorageSystemIP address A Hyper-V host using the StarWind service (this step is required if you installed the StarWind SMI-S Agent on another server, but in my case I have both the SMI-S Agent and the StarWind service installed on the Hyper-V host).

6. StorageSystemPort leave the number unchanged.

7. path the fields specify the correct paths to the folders where the disk drive images are stored. You must specify the paths to the server where the StarWind iSCSI object is launched, using the same format as was used to create virtual devices in the StarWind Management Console. Here is my demo My Computer E StarWind-VMData

8. Because I am using StarWind Virtual SAN for Hyper-V in a converged situation where the storage and compute nodes are on the same hardware, it is recommended that you configure the StarWind SMI-S Agent HA repository with the following parameters: The first node and Another node:

  • Path, partner and partnerHostName
  • HB connections and partnerHBInterfaces
  • Sync connections and partnerSyncInterfaces

Leave the other settings as the default settings.

9. After applying the new settings, restart the StarWind SMI-S Agent, the StarWind SMI-S Agent will restart automatically, so make sure the StarWind Service is running before applying the new settings.

Step 2. Connect the SMI-S service provider to SCVMM 2012 R2

To enable disk drive management using VMM, you must connect the appropriate SMI-S service provider to the SMI-S agent.

Connect your SMI-S provider:

1. Click More resources button on the SCVMM console toolbar.
2. Select Storage devices.


3. Specify the type of storage service. choose Add a storage device managed by your SMI-S service provider button


4. Select SMI-S CIMXML protocol.
5. Enter the address of the host where the StarWind SMI-S Agent is installed and running, and the user name that the VMM uses to authorize the StarWind SMI-S Agent. Since I installed the SMI-S agent on the Hyper-V host, I configure the management IP address.
6. Click Next.


7. If the VMM succeeds in connecting to the SMI-S Agent, it will display all available disk systems and eventually the StarWind Storage Array Pool will be identified.


8. Click Next and select the ConcretePools to assign to the VMM. I choose ConcretePool_Storage_HA because I use HA Storage Pool. Each selected pool must be classified as Gold, Silver or Bronze. If you have not yet defined a rating, click Create a rating create one and then configure Host group.

9. Click Next.


10. Confirm the previously configured settings. Summary shows information about disk matrix, service provider, and groups managed by VMM.


Step 3. Create a logical unit in SCVMM

Adding a new logical unit:

1. Click Create a logical unit on the toolbar.


2. Create a logical unit dialog box select a storage pool, specifies name and size and click ALRIGHT.


The recently created storage device appears in the list.


Confirm this feature in the StarWind Management Console, and as you can see, we have a new device called HAI picture 3


Step 4. Sharing storage pools and logical units

Reserving reserve warehouses and logical units:

1. Click Share capacity on the toolbar.


2. Align storage capacity dialog box, make sure ConcretePool_Storage_HS is listed in the Storage Pools:

In previous versions of SCVMM, we used Align the storage tanks and Align logical units for this host group … However, this behavior has been changed in the latest version of VMM, so this step is no longer needed because we shared storage space All hosts During SMI-S provider registration.


Step 5. Connect memory to Hyper-V servers

Connecting a logical unit to a Hyper-V host:

1. Select the Hyper-V host and click Features in the context menu, but since I have two Hyper-V Cluster nodes, I choose the cluster name NINJA CLUSTER Ninja


2. Features click Available storage space on the left screen.

3. Click Add add a disk group.


4. Click ALRIGHT.


5. Click ALRIGHT confirm and add available storage space to both nodes.

6. Click Features again under Cluster Name

7. Features click Available storage space on the left screen.

8. Select Volume and click Convert to CSV.


9. Click ALRIGHT The disk can be added and added to Cluster Shared Volumes.

10. Features click Shared volumes confirms that the cluster disk is converted to a cluster shared disk.

Confirm this function Failover Cluster Manager!

As you can see, we have a new disk converted to a Cluster Shared Volume disk and ready to host our virtual machines Mouth to mouth


All operations can be performed from the VMM console and do not need to be processed StarWind Management console. thus, the use of SMI-S greatly simplifies storage management, as it eliminates the need to use different disk spaces produced by different storage vendors.

System Center Virtual Machine Manager is an important step in automating the management of private, public and hybrid cloud infrastructure.

I hope this post has been informative for you and I would like to thank you for reading.

/ Charbel


Please enter your comment!
Please enter your name here