Failover and load balancing policies allow you to determine how network traffic is distributed between adapters and how to re-route traffic in the event of an adapter failure.

1

Log in to the vSphere Client and select the host from the inventory panel.

2

Click the Configuration tab, and click Networking.

3

Select a vSwitch and click Properties.

4

In the vSwitch Properties dialog box, click the Ports tab.

5

To edit the failover and load balancing values for the vSwitch, select the vSwitch item and click Properties.

6

Click the NIC Teaming tab.

You can override the failover order at the port group level. By default, new adapters are active for all policies. New adapters carry traffic for the vSwitch and its port group unless you specify otherwise.

7

Specify the settings in the Policy Exceptions group.

Option

Description

Load Balancing

Specify how to choose an uplink.

Route based on the originating port ID. 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.

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.

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. 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. This detects many of the failures previously mentioned that are not detected by link status alone.

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 vSwitch 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. No such issue exists with NLB running in multicast 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. If you want to use some uplinks but reserve others for emergencies in case the uplinks in use fail, set this condition by moving them into different groups:

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

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

Unused Uplinks. Do not use this uplink.

8

Click OK.