6.0

10 (Optional) In the Teaming and Failover group specify the following.
Option Description
Load Balancing
Specify how to choose an uplink.
n
Route based on the originating virtual port — Choose an uplink
based on the virtual port where the traffic entered the distributed
switch.
n
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.
n
Route based on source MAC hash — Choose an uplink based on a
hash of the source Ethernet.
n
Route based on physical NIC load — Choose an uplink based on the
current loads of physical NICs.
n
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.
n
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.
n
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.
NOTE Do not use beacon probing with IP-hash load balancing.
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. 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:
n
Active Uplinks — Continue to use the uplink when the network
adapter connectivity is up and active.
n
Standby Uplinks — Use this uplink if one of the active adapter’s
connectivity is down.
n
Unused Uplinks — Do not use this uplink.
NOTE When using IP-hash load balancing, do not configure standby
uplinks.
vSphere Administration with the vSphere Client
282 VMware, Inc.