Teaming NICs? when server has only two NICs and host VHD on iSCSI

すべての返信

• 2012年5月3日 5:37

  モデレータ

   

   
  

  0

  Hi,

  First of all, it is recommended that you have a read of the following guide for Hyper-V networking.

  How does basic networking work in Hyper-V?

  http://blogs.technet.com/jhoward/archive/2008/06/16/how-does-basic-networking-work-in-hyper-v.aspx

  By the way, general speaking , it is recommended that you dedicate one physical network adapter for Hyper-V host management. It is also recommended that you use dedicate network adapters and switch for iSCSI storage.

  
  

  • 編集済み Vincent HuModerator 2012年5月3日 5:38
  • 回答としてマーク Kilimats 2012年5月3日 21:41
  •  
  • 返信
  • 引用

   
• 2012年5月3日 8:08

   

   
  

  0
  beside the supposed seperation from lan and san traffic, it is also not suggested to team nics for iSCSI, the prefered way to have fault tolerance/load balancing is MPIO. I would suggest adding a dual or quad port nic, depending if you want to seperate the management as well from the normal lan traffic (though from my experience there isnt much impact, at least in R2)
  • 返信
  • 引用

   
• 2012年5月3日 15:37

   

   
  

  0

  Hi,

  I need to setup a single HyperV server with VHD hosted on a Synology SAN using iSCSI block level LUNs (DS1511+)

  That server has only two NICs, we have already completed the teaming and everything seems to work properly, however i am wondering if the performance will slow down due to the fact that every outgoing/incoming traffic will come through a single teamed NIC, thus creating congestion i think...

  For example, here is what will happen with a VHD virtual file server hosted on that SAN (correct me if i'm wrong)

  1- a user copy a file from a shared folder to another located on that same file server

  2- the Hyperv server gets the request from the teammed NIC

  3- HyperV send the request to the SAN through the teammed NIC again

  4- The SAN get the request and send the file transfer copy to the HYPERV team NICs again and back to the file server using the same path

  5- ETC

  Its going to create a lot of congestion, correct? Is it better to dedicate one NIC for HyperV and one for the iscsi SAN VHD host ?

  Splitting networks in this way is a waste of resources. Configure iSCSI to use BOTH networks for performance and redundancy and route Hyper-V non-SAN traffic using one of them (can configure VLANs and apply QoS rules of available).

  -nismo

  • 返信
  • 引用

   
• 2012年5月3日 15:58

   

   
  

  0

  Thanks for the feedback guys, two of you are saying i should not use teaming and one says i should...still confused...

  Is there any benchmark out there showing which configuration perform best?

  • 返信
  • 引用

   
• 2012年5月3日 16:07

   

   
  

  0

  teaming is ok (if the vendor supports it for hyper-v, microsoft doesnt support it and directs to the vendor if they support it) for lan traffic.

  for iscsi traffic, there is MPIO (see this whitepaper for general description http://www.microsoft.com/downloads/details.aspx?FamilyID=CBD27A84-23A1-4E88-B198-6233623582F3&displaylang=en&displaylang=en) which handles distribution of the traffic among multiple adapters differently.

  though you cant use mpio and teaming on the same adapters, thats why the suggestion to buy an additional nic

  • 返信
  • 引用

   
• 2012年5月3日 21:26

   

   
  

  0

  Thanks for the feedback guys, two of you are saying i should not use teaming and one says i should...still confused...

  Is there any benchmark out there showing which configuration perform best?

  I have an impression all of us told you not to team NICs to run iSCSI on top.

  -nismo

  
  

  • 編集済み VR38DETTMicrosoft Community Contributor 2012年5月3日 21:27
  •  
  • 返信
  • 引用

   
• 2012年5月3日 21:41

   

   
  

  0

  Thanks for the feedback guys, two of you are saying i should not use teaming and one says i should...still confused...

  Is there any benchmark out there showing which configuration perform best?

  I have an impression all of us told you not to team NICs to run iSCSI on top.

  -nismo

  
  

  I misunderstood your reply then, my bad. I'll get rid of the teaming in place and have one NIC for HyperV and one NIC for iSCSI
  • 返信
  • 引用