Hyper-V External Switches (Management and SET)
Hi All,
Is the following the best practice / correct way to configure VMSwitches on a bare metal server?
It will consist of 2 x VMs (VM#1 DC, VM#2 File/Print)
I have an HPE DL380 Gen11 and the Hyper-V Role installed, with the following interfaces:
Get-NetAdapter
Name InterfaceDescription ifIndex Status
—- ——————– ——- ——
PCIe Slot 15 Port 1 Broadcom NetXtreme Gigabit Ethernet 11 Up
PCIe Slot 15 Port 2 Broadcom NetXtreme Gigabit Ethernet #2 8 Up
PCIe Slot 15 Port 3 Broadcom NetXtreme Gigabit Ethernet #3 9 Up
PCIe Slot 15 Port 4 Broadcom NetXtreme Gigabit Ethernet #4 6 Up
vEthernet (Hyper V Swi… Hyper-V Virtual Ethernet Adapter 2 Up
Dedicate the management OS to a Hyper-V Switch for traffic isolation.
Management OS
PCIe Slot 15 Port 1
Broadcom NetXtreme Gigabit Ethernet
Remainder for VM traffic using SET:
PCIe Slot 15 Port 2
Broadcom NetXtreme Gigabit Ethernet#2
PCIe Slot 15 Port 3
Broadcom NetXtreme Gigabit Ethernet3
PCIe Slot 15 Port 4
Broadcom NetXtreme Gigabit Ethernet#4
Create New VMSwitch for the Hyper-V Host Management OS
New-VMSwitch -Name “Management OS” -NetAdapterName “PCIe Slot 15 Port 1” -AllowManagementOS $true
We set “Allow management operating system to share this network adapter” as this virtual switch is dedicated to management traffic.
The Hyper-V host should have access to this adapter for administrative purposes.
Next, Create a NewVMSwtich Switch Embedded Teaming (SET)
New-VMSwitch -Name “SET-Team” -NetAdapterName “PCIe Slot 15 Port 2″,”PCIe Slot 15 Port 3″,”PCIe Slot 15 Port 4” -EnableEmbeddedTeaming $true -AllowManagementOS $false
Set-VMSwitchTeam -Name “SET-Team” -LoadBalancingAlgorithm Dynamic
Get-VMSwitchTeam -Name “SET-Team” | FL
Get-VMSwitch
The SET-TEAM VMSwitch is used by the VMs for VM traffic,as it is best practice to isolate VM traffic from management traffic.
We dont “Allow the management OS to share this network adapter” as it can lead to resource contention and degraded performance for both the VMs and the management OS.
Distribution Modes
We have a choice of 2 LB distribution modes for SET Teams
Hyper-V Port
Dynamic
We use Dynamic as “Hyper-V port mode is not the best if you are only hosting a few VMs due to it not being granular enough to achieve a well-balanced distribution”
Configuring TCP/IP
Configure TCP/IP for the Virtual NIC vEthernet (Hyper-V Server Management OS)
The physical NIC is now bound to the virtual switch and does not handle TCP/IP directly.
Do not assign or configure TCP/IP for the Physical NIC (PCIe Slot 14 Port 1) as it is now part of the virtual switch.
Thanks!
Hi All,Is the following the best practice / correct way to configure VMSwitches on a bare metal server? It will consist of 2 x VMs (VM#1 DC, VM#2 File/Print)I have an HPE DL380 Gen11 and the Hyper-V Role installed, with the following interfaces:Get-NetAdapterName InterfaceDescription ifIndex Status—- ——————– ——- ——PCIe Slot 15 Port 1 Broadcom NetXtreme Gigabit Ethernet 11 UpPCIe Slot 15 Port 2 Broadcom NetXtreme Gigabit Ethernet #2 8 UpPCIe Slot 15 Port 3 Broadcom NetXtreme Gigabit Ethernet #3 9 UpPCIe Slot 15 Port 4 Broadcom NetXtreme Gigabit Ethernet #4 6 UpvEthernet (Hyper V Swi… Hyper-V Virtual Ethernet Adapter 2 UpDedicate the management OS to a Hyper-V Switch for traffic isolation.Management OSPCIe Slot 15 Port 1Broadcom NetXtreme Gigabit EthernetRemainder for VM traffic using SET:PCIe Slot 15 Port 2Broadcom NetXtreme Gigabit Ethernet#2PCIe Slot 15 Port 3Broadcom NetXtreme Gigabit Ethernet3PCIe Slot 15 Port 4Broadcom NetXtreme Gigabit Ethernet#4Create New VMSwitch for the Hyper-V Host Management OSNew-VMSwitch -Name “Management OS” -NetAdapterName “PCIe Slot 15 Port 1” -AllowManagementOS $trueWe set “Allow management operating system to share this network adapter” as this virtual switch is dedicated to management traffic.The Hyper-V host should have access to this adapter for administrative purposes.Next, Create a NewVMSwtich Switch Embedded Teaming (SET)New-VMSwitch -Name “SET-Team” -NetAdapterName “PCIe Slot 15 Port 2″,”PCIe Slot 15 Port 3″,”PCIe Slot 15 Port 4” -EnableEmbeddedTeaming $true -AllowManagementOS $falseSet-VMSwitchTeam -Name “SET-Team” -LoadBalancingAlgorithm DynamicGet-VMSwitchTeam -Name “SET-Team” | FLGet-VMSwitchThe SET-TEAM VMSwitch is used by the VMs for VM traffic,as it is best practice to isolate VM traffic from management traffic.We dont “Allow the management OS to share this network adapter” as it can lead to resource contention and degraded performance for both the VMs and the management OS.Distribution ModesWe have a choice of 2 LB distribution modes for SET TeamsHyper-V PortDynamicWe use Dynamic as “Hyper-V port mode is not the best if you are only hosting a few VMs due to it not being granular enough to achieve a well-balanced distribution”Configuring TCP/IPConfigure TCP/IP for the Virtual NIC vEthernet (Hyper-V Server Management OS)The physical NIC is now bound to the virtual switch and does not handle TCP/IP directly.Do not assign or configure TCP/IP for the Physical NIC (PCIe Slot 14 Port 1) as it is now part of the virtual switch.Thanks! Read More
