This article provides information on configuring NIC teaming.
A NIC team can share the load of traffic between physical and virtual networks among some or all of its members, as well as provide passive failover in the event of a hardware failure or network outage.
To utilize NIC teaming, two or more network adapters must be uplinked to a virtual switch. The main advantages of NIC teaming are:
Increased network capacity for the virtual switch hosting the team.
Passive failover in the event one of the adapters in the team goes down.
Observe these guidelines to choose the correct NIC Teaming policy:
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 an 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 a 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.
Route based on physical NIC load (Only available on Distributed Switch): Choose an uplink based on the current loads of physical NICs.
The NIC team used for the virtual machine network provides extra capacity as well as failover, and keeps the portgroup connected to the network if one of the network adapters fails. The VMotion uplink is ideally connected to its own subnet along with other ESX server hosts' vMotion ports to separate its traffic from the virtual machine and Service Console traffic, and to maximize performance.
An additional network adapter can be uplinked to virtual switch 1 to provide for failover on the Service Console (management) interface, or to a new virtual switch 4 to provide for iSCSI or NFS storage (ideally on its own subnet).