This article is not part of the Building Microsoft System Center Cloud series but we will use the new cluster to host our VMs in the cloud series.

Design

High-level design

  • None. It is very simple...

Low-level design

Networks

First we should configure the network.

Topology
  • In the production environment you would like to have physical or VLAN separation of the networks but in our case in our testing environment we will use this configuration because this is the best configuration that currently I am able to use.
  • Another possibility is to have multiple 10 Gb network adapters on a single network, team them to a single virtual switch and create multiple virtual network adapters with configured Quality of Services (QoS - configured minimal bandwidths). It is possible to do this configuration on a single Hyper-V cluster using PowerShell but it is much simpler to do it later from the System Center Virtual Machine Manager.
  • Do not forgot to use different subnets for inter-cluster communication (heartbeat and other communication) and live migration.

Storage

  • Direct connection to the SAN (Fibre-Channel).

Implementation overview

« Previous Next »

Part of the series

  1. Implementation of the Windows Server Failover Cluster - Basic guide with all recommended steps
  2. Implementing Windows Server 2012 R2 Hyper-V Failover Cluster - Part 2 - Network configuration
  3. Implementing Windows Server 2012 R2 Hyper-V Failover Cluster - Part 3 - Installation and basic configuration
  4. Implementing Windows Server 2012 R2 Hyper-V Failover Cluster - Part 4 - Cluster storage and quorum configuration
  5. Implementing Windows Server 2012 R2 Hyper-V Failover Cluster - Part 5 - Cluster network configuration
  6. Implementing Windows Server 2012 R2 Hyper-V Failover Cluster - Part 6 - Final steps
  7. Implementing Windows Server 2012 R2 Hyper-V Failover Cluster - Part 7 - Installation of the first VM directly into HA