How to configre 4-port NIC for standalone Hyper-V server

hyper-v

I would like to ask you guys for help/hint/recommendation regarding 4-port NIC configuration prior to installing Hyper-V role on my HP DL380 server.

I have 2 boxes on the network:

  1. DC: Server 2012 Standard (AD,DNS,DHCP)
  2. Hyper-V host Server 2012 Standard (DL380), joined to the domain.

This Hyper-V host has 4-port NIC. My goal is to host 2 virtual machines: another domain controller and Exchange 2013 Standard for 40 users. All files related to virtual machines will be stored on RAID5 local drive, there is no iSCSI SAN nor DAS, therefore I believe I don't need to use NICs for iSCSI. I'm also not sure of using NIC for Live Migration etc. as this should remain standalone Hyper-V server (no cluster).

What is your recommendation for using 4 NICs (4×1 Gb ports) with Hyper-V STANDALONE server (not cluster) ?

Should I take in consideration NIC Teaming? (better performance?)

Best Answer

Usually on a Hyper-V server extra NICs are used for:

  • Live migration (often gets its own LAN, since it will have extremely heavy traffic when migrating)
  • Cluster communications (again, own LAN so nothing else interferres or causes high latency)
  • Storage network, if using iSCSI
  • Management network, if you have a seperate management network
  • The host system
  • Dedicated to specific VMs

Since you don't intend to run a cluster, I would setup

  • One port dedicated to the host OS, so anything that breaks in the VMs shouldn't interfere with you accessing the host
  • Two ports in a team for the VMs, either load balancing or active/standby, depending on card and switch support. Active/standby doesn't help increase capacity, but saves you if a port on the NIC or switch dies, or a cable breaks. It may also let you have redundant switches
  • One port left unused. If one of your VMs turns out to need more network performance, you have the option of dedicating this port to that VM later on.
Related Topic