Storage configuration of SCVMM 2012 SP1 with Windows 2012 File Server (Part 2)

From my last Post, we have discussed about what we need to achieve in the Lab. I’m pasting the diagram here again so we can use that as reference. For more details, you can click last post to get it.

What a Windows 2012 file server can do?

A Windows 2012 File server can provide storage via SMB 3.0 Share and iSCSI. If you are looking for how to do SMB 3.0 share, please follow this link. Windows 2012 also provide native version of iSCSI feature which includes a iSCSI Server end and iSCSI initiator (client end). It’s all free.

With SCVMM 2012 SP1, the installation CD even comes with a SMI-S provider driver which you can install on Windows 2012 so VMM can import Windows 2012 File server into Library as iSCSI array rather than SMB Share.

Import Win2012 File Server via SMB share

I have mentioned this before. VMM can import a File Server via only one method. For example, if you have import this File server via SMB Share, you won’t be able to import this File server via iSCSI. You must remove the server from Library and import again.

Here is the procedure to import a Win2012 File Server into VMM.

Before you do anything, you need to add your VMM service account (For example, svc_vmm) into local administrator group on Win2012 File server.

Notice:

You can’t add a Active Directory Group into local administrator group and you must user individual user instead. Otherwise, it won’t work.

Like following:

After you have done that, open VMM console and choose Fabric,

Clearly, you have 3 options here. Let’s choose Windows based File (SMB Share).

Provide server’s FQDN

Now, what it does is to push/install VMM agent on File server with credential of account you choose before, that service account must have load admin rights on File server.

Now, remember those are SMB shares.

Notice:

the storage provider type is Native Windows WMI? That’s how VMM get all information by executing WMI remotely. But that native window WMI doesn’t support iSCSI.

If you click file Servers, you will see it.

Let’s check a Hyper-v Host properties

Import Win2012 File Server via iSCSI Protocol

With SMB Share, you can’t create storage pool from VMM, nor Logical Unit which sort of defeat purpose of VMM. At the end of the day, it is a Virtual Machine Manager. What happen if it can’t allocate resource inside of VMM with multiple tenants scenario?

With Windows File Server, you don’t need to download StarWind FreeNas or any other third party SAN/NAS tool, you can just build a iSCSI box base on Native Windows.

First of all, we need to install iSCSI features on Windows File server.

Now, the next thing we need to install is SMI-S provider on Windows file Server. SMI-S will allow us to connect VMM with iSCSI.

so From VMM installation folder, you will find this file.

copy that file to File server. You need to check whether the stability patch has been installed already on File server. KB2770917

Now, you can install this SMI-S provider.

Notice:

You MUST reboot File server after installation otherwise, you will ran into some strange issues.

Don’t forget to reboot.

On the client end, Testhyp01 and Testhyp02, you can do following.

Install iSCSI Initiator

Run this iSCSI initiator

just type the IP of File server and click quick connect. It may not work for iSCSI, but at least, it creates an iSCSI initiator.

Install Multipath I/O

If you have already import File server, remember to remove it first.

Then, you can add storage again

This time, we choose SMI-S provider

after a scan

Now, you are able to see all drives on File server.

If you don’t have any classification, you will get this. Then, you can build classification. Classification is just resource tag which you use it to label different storage resource. I use Gold and Silver here.