Done use that configuration in production! It’s only for lab use!
This configuration is very similar to the 4x 10Gb Ethernet config but not useable for production.
Hyper-V Cluster Network configuration with following parameters:
The following configuration leverages 3x 1GB 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 |
– Easy to build and good for lab use
– enougth bandwidth for test workloads
– fully converged |
– limited bandwidth
– no production use
– cheap to build |
Switches
1GBE SW01 |
1 GBit/s |
physical stacked or independed |
1GBE SW02 |
1 GBit/s |
physical stacked or independed |
SoftSW01 |
1 GBit/s |
Software defined / converged |
Neccessary Networks
Networkname |
VLAN |
IP Network (IPv4) |
Connected to Switch |
Management |
100 |
10.11.100.0/24 |
SoftSW01 |
Cluster |
101 |
10.11.101.0/24 |
SoftSW01 |
Livemigration |
450 |
10.11.45.0/24 |
SoftSW01 |
Storage |
400 |
10.11.40.0/24 |
SoftSW01 |
Virtual Machines |
200 – x |
10.11.x.x/x |
SoftSW01 |
Possible rearview Server

Schematic representation
Switch Port Configuration
Bandwidth Configuration vNICs
vNIC |
min. Bandwidth Weight |
PowerShell Command |
Management |
10% |
|
Set-VMNetworkAdapter -ManagementOS -Name "Management NIC Name" -MinimumBandwidthWeight 10 |
|
Cluster |
5% |
|
Set-VMNetworkAdapter -ManagementOS -Name "Cluster NIC Name" -MinimumBandwidthWeight 5 |
|
iSCSI |
30% |
|
Set-VMNetworkAdapter -ManagementOS -Name "iSCSI NIC Name" -MinimumBandwidthWeight 30 |
|
Livemigration |
30% |
|
Set-VMNetworkAdapter -ManagementOS -Name "Livemigration NIC Name" -MinimumBandwidthWeight 30 |
|
QoS Configuration Switch
Networkname |
Priority |
Management |
medium |
Cluster |
high |
Storage |
high |
Livemigration |
medium |
VMs |
dependig on VM Workload |
Like this:
Like Loading...