Hyper-V 2012 R2 Network Architectures Series (Part 1 of 7) – Introduction

Hi Virtualization gurus,

Since 6 months now, I’ve been working on the internal readiness about Hyper-V Networking in 2012 R2 and all the options and functionalities that exists and how to make them work together and I realize that a common question in our team or from our customers is what are the best practices or the best approaches when defining the Hyper-V Network Architectures of your Private Cloud or your Virtualization farm. Hence I decided to write this series of posts that I think they might be helpful at least to do the brainstorm to find the best approach for every particular scenario. The reality is that each environment is different and use different hardware, but at least I can help you identify 5 common scenarios on how to squeeze the performance of your hardware.

I want to make clear that there is no just one right answer or configuration  and your hardware can help you determine the best configuration for a robust, reliable and performer Hyper-V Network Architecture.  Please note that I will do some personal recommendation based on my experience. These recommendations might or might not be the official – generic recommendations from Microsoft, so please call you support contact in case of any doubt.

The series will contain these post:

1. Hyper-V 2012 R2 Network Architectures Series (Part 1 of 7 ) – Introduction (This Post)

2. Hyper-V 2012 R2 Network Architectures Series (Part 2 of  7) - Non-Converged Networks, the classical but robust approach

3. Hyper-V 2012 R2 Network Architectures Series (Part 3 of  7) – Converged Networks Managed by SCVMM and Powershell

4. Hyper-V 2012 R2 Network Architectures Series (Part 4 of 7 ) – Converged Networks using Static Backend QoS

5. Hyper-V 2012 R2 Network Architectures Series (Part 5 of 7) – Converged Networks using Dynamic QoS

6. Hyper-V 2012 R2 Network Architectures Series (Part 6 of 7 ) – Converged Network using CNAs

7. Hyper-V 2012 R2 Network Architectures Series (Part 7 of 7 ) – Conclusions and Summary

8. Hyper-V 2012 R2 Network Architectures (Part 8 of 7) – Bonus

Comments (7)
  1. Recep YUKSEL says:

    Thank you Cristian Edwards.

  2. Anonymous says:

      ** Newly updated to include 2012 R2 Best Practices. See 11/03/2013 blog regarding R2 updates by

  3. Anonymous says:

    Pingback from A collection of Windows Server 2012 R2 / Hyper-V Server 2012 R2 links and related articles | Ahmad Sabry ElGendi

  4. Sreenath Gupta says:

    Dear Hyper-V team,

    we are facing very horrible situation with hyper-v 2012 performance, we have installed hyperv 2012 on Dell R820 server and the performance is very bad, for the first hour everything is good, after sometime, i am facing network latency issue and i am getting
    more than 10 ms, i have seen lot many articles and blog to find out the issue but i could not, kindly help us to solve the problem.

    Dell Team has even disabled the VMQ from the BACS4 console still the same problem.

    Dell team has connected the server through IDrac and they have even updated all the firmwares and drivers, still the same problem no improvement, kindly resolve asap.

  5. Edward ho says:

    Probably tcp offload

  6. ian_pick says:

    I would absolutely love a downloadable copy of this entire series for reference. With all the HyperV books, help, walkthroughs, etc., online that I’ve been reading since November, not -one- of them covered the networking aspect like this, and this was
    exactly what I needed.

  7. Suen says:

    I have Laptop with Server 2012 R2 Hyper-V install BSD . How to let BSD can ping to my laptop network adapter.
    BSD network adapter is . 2012 R2 Server Network Adapter IP is

Comments are closed.

Skip to main content