See also more Hyper-V pages

http://blogs.technet.com/b/gavinmcshera/archive/2011/03/27/3416313.aspx

http://www.windowsnetworking.com/articles-tutorials/cloud-computing/Hyper-V-Private-Cloud-Networking-Beginners-Part1.html

http://www.altaro.com/hyper-v/how-to-adjust-mtu-jumbo-frames-on-hyper-v-and-windows-server-2012/

http://www.hyper-v.nu/archives/marcve/2013/01/lbfo-hyper-v-switch-qos-and-actual-performance-part-1/

http://social.technet.microsoft.com/wiki/contents/articles/151.hyper-v-virtual-networking-survival-guide.aspx

http://social.technet.microsoft.com/wiki/contents/articles/11524.windows-server-2012-hyper-v-network-virtualization-survival-guide.aspx

http://channel9.msdn.com/Events/TechEd/NorthAmerica/2012/VIR303

http://technet.microsoft.com/en-us/library/jj134230

• Hyper-V Network Virtualization provides “virtual networks” to virtual machines similar to how server virtualization (hypervisor) provides “virtual machines” to the operating system.
• Network virtualization decouples virtual networks from the physical network infrastructure and removes the constraints of VLAN and hierarchical IP address assignment from virtual machine provisioning.
• For workload owners, the key benefit is that they can now move their workload “topologies” to the cloud without changing their IP addresses or re-writing their applications.
• For infrastructure owners, the additional flexibility in virtual machine placement makes it possible to move workloads anywhere in the datacenters without changing the virtual machines or reconfiguring the networks. For example Hyper-V Network Virtualization enables cross subnet live migration so that a virtual machine can live migrate anywhere in the datacenter without a service disruption.

• What is the point of having multipath iSCSI connections if both are patched into a single switch or if your SAN only has ports on a single card?
• What's the point in NIC teaming (fail on fault) if your physical machine has a single point of failure in a multiport network card? The same also holds through for blade enclosures. If there is going to be a hardware failure it's very unlikely to be limited to a single port. The whole card/unit is going to fail.

• Windows Server 2012 has vendor-agnostic NIC teaming
• LBFO - Load Balance Fail Over
• Switch-dependent mode
• Switch-independent mode
• Active/active
• Active/standby

Tested on Windows Hyper-V Server 2012 with an Intel X540 10GbE NIC

Start PowerShell:

powershell

Display the current settings:

Get-NetAdapterAdvancedProperty -Name "Ethernet 4" -DisplayName "Jumbo Packet" | Format-list

Enable Jumbo Frames:

Set-NetAdapterAdvancedProperty -Name "Ethernet 4" -RegistryKeyword "*JumboPacket" -RegistryValue "9014"

• Minimum - Floor
• Maximum - Cap

• Up to 8 classes
• Storage traffic separate

• SR-IOV
• Near-native network performance
• Chipset, NIC and BIOS support required
• Bypasses virtual switch and ACLs
• Can be teamed in Windows 8 and Server 2012 for maximum performance and reliability
• Can live migrate to host without SR-IOV

• Always enable VMQ
• Improves performance
• Balances interrupts

• DCTCP
• Manages congestion
• Lower latency
• Higher throughput
• Requires ECN capable switches (RFC 3168)
  • Explicit Congestion Notification

• Site-to-site connectivity
• Remote access gateway connectivity
• Uses IPsec (VPN)

• Charge-back
• Configuration and usage data preserved across live migration

• Discover service
  • DC, DNS, DHCP
• Organize, assign, monitor and manage IP addresses
• Port mirroring
  • Traffic analysis

http://www.server-log.com/blog/2012/9/10/set-up-a-converged-network-for-windows-server-2012-hyper-v-f.html

Converged networks is a new functionality in Windows Server 2012 which allows the creation of virtual network adapter (normally used for virtual machines) in the parent partition (management OS).

• Converged network interfaces are often created from bonded NIC teams
• PowerShell must be used to create converged networks

Get-NetAdapter | sort Name

First, a new Hyper-V virtual switch needs to be created. The switch is created with the “Weight” mode in order to guarantee a minimum amount of network bandwidth for the cluster networks.

New-VMSwitch "ConvergedVMSwitch" -MinimumBandwidthMode Weight -NetAdapterName "ConvergedNicTeam"

Next, we check that the Hyper-V Extensible Virtual Switch is bound to the correct network adapter.

Get-NetAdapterBinding | where {$_.DisplayName -like "Hyper-V*"}

By default, a virtual management NICs is also created when a VM switch is created using this PowerShell cmdlet. This NIC is required because all NICs were used for the NIC team and the team is the Hyper-V virtual switch. Without, the virtual management NIC, you would no longer have access to the Hyper-V host itself.