Hyper-V Cluster Network configuration with following parameters:

The following configuration leverages 4x 1GB Ethernet and 4x 10GB Ethernet NICs and LOM (LAN on Motherboard). The storage can be connected via iSCSI with MPIO or SMB 3.x.x without RDMA. The configurations uses physical configuration and software defined / converged network for Hyper-V.

 Pro’s and Con’s of that solution

 Pro Con
– High Bandwidth for VM- Good Bandwidth for Storage
– Separated Management and Heartbeat Interface
– Full fault redundant
– Can be used in switch independent or LACP (with stacked switches) teaming mode
– Limited Bandwidth for Livemigration
– a lot of NICs and Switches needed


Switch name Bandwidth Switchtyp
1GBE SW01 1 GBit/s physical stacked or independed
1GBE SW02 1 GBit/s physical stacked or independed
10GBE SW01 10 GBit/s physical stacked or independed
10GBE SW02 10 GBit/s physical stacked or independed
SoftSW01 1 GBit/s Software defined / converged
SoftSW02 10 GBit/s  Software defined / converged

 Neccessary Networks

Networkname VLAN IP Network (IPv4) Connected to Switch
Management 100 SoftSW01
Cluster 101  SoftSW01
Livemigration 450  1GBE SW01 & 1GBE SW02
Storage 400  10GBE SW01 & 10GBE SW02
Virtual Machines 200 – x 10.11.x.x/x  SoftSW02

 Possible rearview Server


 Schematic representation


Switch Port Configuration

 sw1gbe sw10gbe

Bandwidth Configuration vNICs

vNIC min. Bandwidth Weight PowerShell Command
Management 40%
Cluster 10%

QoS Configuration Switch

Networkname Priority
Management medium
Cluster high
Storage high
Livemigration medium
VMs dependig on VM Workload


How to get notified and react when a cluster NIC fails

Hi everybody,

today a short day to day helper regarding cluster networks.

Last weekend I had a question from my coworker, if it is possible to react on failed networkconnections within a cluster even if the cluster is still running.

As you know Hyper-V is running as long as the cluster heartbeat is available and the storage is reachable. Only if these connections fail, Hyper-V Cluster forces a node to failover his roles.

My answer, yes it is possible with some tricks. First thing you need to know is, that if a network connection in the cluster failes, we get an error event.

Event ID 1129 — Cluster Network Connectivity Partitioned https://technet.microsoft.com/en-us/library/dd353962%28v=ws.10%29.aspx?f=255&MSPPError=-214721739

This event is also noticed in the event viewer of your Hyper-V Host. Now you can attach a task to that event and for example run a script which forces a failover.

02-06-_2015_09-17-51 02-06-_2015_09-18-35 02-06-_2015_09-19-07


The script to set the node in maintenance  mode and force a failover could look like:

You can achieve the same effect when you use System Center Operations Manager by configuring an Agent Task for your Hyper-V Host.

Find more info here: https://technet.microsoft.com/en-us/library/hh563486.aspx


Free ebook: Microsoft System Center Deploying Hyper-V with Software-Defined Storage & Networking

Microsoft recently published a new ebook about Deploying Hyper-V with Software-Defined Storage & Networking. You can find it here.

New book: Windows Server 2012 R2 Pocket Consultant: Storage, Security, & Networking

Source: http://blogs.msdn.com

Coverage includes:

· Managing file systems and drives
· Configuring storage
· Data sharing
· Managing TCP/IP networking
· Running DHCP clients and servers
· Optimizing DNS
· Administering network printers and print services
· Security, compliance, and auditing
· Backup and recovery

To download the eBook please click here.