Skip navigation


Normally, I wouldn’t directly forward a link.

but this is too good to pass.

Here it is. 

 

 


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.

image

 

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:

image

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

image

image

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

image

Provide server’s FQDN

image

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.

image

Now, remember those are SMB shares.

image

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.

image

 

If you click file Servers, you will see it.

Let’s check a Hyper-v Host properties

image

 

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.

clip_image002[7]

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.

image

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

image

Now, you can install this SMI-S provider.

Notice:

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

image

image

Don’t forget to reboot.

 

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

Install iSCSI Initiator

image

Run this iSCSI initiator

image

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

image

 

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

Then, you can add storage again

image

This time, we choose SMI-S provider

image

after a scan

image

 

image

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

 

image

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.

image

 

image

image

image

 

SNAGHTML22e8fd52

 

Allocate storage resource in SCVMM 2012 SP1

 

When you allocate your storage resource in VMM, you should do it from Host Group folder level.

image

Notice:

Only iSCSI or SAN can be allocated to Host group. SMB share can only be allocated via host cluster level.

You can allocate Storage Pool

image

image

Create logical Unit base on your new storage pool,

On Host Cluster level

image

Convert this Available Storage to CSV

image

You can convert CSV back to available storage but only it has no VMs sitting on that.

image

 

The end


Now, in this post. I’m going to talk about Storage in SCVMM 2012 SP1 and also how to build a Windows 2012 File server to connect with SCVMM.

One thing I’m very sure about Microsoft is they must love Onions. Because a SCVMM 2012 combining with Windows File server 2012 is like a huge onion which has many layers.

With embedded VHD technology, Microsoft deployed one layer after another layer of VHD which makes me worried because VHD can be corrupted. What would happen if one of VHD layers corrupted and you will loss all data on top of this layer? Or shall we wait for Windows 2012 R2 which may use VHDX instead of VHD?

Anyway, with no further ado, let’s cut Onion open.

Following is the diagram of File storage I used in my lab.

image

Let me walk you through with this diagram first so you will have better understand instead of lossing yourself in a million picture of wizard.

Layer 1(Physical Disks):

Target: File Server

Let’s start with physical disk layer on physical Host.

Windows 2012 File server has 3 physical disk. 2 x RAID 1 for 0S which only 70GB. 1 900GB disk with Raid 0.

Let’s see a screenshot from File server

image

 

Layer 2 (Storage Pool):

Target: File Server

With Windows File server 2012, You can build a storage pool which we call it VMMlib01

image

 

Layer 3(Virtual Disks):

Target: File Server

Now, we build a virtual Disk on top of Storage Pool.

image

Since this is my File server, I have built number of Virtual disks (the virtual disk concept equals normal physical disk back in Win2k8). I have built 2 quorum disks size are 1GB for VMM cluster, and Hyper-v cluster.

VHD50, Virtual Disk 01 and VHD200 are my test virtual disks to store VMs.

for test purpose, I have setup both Fixed and thin disks.

 

Layer 4 (Volumes):

Target: File Server

Same thing as volume in old OS. You will give drive label to each volume.

image

I have create each volume for each virtual disk. Those disks will be shared via iSCSI.

Layer 5(Storage Pool):

Target: VMM server

In the VMM, there are multiple ways to import storage into VMM library. With same target host (like File server here), only one way of connection will be accepted.

For example, if I choose to use SMB share to connect to File server, then I can’t use iSCSI to connect in VMM.

You can choose to use simple SMB 3.0 share, but then you will loss lots of storage function.

If you choose using FC/iSCSI as storage, you will be able to define your storage as different classification. You may want to put fast storage pools into gold classification and slow storage to Silver or Brown.

The storage Pool you will find here is same thing as volume from File Server.

 

 

image

 

Layer 6 (Logical Unit)

Target: VMM Server

This logical Unit is created base on Storage Pool in VMM server. You can choose use some part of space to assign to Host group (Not cluster) and reserve some logical Units for future.

