Hyper-V
A Windows technology providing a hypervisor-based virtualization solution enabling customers to consolidate workloads onto a single server.
2,636 questions
Create Hyper-V Cluster with different netwok speeds
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(6.4, 81%, 10%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EJ%3C/text%3E%3C/svg%3E)
JoBeko
1
Reputation point
I have a branch office with 2 individual 2019 Hyper-V servers => single point of failure, maintenance only possible on Sundays/holidays.
I now want to build a Win 2019 cluster with redundant ISCSI SAN.
The servers each have 2x 1Gbits in the company network and 2x 10Gbits in the SAN network.
Planned reconstruction:
Set up two SET (Switch Embedded Teaming).
A SET with both 1Gbits NICs for VMs and management.
A SET with both 10Gbits NICs for iscsi, csv, live migration...
Creating the vSwitches:
New-VMSwitch -Name "vVM" -NetAdapterName "Gbits1_1","Gbits1_2" -EnableEmbeddedTeaming $true
New-VMSwitch -Name "vOther" -NetAdapterName "Gbits1_1","Gbits1_2" -EnableEmbeddedTeaming $true
Creating the vNics:
Add-VMNetworkAdapter -ManagementOS -Name "MGT" -SwitchName "vVM"
Add-VMNetworkAdapter -ManagementOS -Name "iscsi1" -SwitchName "vOther"
Add-VMNetworkAdapter -ManagementOS -Name "iscsi2" -SwitchName "vOther"
Add-VMNetworkAdapter -ManagementOS -Name "csv" -SwitchName "vOther"
Add-VMNetworkAdapter -ManagementOS -Name "LiveMig" -SwitchName "vOther"
Would the structure work like this and can I use MPIO together with the two virtual iscsi networks?