• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 269
  • Last Modified:

How do I properly setup Teaming and Virtual Switches on Hyper-V Server 2012 R2

I have a Server 2012 R2 Data Center edition and I loaded Hyper-V. My server has 4 physical NIC's. Based off another recommendation I named one VM for virtual machine traffic, another management, another cluster and the last live migrations. The idea being I would send specific traffic over each physical NIC but I wanted to Team the NIC's for bigger bandwidth. So I Teamed all four in Switch Independent Mode with Dynamic Load Balancing.

Then I went to Roles and installed the Hyper-V role. It ask me to create a Virtual Switch when installing the role. The options are to select one of the individual NIC's or to Select the Team that covers all of them. What is the proper way to set this up or best practice?
0
aando
Asked:
aando
  • 2
  • 2
3 Solutions
 
VB ITSSpecialist ConsultantCommented:
Best practice would be to install another 4 NICs for some redundancy.

Have 1 NIC for management, 1 NIC for live migrations, then assign the rest to NIC Teams for the cluster and VMs. The amount of NICs you assign to each of these Teams is your call. If you think you need more bandwidth for your cluster then assign more NICs to this Team over the Team for your VMs.

With the above scenario, you would simply use the VM NIC Team for the Hyper-V Virtual Switch.
0
 
Philip ElderTechnical Architect - HA/Compute/StorageCommented:
You can team them as follows:
 + 2 Ports: Management Team (shared with Live Migration)
 + 2 Ports: vSwitch (not shared with host OS)

New-NetLbfoTeam is the PowerShell to use.
Get-NetAdapter is the PoSh to use to figure out which port is which.
0
 
aandoAuthor Commented:
So are we saying I need to un-team the 4 and set it up differently? I don't really want to add 4 more to this.
0
 
Philip ElderTechnical Architect - HA/Compute/StorageCommented:
Two teams with two ports per team is how we set ours up as a bare minimum. We install two i350T4 NICs by default so end up with a bit more flexibility across 8 ports.
0
 
aandoAuthor Commented:
I was looking more of how to fix what I have not necessarily add to it but they both gave some best practices from different aspects.
0

Featured Post

Simplify Active Directory Administration

Administration of Active Directory does not have to be hard.  Too often what should be a simple task is made more difficult than it needs to be.The solution?  Hyena from SystemTools Software.  With ease-of-use as well as powerful importing and bulk updating capabilities.

  • 2
  • 2
Tackle projects and never again get stuck behind a technical roadblock.
Join Now