NIC teaming in ESXi/ESX (1004088)
This article discusses how to configure 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.
Sample environment using four network adapters:
Virtual switch Portgroup # Uplinks
1 Service Console 1
2 Virtual Machine 2
3 VMotion 1
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).
For translated versions of this article, see:
create-network-redundancy create-nic-load-balancing no-redundant-connectivity uneven-network-utilization
- ESX/ESXi host requirements for link aggregation
- Specifying or changing the NIC teaming policy from the command line in ESX/ESXi 4.x and ESXi 5.0
- Equipos de NIC en ESXi y ESX
- Equipe da NIC no ESXi e ESX
- NIC Teaming: Load balancing based on v-port ID