Special article: Hyper-V Cluster simulation demo

Introduced

Because the previous several are directly finishing the next nine uncle's hyper-V e-book sent up, personally think he wrote is not the most detailed, so today I according to their actual situation to write a simulation of the actual combat demonstration. Everything is done through the VMware WorkStation 12PRO. If you experiment with VMware, you can see my previous blog http://www.cnblogs.com/wanggege/p/4604182.html.

Environment Introduction

This environment is done through 4 servers, 1 dc,1 storage, and 2 Hyper-V host computers.

Network Name and purpose

Name	Use
public	for managing hosts
VM	communication between virtual machines
ISCSI	For HV host attached storage

Server IP

Each server has a public network card for normal management, the Stroage server has three network cards to establish the NIC group to provide iSCSI services, 2 Hyper-V hosts a four-block network card, where the VM network card for virtual machine use, migration for virtual machine migration between the clusters.

Server name	Public	Vm	ISCSI	Migration
DC	172.28.103.100
Storage	172.28.103.101		192.168.101.2*3
HV1	172.28.103.102	172.28.104.100	192.168.101.3	192.168.100.10
HV2	172.28.103.103	172.28.104.101	192.168.101.4	192.168.100.11
Hvcluster	172.28.103.104

VMNET0 is a 103 network segment Vmnet2 is 104 segment

Operating system

In addition to storage is using a dedicated storage version of Windows, others use server Datacenter

windows Server-R2 With Update1 Datacenter

" TD style= "PADDING-LEFT:7PX; padding-right:7px; Border-top:none; Border-left:none; Border-bottom:solid 0.5pt; Border-right:solid 0.5pt; "valign=" bottom ">

Span style= "color:black; Font-family: the song body; > server name	operating system
DC	windows Server-R2 With Update1 Datacenter
storage	windows Storage Server R2 with Update1
hv1
HV2	Windows Server R2 with Update1 Datacenter

Server deployment domain Control Server Installation

Specific installation can see my previous blog Windows Server R2 create ad domain http://www.cnblogs.com/wanggege/p/4605678.html

Hardware creation

Select Clone

Choose to take a snapshot of Sysprep

Server Deployment Modify IP address

Installing the Domain Control Service

Start installation

Create a domain contoso.com

Automatic restart when installation is complete

Create a new OU

Create three servers

Configure Group Policy

Turn on the firewall

Domain control creation complete, waiting for other servers to join the domain

Storage Server Installation Hardware creation

Server Deployment Modify IP address

Modify Network card Order

Creating NIC NICs

Add to New Group

Create complete

Set IP address, no gateway required

Ping the test

Installing iSCSI Services

Create an iSCSI disk

Select disk

Create a quorum disk

Configuring iSCSI Targets

Create a data disk

Create complete

HV Server Installation Hardware creation

Add 4 NIC

Select Hyper-V

Server Deployment Modify IP address

Network card renaming, convenient to distinguish

Advanced settings, adjusting the network card sequence

Use public NIC by default

Set the IP address of the VM

Unregister to DNS

iSCSI and Migration network cards do not set the gateway

Ping once setup is complete

Connecting iSCSI disks

Select Automatic Configuration

Disk online and initialized

Installing Virtualization services and Clustering features

Storage defaults, etc. will be modified at the first

Automatic Restart after installation

Modify the name of the created virtual Switch to the same name on all 2 servers, otherwise you will not be able to create the cluster because of different configurations.

Create a Failover Cluster

Open Failover Cluster Manager

Verifying the configuration

Run All tests

The test may be out of this, do not be careful, because the test will be the disk unloading

A network is an alert, it doesn't matter, because iSCSI and migration do not have a gateway set up

Create a cluster

Create complete

To configure a cluster to add a clustered shared volume

Configure the Network

Create a virtual machine

Modifying the virtual machine location

Now that the cluster has been created, it works, and we'll start using other components, such as SCVMM, to component the private cloud.

Special article: Hyper-V Cluster simulation demo