6.0

6 (Optional) Expand NIC teaming and congure the following components.
Option Description
Load Balancing
Specify how to choose an uplink.
n
Inherit from vSwitch. Choose the uplink that is selected for the
associated virtual 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 osets 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 originating port ID. Choose an uplink based on the
originating port ID.
n
Use explicit failover order. Always use the highest order uplink from
the list of active adapters which passes failover detection criteria .
N IP-based teaming requires the physical switch to be congured
with etherchannel. For all other options, etherchannel must be disabled.
Network Failover Detection
Specify the method to use for failover detection.
n
n
Inherit from vSwitch. Inherits the respective conguration of the
associated virtual switch.
n
Link Status only. Relies only on the link status that the network
adapter provides. This option detects failures, such as cable pulls and
physical switch power failures, but not conguration errors, such as a
physical switch port being blocked by a spanning tree or that is
miscongured to the wrong VLAN or cable pulls on the other side of a
physical switch.
n
Beacon only. 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 that are not
detected by link status only.
N Do not use beacon probing with IP-hash load balancing.
Notify Switches
Select Yes, No, or Inherit from vSwitch to notify switches in the case of
failover.
If you select Yes, when a virtual NIC is connected to the distributed switch
or that virtual NIC’s trac is routed over a dierent physical NIC in the
team because of a failover event, a notication is sent out over the network
to update the lookup tables on physical switches. In almost all cases, this
process is preferred for the lowest latency of failover occurrences and
migrations with vMotion.
N 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.
vSphere Single Host Management - VMware Host Client
110 VMware, Inc.