Congratulations. You reached the last of these 7 posts covering the most common Hyper-V Network Architectures today. Maybe you don’t remember all the pros/cons and caveats on each case, but don’t worry. I’ve built this table that summarizes the most important factors to consider when deciding which Hyper-V Network Architecture you want to use. As I said from the beginning, there is not one unique best practice but different options for different situations or needs. Each column in the table represents an important factor to consider and each row represents the 5 scenarios covered in the Series. I’ve added a last column to categorize each scenario based on Performance and Throughput. I find it useful to explain the differences and I hope you find it useful as well. I personally prefer the Non-Converged Network Architecture if possible and affordable but there is no reason to discard the other options if you know how the end to end solution works and how the different pieces in the backend and Windows interact with each other.
RSS and VMQ
Standardized INF Keywords for RSS
Standardized INF Keywords for VMQ
VMQ Deep Dive
NIC Teaming Whitepapers
Windows Server 2012
Windows Server 2012 R2
Hyper-V Virtual Switch
Nice post Christian. I would point out however, that dedicated management CAN be done in a converged network with VMM design, provided there is an addition NIC or pair of NICs available. I just finished implementing one such design for a customer. I personally am a strong advocate for the converged networking with VMM approach.
Hi Wes. As I mentioned, there are almost unlimited combinations but these 5 are the most common ones in general. Regarding your approach, you will have RSS for MGMT, but how you manage the CSV and LM? Over the Converged Network with vNICs right? and what sVMQ setup are you using?