Microsoft has published an technical article giving network recommendations for building a Hyper-V cluster in Windows Server 2012. The guide provides network configuration recommendations that are specific to a Hyper-V cluster that is running Windows Server 2012. It includes an overview of the different network traffic types, recommendations for how to isolate traffic, recommendations for features such as NIC Teaming, Quality of Service (QoS) and Virtual Machine Queue (VMQ), and a Windows PowerShell script that shows an example of converged networking, where the network traffic on a Hyper-V cluster is routed through one external virtual switch.
The solution which should be highly available should have a network design which meets the following goals:
- Ensure network quality of service
- Provide network redundancy
- Isolate traffic to defined networks
- Take advantage of Server Message Block (SMB) Multichannel, where applicable
The technical article covers the following topics:
- Overview of different network traffic types
- How to isolate the network traffic on a Hyper-V cluster
- NIC Teaming (LBFO) recommendations
- Quality of Service (QoS) recommendations
- Virtual machine queue (VMQ) recommendations
- Example of converged networking: routing traffic through one Hyper-V virtual switch
- Appendix: Encryption