Using VMM to manage you Hyper-V NIC teams created with BACS

Using BACS version 11.6.10 you can create NIC teams in you Hyper-V Server to ensure Virtual Machines connectivity and manage your BASP NICs from Virtual Machine Manager. Just follow these easy steps

  1. Remove any existing External Virtual Networks connected to the NICs that are part of the team

  2. Use BACS to create your team, configure the desired team Type, add the NICs involved in the team and add the VLANs you want

  3. Refresh the Host in VMM. Now you should see your BASP Virtual Adapters in the hardware of your host like this:
  4. BASP adapters

  5. Once these adapters show up in your Host in VMM you can create one external Virtual Network for each Virtual BASP Network Adapter

    1. Do not configure any VLANs on these Virtual Networks since the BACS software is in charge of this

    2. When selecting the BASP Virtual Adapter, you must check in the BACS software the Name of the BASP adapter to select the correct one in VMM:
    3. BASP Virtual Network adapters

  6. Connect a VM to the desired Virtual Network adapter.

  7. Now your VM is connected to a VN that provides the Failover and High availability provided by BACS
Note that this is a result of some tests I did on my machines and is not ensured to work in all environments and not officially supported by VMM or Hyper-V

Comments (5)
  1. PnoT says:

    Actually Broadcom 5708 and 5709 worth flawless in Link Aggregation Mode with the latest broadcom drivers on our Dell 1950 and 2950s.  I’ve installed BACS on our Hyper-V Server and can manage the team easily that way.  You need netframework 2.0 in order to install BACS on the server but there is a workaround for it at:

    I’d also recommend making sure you’ve setup your switch for LAG as well but i’m running this configuration as i type this without issue.

    I have yet to get VLANs to work thou and trunking so if anyone has something that i might be missing let me know.

  2. Anonymous says:

    Ein interessantes Thema im Bereich Server Virtualisierung ist NIC Teaming. Hier geht es darum 2 physikalische

  3. Anonymous says:

    Greetings folks, NIC Teaming , also called “Load Balancing and Fail-Over” (LBFO) or “Link Aggregation”

  4. Anonymous says:

    Dans ce bulletin, je vais aborder l’aspect de l’aggrégation de lien aussi appelée “Teaming” sur les plateformes

  5. Anonymous says:

    Broadcom 5708 and 5709 do not work with teaming and Hyper-V.

    This is tested on a Del Blade Center. Drivers are the ones released by Dell on April 2009 (BACS, Virtual Adapter 1.2.10, 5709S The BACS adapter does not support VLAN tagging, therefore you can not use the virtual switch to connect a guest to a vlan. Instead you have to define all your VLANs in the BACS which them crates a virtual adapter for each VLAN and all these adapters use the same MAC address which causes problems with duplicate MAC addresses (e.g. when trying to build a cluster). Furthermore with hyper-v virtual switch teaming with BACS does not work at all. The only model that works (without VLANs) is a pait of active/passive adapters. On the new Dell Blade Centers you can only choose Broadcom network adapters. According to Dell support there is no know date when this situation might change (the current dirver set was just released with those limitations).

    So if you plan to use Hyper-V with high availabiltity –> do not choose Dell Blade Centers.

Comments are closed.

Skip to main content