DFS 2012R2 Step By Step Guide

Hello all,

Long time since my last post, i just finished a large implementation of DFS 2012R2 and iv’e thought this will be informative for you all so hope you will enjoy.

I also recommend using the Technet virtual Labs via Microsoft for trying to configure DFS

https://technet.microsoft.com/en-us/virtuallabs/bb467605.aspx

DFS 2012R2

Best Regards,

Henry Hazot

Hyper-V 2012R2 installation via IBM V3700

This week i had the pleasure of setting up a new system for my client…

V3700 IBM Storage two controllers

X3550M4 fully loaded to rock and roll

2 HP 5500 switch

The main idea is to create a classroom lab for students at High-School, cool right now your probably thinking this is a private school but your wrong it’s a Public High-School so good for them…:-)

I started by installing the new V3700 that by the way is a walk in the park compare to all kind of other vendors.

You receive a “Donkey” just plug it in your laptop and a nice clean wizard will startup and guide u to give a managment IP for the Cluster of the controller.

Then just plug it to the left controller and wait until the blinking stops…about 3 min.

Next open a browser and https://ClusterIPaddress the default username is SuperUser and the default Password is passw0rd the “O” is Zero.

Once you launch the GUI you get the Overview panel that is so nice and user friendly i got to say that for IBM this is a big step.

Next Configure a Pool of disk and RaidGroup btw this is also a wizard.

Create Volumes as requested, for our manners i created a 512GB fix size.

Add the servers Initiators to a new group and called them Hyper-V

Map the Vol to the new Group Hyper-V.

Configured the ISCSI ip for the second  network card for the ISCSI protocol.

That’s it…done.

Installed the new X3550M4 via ServerGuide pre downloaded from the IBM site.

Booted up and configure Raid 1 for the OS and run with the wizard until it asks you to replace the dvd with the Windows Server 2012R2

Finished the installation MUST fully update the OS via Microsoft update.

Rename and join the Hyper-V servers to the Domain…..btw i updated the Active Directory already to 2012R2 🙂

Configured all of the network cards as pre planned all teaming except the ISCSI.

2 cards for Managment

2 cards for Virtual Switch

2 cards for ISCSI

1 card for IMM

Installed MPIO and ISCSI for mapping the newly created Volume on the V3700…

Very Important not to use Teaming for ISCSI it’s not best practices and works bad, best is to use the MPIO by Microsoft.

Next…Connected the ISCSI initiators to the target Cluster IP of the V3700 and success login.

You can see that i successfully connected to the target V3700.

Next install on both Hyper-V the feature Fail Over Clustering and reboot.

Open the FailoverCluster and run the Validate Cluster Wizard….this process will check that all of the pre configuration are ready for creating the cluster Important to understand that this process only validates and doesn’t create.

I got some red errors about having a few more Network cards with the same IP 169.254.x.x…of-course Microsoft there not connected i had to just Disable these two cards on both servers before retrying the validation again.

Next, Give the Hyper-V cluster a name and IP you will need to pick on witch network cards you will like to relay i choosed the Management.

I Couldn’t print screen the real deal because of security issues so i just found this screen online.

Next up creating the CSV for the Virtual Machines .

It will look somthing like this…on the right there is the Add Storage wizard so easy just add the ISCSI Volume we created on the V3700.

Now just create a new a Virtual Switch or Virtual Fiber Swtich in our case it’s a Virtual Switch.

New external virtual switch and configure the bind with the pre configured Teaming for the Virtual Switch Card.

Create a new VM or via the Hyper-v Management or via the FailoverCluster Management….so whats the different. ?

If you would like the VM to be Highly Avalible and be able to LiveMigration you will pick the FailoverCluster Management but if you want just a simple VM pick the Hyper-V Management, i always want the HightAvailability so lets have a look….

That’s it…all done.

Enjoy

Henry Hazot