Network adapter teaming (where two or more network interface cards work together as one and appear as a single, separate device) provides a GSX Server host and the virtual machines running on it with a level of network hardware fault tolerance. Should one physical network adapter fail, network traffic for the host and virtual machines can continue using the remaining network adapters in the team.

Another method for providing fault tolerance is by making sure that automatic bridging is enabled. This feature is available on Windows hosts only and is enabled by default. For more information, see Configuring Bridged Networking Options on a Windows Host. This method is more limited than using NIC teaming, as it does not allow for load balancing, switch fault tolerance, fault tolerance to any necessary services running on the host or the ability to specify an adapter as the primary or secondary adapter.

Certain NIC teaming modes provide load balancing and are discussed below.

If your GSX Server host is configured to use teamed network interface cards, and you use bridged networking with your virtual machines, you need to adjust your network settings. You do this by binding the VMware Bridge Protocol to the teamed NIC and unbinding it from each individual, physical NIC on the host. See Setting Up the Windows Host.

Before you start using teamed NICs to network your virtual machines, you should have a good understanding of how network teaming works in your host environment.

VMware supports teamed NICs on Windows hosts with enterprise class network adapters that can be configured for NIC teaming. If there is a specific teamed networking mode (such as 802.3ad Dynamic or 802.3ad-Draft Static mode) you want to use, then you should use adapters that support that mode.

VMware has not tested and does not support network adapter teams with GSX Server on Linux hosts.

GSX Server supports teamed Broadcom-based network adapters when used with Broadcom teaming software in the following modes:

GSX Server supports teamed Intel-based network adapters when used with Intel PROSet version 6.4 or higher (32-bit hosts) or PROSet version 10.0 or higher (64-bit hosts) in the following modes:

When using GSX Server on a Windows host with teamed network adapters and bridged networking, the VMware Bridge Protocol must be bound to the teamed network adapter and unbound from the individual physical network adapters. Complete the following steps.

1. Open the Windows Control Panel, then open Network Connections (on a Windows Server 2003 host) or open Network and Dial-up Connections (on a Windows 2000 host).

2. To bind the VMware Bridge Protocol to the teamed NIC, right-click the teamed NIC device and choose Properties. Check VMware Bridge Protocol, then click OK to close the property sheet.

3. To unbind the VMware Bridge Protocol from each physical NIC that is being used for bridged networking, right-click the NIC device and choose Properties. Clear the VMware Bridge Protocol check box, then click OK to close the property sheet.

Alternately, you can use the Virtual Network Editor to either map the teamed NIC to VMnet0 or exclude the physical adapters from any automatic bridging by GSX Server. For information, see Configuring Bridged Networking Options on a Windows Host.

If you change the teamed networking mode, you must delete the original NIC team on the host and create a new team. Do not modify a virtual machine's NIC teaming settings.