Go Premium for a chance to win a PS4. Enter to Win

x
?
Solved

Does Hyper-V support NIC Teaming?

Posted on 2008-10-31
9
Medium Priority
?
5,061 Views
Last Modified: 2013-11-11
Does Hyper-V support NIC Teaming?
0
Comment
Question by:Help_NTI
9 Comments
 
LVL 17

Expert Comment

by:OriNetworks
ID: 22876350
However, there are work around such as with HP's Network Utility.
0
 
LVL 17

Expert Comment

by:OriNetworks
ID: 22876367
To clarify, what I have understood is that you cannot directly manage via Hyper-V but your vendors should supply utilities that allow you to manage this functionality.
0
Microsoft Certification Exam 74-409

Veeam® is happy to provide the Microsoft community with a study guide prepared by MVP and MCT, Orin Thomas. This guide will take you through each of the exam objectives, helping you to prepare for and pass the examination.

 

Author Comment

by:Help_NTI
ID: 22879092
NIC teaming works well in Windows Server 2008 but we are having difficulties on its features when it comes to Hyper-V's Virtual Machines. The VM loses connection when we disconnect one of the NICs but the Windows Server 2008 does not. Any ideas?

Thank you!
0
 

Author Comment

by:Help_NTI
ID: 22879158
Additionally, our two NICs are Broadcom and supports NIC teaming in Windows Server 2008 but we guess NOT in Hyper-V's VMs? Please advise, thanks.
0
 
LVL 4

Expert Comment

by:mukulag
ID: 23007796
Microsoft does not "support" NIC teaming.  Support for NIC teaming must be provided by the OEM of the NIC or server product.
Due to a number of factors, most NIC teaming implementations (i.e. HP, Dell, etc.) cannot be supported in conjunction with Hyper-V.  Even if you find a way to get it working the OEM will not support the implementation

http://social.technet.microsoft.com/Forums/en-US/winserverhyperv/thread/5af859d0-d26f-4125-9f24-a52378933d80/
0
 

Author Comment

by:Help_NTI
ID: 23178486
Here is the "Accepted Solution":

http://social.technet.microsoft.com/Forums/en-US/winserverhyperv/thread/5af859d0-d26f-4125-9f24-a52378933d80/

ColinFraser - Posted on Tuesday, July 22, 2008 5:29:10 PM

We had a similar issue in our environment as well. We're running a dell m1000e blade chassis with m600 dual quad cores, 16gb ram, mirrored sas drives, windows 2008 x64 host with multiple windows 2003 32bit guests. The host has broadcom BCM5708S netxtreme II GigE adapters. BACS 3 version 11.0.20.0, NIC driver version 4.1.3.0.

The symptoms in our case were that the guests had no network connectivity off of the host machine. That is to say that the host could ping the guests, the guests could ping the host, but the guests could not ping any other computers on the network and no computers on the network could ping the guests - although other computers could ping the host. If we broke our team and bound the IP to one of the NIC's all would work fine, going back to teaming would break network communications once again.

After much playing we found that the following resolved our issue:
Force speed/duplex, disable IPV4 checksum offload and receive side scaling
Break the team
In hyperv manager remove the virtual network
Recreate the team using the "create team" wizard
team type is smart load balancing
set one adapter to be a secondary adapter
enable auto-fallback disable mode
no vlans in use
In our case the 2 physical Broadcom adapters in Network Connections have only QOS Packet Scheduler and Broadcom Advanced Server Program Driver checked
The team in Network Connections has only Broadcom Advanced Server Program Driver and Microsoft Virtual Network Switch Protocol checked
Go back into hyper-v manager and create a new external virtual network adapter and bind it to the BASP Virtual adapter.
Assign your static ip to the hyper-v external virtual network adapter created above. In properties of the external virtual network adapter everything except Microsoft virtual network switch protocol is checked.

After this was done we found that we now had full network connectivity to the guests and vice versa. Failover also worked beautifully as well in this configuration. Disabling a switch port to the primary nic in the team caused the secondary nic to take over without even dropping a packet. One thing to note - not setting one of the nic's as secondary appears to work fine until you shutdown both switch ports and try to bring them back up - network connectivity is not restored. Configuring the team with one adapter as secondary overcomes this issue.

Hope this helps someone out there...we fooled around with it forever to get it working correctly.

Colin

0
 
LVL 1

Accepted Solution

by:
Computer101 earned 0 total points
ID: 23208842
PAQed with points refunded (500)

Computer101
EE Admin
0

Featured Post

How to Use the Help Bell

Need to boost the visibility of your question for solutions? Use the Experts Exchange Help Bell to confirm priority levels and contact subject-matter experts for question attention.  Check out this how-to article for more information.

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

Scenario:  You do full backups to a internal hard drive in either product (SBS or Server 2008).  All goes well for a very long time.  One day, backups begin to fail with a message that the disk is full.  Your disk contains many, many more backups th…
Resolving an irritating Remote Desktop connection that stops your saved credentials from being used.
This tutorial will show how to push an installation of Backup Exec to an additional server in both 2012 and 2014 versions of the software. Click on the Backup Exec button in the upper left corner. From here, select Installation and Licensing, then I…
This Micro Tutorial hows how you can integrate  Mac OSX to a Windows Active Directory Domain. Apple has made it easy to allow users to bind their macs to a windows domain with relative ease. The following video show how to bind OSX Mavericks to …
Suggested Courses

885 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question