Knowledge Base

The VMware Knowledge Base provides support solutions, error messages and troubleshooting guides
 
Search the VMware Knowledge Base (KB)   View by Article ID
 

NIC teaming in ESXi/ESX (1004088)

Purpose

This article discusses how to configure NIC teaming. A NIC team can share the load of traffic between physical and virtual networks among some or all of its members, as well as provide passive failover in the event of a hardware failure or network outage.

Resolution



To utilize NIC teaming, two or more network adapters must be uplinked to a virtual switch. The main advantages of NIC teaming are:

  • Increased network capacity for the virtual switch hosting the team.
  • Passive failover in the event one of the adapters in the team goes down.
To configure NIC teaming using the vSphere / VMware Infrastructure Client:
  1. Highlight the host and click the Configuration tab.
  2. Click the Networking link.
  3. Click Properties next to the virtual switch.
  4. On the Network Adapters tab, click Add.
  5. Select the appropriate (unclaimed) network adapter(s) and click Next.
  6. Ensure that the selected adapter(s) are under Active Adapters.
  7. Click Next.
  8. Click Finish.
  9. On the Ports tab, highlight the name of the port group and click Edit.
  10. Click the NIC Teaming tab.
  11. The default load balancing policy is Route based on the originating virtual port ID. If the physical switch is using link aggregation, Route based on IP hash load balancing must be used. For more information, see ESX/ESXi host requirements for link aggregation (1001938) and the VMware Virtual Networking Concepts guide.

Observe these guidelines to choose the correct NIC Teaming policy:

  • If the route is based on the originating port ID: Choose an uplink based on the virtual port where the traffic entered the virtual switch.
  • If the route is based on an IP hash: Choose an uplink based on a hash of the source and destination IP addresses of each packet. For non-IP packets, whatever is at those offsets is used to compute the hash.
  • If the route is based on a source MAC hash: Choose an uplink based on a hash of the source Ethernet.
  • If you use explicit failover order: Always use the highest order uplink from the list of Active adapters which passes failover detection criteria.

Note: IP-based teaming requires that the physical switch be configured with EtherChannel. For all other options, EtherChannel should be disabled.

Additional Information

Sample environment using four network adapters:

Virtual switch  Portgroup          # Uplinks
      1         Service Console        1
      2         Virtual Machine        2
      3         VMotion                1

The NIC team used for the virtual machine network provides extra capacity as well as failover, and keeps the portgroup connected to the network if one of the network adapters fails. The VMotion uplink is ideally connected to its own subnet along with other ESX server hosts' VMotion ports to separate its traffic from the virtual machine and Service Console traffic, and to maximize performance.

An additional network adapter can be uplinked to virtual switch 1 to provide for failover on the Service Console (management) interface, or to a new virtual switch 4 to provide for iSCSI or NFS storage (ideally on its own subnet).



For translated versions of this article, see:

Tags

create-network-redundancy create-nic-load-balancing no-redundant-connectivity uneven-network-utilization

See Also

Update History

1/13/2012 - Added link to Virtual Networking Concepts guide and corrected steps. Updated the product list. 07/25/2012 - Corrected steps 4 and 9.

Request a Product Feature

To request a new product feature or to provide feedback on a VMware product, please visit the Request a Product Feature page.

Feedback

  • 44 Ratings

Did this article help you?
This article resolved my issue.
This article did not resolve my issue.
This article helped but additional information was required to resolve my issue.
What can we do to improve this information? (4000 or fewer characters)
  • 44 Ratings
Actions
KB: