Does Hyper-V support NIC Teaming?

Does Hyper-V support NIC Teaming?
Help_NTIAsked:
Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

OriNetworksCommented:
However, there are work around such as with HP's Network Utility.
0
OriNetworksCommented:
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
Problems using Powershell and Active Directory?

Managing Active Directory does not always have to be complicated.  If you are spending more time trying instead of doing, then it's time to look at something else. For nearly 20 years, AD admins around the world have used one tool for day-to-day AD management: Hyena. Discover why

Help_NTIAuthor Commented:
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
Help_NTIAuthor Commented:
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
mukulagCommented:
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
Help_NTIAuthor Commented:
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
Computer101Commented:
PAQed with points refunded (500)

Computer101
EE Admin
0

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Microsoft Server OS

From novice to tech pro — start learning today.

Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.