NIC Teaming, also called “Load Balancing and Fail-Over” (LBFO) or “Link Aggregation” or “IEEE 802.1AX-2008”, groups multiple interfaces to provide fault tolerance and load balancing for Network Interface Cards (NIC) connecting Windows Server to the network. This aggregation combines the individual capacity of multiple interface cards to form a high performance virtual link so the failure of an individual port or adapter does not cause a loss of connectivity. Below is a picture from Wikipedia.org on how a typical NIC teaming looks like:
The Microsoft support position on NIC teaming for Windows Server 2008 (deployed either in a physical environment or virtualized environment with Hyper-V) is that hardware and driver support is provided by the hardware manufacturer as outlined in KB Article 254101.
Alex, one of our test engineers, spent some time researching Broadcom Advanced Control Suite (BACS) version 11.6.10 with Broadcom Advanced Server Program (BASP) NICs, and found out that he could actually make NIC teaming work with his Hyper-V hosts and have VMM manage the BASP NICs.
Here is the blog he posted for what he has experimented and his step-by-step notes on how he made it work for him.
Hope this is useful information for you!
Enjoy your reading,
Looking for BACS version 11.6.10, having a hard time finding it, can you provide any help?
Did you use live.com? :-) Here it is:
search.live.com/results.aspx (the first link should take you to the download page directly).
Ein interessantes Thema im Bereich Server Virtualisierung ist NIC Teaming. Hier geht es darum 2 physikalische
BACS support VLAN taggin? is a pretty important issue if don't support
By the way BACS needs framework 2.0...more trash in our systems..