Teaming and failover policies allow you to determine how network traffic is distributed between adapters and how to reroute traffic in the event of an adapter failure.


Browse to a distributed switch in the vSphere Web Client.


Right-click the distributed switch, and select Manage Distributed Port Groups.


Select the Teaming and failover check box and click Next.


Select the port group that you want to edit and click Next.


Edit the teaming and failover settings for the distributed port group.



Load balancing

Specify how to choose an uplink.

Route based on the originating virtual port. Based on the virtual port where the traffic entered the virtual switch.

Route based on IP hash. 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.

Route based on source MAC hash. Based on a hash of the source Ethernet.

Route based on Physical NIC Load. Based on the current load of the physical network adapters connected to the port group. If an uplink remains busy at 75% or higher for 30 seconds, the host proxy switch moves a part of the virtual machine traffic to a physical adapter that has free capacity.

Use explicit failover order. Always use the highest order uplink from the list of Active adapters which passes failover detection criteria.


IP-based teaming requires that the physical switch be configured with etherchannel. For all other options, disable etherchannel.

Network failover detection

Specify the method to use for failover detection.

Link Status only. Relies solely on the link status that the network adapter provides. Detects failures, such as cable pulls and physical switch power failures, but not configuration errors, such as a physical switch port being blocked by spanning tree or that is misconfigured to the wrong VLAN or cable pulls on the other side of a physical switch.

Beacon Probing. Sends out and listens for beacon probes on all NICs in the team and uses this information, in addition to link status, to determine link failure.

Notify switches

Select Yes or No from the drop-down menu to notify switches in the case of failover.

If you select Yes, whenever a virtual NIC is connected to the distributed switch or whenever that virtual NIC’s traffic would be routed over a different physical NIC in the team because of a failover event, a notification is sent over the network to update the lookup tables on physical switches.


Do not use this option when the virtual machines connected to the port group are using Microsoft Network Load Balancing in unicast mode.


Select Yes or No to disable or enable failback.

This option determines how a physical adapter is returned to active duty after recovering from a failure.

Yes (default). The adapter is returned to active duty immediately upon recovery

No. A failed adapter is left inactive even after recovery until another currently active adapter fails, requiring its replacement.

Failover order

Specify how to distribute the work load for uplinks. To use some uplinks but reserve others in case the uplinks in use fail, use the up and down arrows to move them into different groups:

Active adapters. Continue to use the uplink when the network adapter connectivity is up and active.

Standby adapters. Use this uplink if one of the active adapter’s connectivity is down.

Unused adapters. Do not use this uplink.


Review your settings and click Finish.

Use the Back button to edit any of your selections.