This is the first of five blog posts “From Microsoft Private Cloud to Hybrid Cloud Services”.
Here you can find our Configuration hardware on-premisses and the Start of this blog series.
PRIVATE CLOUD Infrastructure :
Before we start with installing Microsoft Windows Server 2012 R2 on our hardware, it is important to check your vendor support for Windows Server 2012 R2.
For production is vendor support very important ! (Check this for your own hardware configuration first)
Microsoft built a lot of drivers into Operating System W2012R2, we use DELL Power Edge Servers and found the following about support :
Our Dell Power Edge Servers (R410 – R610 – R710 – M620) hardware configuration drivers are in the box of Windows Server 2012 R2 🙂
We already had Microsoft Windows Server 2012 Datacenter edition installed in our forest called ICTCUMULUS, with the DELL management DVD for W2012.
Dell Support & Drivers for the Power Edge R710
We successfully upgraded all the Servers from Windows Server 2012 => Windows Server 2012 R2 and we raised domain and forest functional level to R2 :
Here you see the configuration step-by step guide for Microsoft Windows Server 2012 R2 Hyper-V Cluster :
We started with building the production Teams on each Hyper-V node with Microsoft Windows Server 2012 R2 NIC-Teaming :
Enable NIC-Teaming on the local Server with Server Manager
Our two 1 Gbit NICs are both active for the capacity
- NIC 1+2 Production Team
- NIC 3 CSV for Storage (I-SCSI Trafic)
- NIC4 Heartbeat network for Cluster.
Now we have network configured we can attach the I-SCSI LUNS to the Server, with our Dell Powervault MD3200i storage box :
With the Storage Manager of Dell we made a Host Group “Hyper-V_Cluster” with the four Hyper-V nodes.
There we provision 5 LUNS ( 4 x VDISK of 1TB and 1 x VDISK for QUORUM) for the Microsoft Windows Server 2012 R2 Hyper-V nodes.
With iSCSI Initiator of Windows Server 2012 R2 we attach the storage which is provisioned with the Dell Storage Manager.
Now we have the storage presented to the Hyper-V host and can we configure the LUNS with Diskmanagement :
Do this with all the LUNS and give them the right Volume Label like for example CVS1, CSV2, CSV3, CSV4….
Now we Have Networking and Storage ready to go, we can install the Features Hyper-V and Failover Clustering of Windows Server 2012 R2.
Install prerequisite .net Framework 3.5 via de command prompt. Make sure you mount the Windows 2012 DVD in D:
Run as Administrator CMD.exe and type the following commando : dism /online /enable-feature /all /featurename:NetFx3 /source:d:\sources\sxs
- Install the following features of Windows Server 2012 R2 : Hyper-V and Failovercluster
- Update Software via Windows Update.
- Open failover Cluster Manager
In our report we had a message about Gateway :
Here we give the Cluster a name with IP-adres.
For Hyper-V we set the Storage path for the VM Configs and VHDx Disks in Hyper-V Settings for each host.
With these steps we checked our hardware that’s in the driver box of Microsoft Windows Server 2012 R2, we provisioned iSCSI Storage and made a Windows Server 2012 R2 Hyper-V Cluster.
My Next blog is all about Management with System Center 2012 R2 Virtual Machine Manager and App-Controller.