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

To override the teaming and failover policy at the port level, enable port-level overrides. See Edit Advanced Distributed Port Group Settings with the vSphere Web Client

1

Browse to a distributed switch in the vSphere Web Client.

2

Click the Manage tab, and select Ports.

3

Select a port from the list.

4

Click Edit distributed port settings.

5

Click Teaming and failover, and select the check box next to the policy that you want to override. Edit the settings for the port.

Note

If you did not enabled port-level overrides, no options are available.

Option

Description

Load Balancing

Select an uplink.

Route based on the originating virtual port. Choose an uplink based on the virtual port where the traffic entered the virtual switch.

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

Route based on source MAC hash. Choose an uplink 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. 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.

Note

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

Network Failover Detection

Select the method to use for failover detection.

Link Status only. Relies solely on the link status that the network adapter provides. This option 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 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 out over the network to update the lookup tables on physical switches. In almost all cases, this process is desirable for the lowest latency of failover occurrences and migrations with vMotion.

Note

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

Failback

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. If failback is set to Yes (default), the adapter is returned to active duty immediately upon recovery, displacing the standby adapter that took over its slot, if any. If failback is set to 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.

6

Click OK.