Layer 7 (Clustered Share Volume)

Target: VMM Server –> Hyper-v Cluster

Believe it or not, once you assign Logical Unit to Host group and it doesn’t mean your hyper-v Cluster is going to use it. From Cluster point of View, it just got available space.

You need to convert it to Cluster shared Volume

image

 

image

 

Now, if you switch to Hyper-v cluster, you will see your shared volume is there.

image

 

SNAGHTML1ee369da

 

To be continued …..


Well, this is very stupid thing for me who is working with Vmware product for years.

As you all know, I have a Hyper-v Cluster (2 nodes) which I connect with iSCSI storage (Windows file Server 2012). I have built CSV share and allocate to cluster via SCVMM 2012. But when I tried to clone (yes, clone, not even deploy),

I ran into following error.

image

I checked everything up and down, cluster configuration, destroy LUN, format LUN , etc. Finally, I found this resolve this issue.

 image

Why the Microsoft just setup as default?

Anyway, that resolves my issue. Hope this post can help you.


Cause:

This issue has same cause as you can’t shutdown VM from VMM console.

SNAGHTML4f7965e

 

image

 

Well, don’t worry about file format (VMM 2012 SP1 supposes both VHD/VHDX, don’t worry about location of your VM, it can be on local disks of Hyper-v or Share storage, it has something to do with virtual Guest Services, or you can call it “Integrated Service” from Hyper-v.

 

If you go to Hyper-v, and try to install Integrated Service on that VM, system will tell you you are on latest version already.

So what to do?

Solution:

 

Just click “Refresh” from VMM Console

SNAGHTML4fb66de

 

This is clearly a bug of VMM which import VMs into VMM but not checking integrate service properly!


This is Part 2 of installing SCVMM 2012 SP1 on virtual cluster and on Hyper-v Cluster hosts.

Part 1 can be found from here

Let’s review what we have installed.

We have installed File server which provides Quorum disks. We have created AD components and two VMM virtual servers.

We have installed Failover features on VMM servers and all other prerequisites.

Let’s start the Part 2 with Create a Cluster on VMM servers.

Start Failover manager and Validate a cluster first (if you don’t do this step, the creation wizard will also do it)

 

image

Now, with any clusters, a heartbeat network is required. Since our VMMs will sit on same Hyper-v Host, so what I need is to build a new Virtual Switch called Heartbeat.

Notice:

If you want to join these two Hyper-v hosts in the future, you must have EXACTLY same virtual network settings on both Hyper-v hosts. Therefore, a internal switch or private switch is NO NO for cluster. You have to build External switches with same name on both Hyper-v Hosts.

 

image

Once this is done, add a new virtual Nic on VMM and connect to heartbeat switch.

SNAGHTML1c00f2

 

image

Configure Heartbeat IP on both VMMs

 

clip_image002

 

clip_image002[5]

You also make sure you have create DNS A records for this cluster and also VMM app cluster.

clip_image002[7]

image

 

image

 

clip_image002[11]

 

image

With Windows 2012 Cluster, we can actually use share folder as quorum.

image

 

clip_image002[13]

 

clip_image002[15]

 

image

image

image

 

Install VMM 2012 SP1

Well, most jobs are done. Here is the final installation.

clip_image002[17]

 

clip_image002[19]

System automatically detects you are on cluster. so click Yes.

clip_image002[23]

 

image

 

clip_image002[25]

 

clip_image002[27]

 

clip_image002[29]

Yes, it’s installed on C drive.

 

clip_image002[31]

Oops, I didn’t setup enough start up memory on this VMM vm.

I went back and made adjustment.

clip_image002[33]

image

Be aware to make sure svc_vmmadmin has rights to create DB on your SQL database server.

image

Make sure VMMCLU01 exists in your DNS server.

image

The location of AD can be found via ADSI EDIT. Just found the OU like this

image

 

clip_image002[37]

 

clip_image002[39]

DOn’t do that now, you are on cluster.

 

clip_image002[41]

clip_image002[43]

Now, do the same thing on the other VMM VM. Most critical settings are already setup.

image

 

image

Once the wizard go through, you installed VMM on cluster successfully.

clip_image002[45]

 

clip_image002[47]

 

This is the end of this post. There will be other posts soon talking about how to configure VMM 2012 SP1.


Just run into this issue and tried to connect iSCSI disk to Win2012 cluster. No matter how hard I tried, it just disappear from Failover manager.
I googled it and found this

What types of drives can I use with Storage Spaces?

You can use commodity drives attached via Serial-Attached SCSI (SAS), Serial ATA (SATA), or USB. Storage layers that abstract the physical disks are not compatible with Storage Spaces. This includes VHDs and pass-through disks in a virtual machine, and storage subsystems that layer a RAID implementation on top of the physical disks. iSCSI and Fibre Channel controllers are not supported by Storage Spaces.
RAID adapters, if used, must be in non-RAID mode with all RAID functionality disabled. Such adapters must not abstract the physical disks, cache data, or obscure any attached devices including enclosure services provided by attached just-a-bunch-of-disks (JBOD) devices. Storage Spaces is compatible only with RAID adapters that support completely disabling all RAID functionality.
Yes, in Windows Server 2012 you are able to leverage Clustered Spaces only for SAS connected JBODs.

To explain the philosophy/rationale behind this: In Windows 8 (equally applicable to Windows Server 2012), Storage Spaces enables delivery of a new category of highly capable storage solutions at dramatically lower price-points & maximized operational simplicity. In doing so, we have strived to ensure a predictably consistent usage experience (irrespective of storage component hardware failures) while delivering excellent performance. Our internal testing exposed complex interactions when combining Spaces with “storage arrays” connected via iSCSI and/or FC. Therefore, for Windows 8 (Windows Server 2012), we are constraining Spaces based deployments to SAS connected JBODs (for business critical deployments), and SATA/USB connected disks (for home/enthusiast/small-business customers).

 

Stand by for answer from Microsoft

 

Update:

I have found solution how to connect iSCSI server to VMM, but not via cluster though. I will write a new post about how to do it. However, still waiting for MS reply regarding this interesting thing.

Reference:
http://social.technet.microsoft.com/wiki/contents/articles/11382.storage-spaces-frequently-asked-questions-faq.aspx


With fresh installation of Windows 2012 and Windows 8, you can’t access old SMB share or CIFS share correct.

The solution is following.

· To enable SMBv1 on the SMB client, run the following commands:

· sc.exe config lanmanworkstation depend= bowser/mrxsmb10/mrxsmb20/nsi

· sc.exe config mrxsmb10 start= auto

· To enable SMBv2 and SMBv3 on the SMB client, run the following commands:

· sc.exe config lanmanworkstation depend= bowser/mrxsmb10/mrxsmb20/nsi

· sc.exe config mrxsmb20 start= auto

 

 

 

Run following Powershell command to disable new security negotiate on SMB 3 which some third party doesn’t support. 

Be aware once you disable this security negotiate, you need to disable all Windows 8 and Windows 2012 in your environment so they can talk to each other.

 

Set-SmbClientConfiguration -RequireSecuritySignature $false

Or

Set-ItemProperty -Path “HKLM:\SYSTEM\CurrentControlSet\Services\LanmanWorkstation\Parameters” RequireSecureNegotiate -Value 0 -Force


image

Last week, I presented my design chart of my Lab. Today, I’m going to build SCVMM2012 cluster on Virtual Machine. In another word, this post will also show you how to build Virtual Cluster on Hyper-V.

Environment:

Physical Host:

Before you start, you need to make sure that you have at least one Hyper-v Host available. You will also need a windows File Server which will provide quorum disk for your vmm cluster. You can use a virtual file server(Windows 2012) but I have a physical box.

Clearly, you need a virtual SQL server as database source.

Virtual Machine:

Since we are building cluster, so you will need to VMs which I install Windows 2012 on that. Each VM has 2 nics. One is heartbeat and the other is for production and management.

What you will install on VMM01 and VMM02:

  • AD Preparation

Create two user accounts, svc_vmm and svc_vmmadmin

image

 

image

  • Configure distributed Key Management (DKM)

DKM is critical for VMM which stores encryption key for both VMM servers to access.

clip_image002[23]

clip_image002[25]

clip_image002[27]

image

grant Vmmadmins rights for this AD  object

 

image

image

image

image

 

  • Install Windows 2012 Standard version

Build windows 2012

Add IP address

Join VM into domain

Turn off Firewall

Enable Remote Desktop

Disable IE security

Disable UAC

test remote winrs /r:vmm01 ipconfig

image

  • Add SCVMM accounts into local Administrator groups

You must add those two accounts separately.

Please DO NOT create a group and put users into group and put group into local administrator group, because it won’t work!

image

 

  • Install Failover Manager
  • Install .NET Framework 3.5 Feature

clip_image002

When you install that, be aware you need to have Windows 2012 ISO or CD ready like following

clip_image002[5]

You instruct installation application where to find source code, otherwise, it will fail.

Tip:

You will be surprised that how many features actually coded base on 3.5 rather than 4.1. This is one of “must install” for me every time I install a VM.

  • Install Windows ADK for Windows 8

clip_image002[7]

 

clip_image002[9]

 

clip_image002[11]

 

clip_image002[13]

 

clip_image002[15]

 

  • Install SQL Native Client (I’m using SQL 2008 R2 SP1)
  • Install SQL Command Line Utilities

clip_image002[17]

Build windows 2012 File Server

A file server is important for cluster. As cluster, you need a quorum disk which can be accessed by all members of cluster so they can exchange data, voting etc. You can have a NAS or SAN blah,blah, but the cheapest way is to use a free windows Server to provide shared folder. Windows 2012 cluster has this capability to use this share folder as quorum storage, thank for SMB 3.0 which allows multiple accesses at same time.

By saying that, we can also build iSCSI features on both File server and VMM01,02. No additional software required, Windows 2012 will allow us to have a iSCSI storage. I will write another post about it.

Let’s install

Make sure you have these service installed on your windows File server.

clip_image002[31]

You will also need a separated physical disk attached to file server.

clip_image002[33]

Once you have this physical disk, you can build a new storage Pool.

clip_image002[35]

clip_image002[37]

clip_image002[39]

clip_image002[41]

Now, I have storage Pool, I will start build a virtual disk on the pool.

clip_image002[43]

clip_image002[45]

clip_image002[47]

clip_image002[49]

clip_image002[51]

clip_image002[53]

clip_image002[55]

You will also need to build another virtual disk for storing VMs as to be used by VMMLibrary Role later on.

Now, you need to install Share feature.

clip_image002[57]

clip_image002[59]

 

clip_image002[61]

Once that’s done, Let’s come back and share the quorum

clip_image002[63]

clip_image002[65]

clip_image002[69]

clip_image002[67]

clip_image002[71]

don’t need anything here for quorum

clip_image002[73]

However, we do need permission to be added here. You need to add svc_vmm, svc_vmmadmin and also two VMM computer AD objects.

image

image

 

I’m not going to repeat similar steps here.

clip_image002[75]

With this File server, you can also build quorum for Hyper-v Hosts as well.

 

To be continued….


topology of scvmm

 

 

This is the test environment I currently have. I will write a series of posts of how to build this environment and issues I have encountered along the way.

Essentially, this lab involves following physical hosts.

2 Hyper-v 3 servers, 1 ESXi and 1 file server.

The rest of them are all VMs with Windows 2012.

VMM01,VMM02, clustered

SQL03 (windows 2008 R2, SQL 2008 R2 )

APPV01 (App-v Server)

VCE01 (vCenter 5.1)

Plus with some DCs which are not included in this diagram.

Most posts will come. Please be patient.

Follow

Get every new post delivered to your Inbox.

Join 125 other followers