Physical NICs, at least two, combined behind one virtual switch so that a failed link is covered and, with certain load-balancing algorithms, more bandwidth is available. VCF sets port groups to Route based on physical NIC load by default; for vSAN, teaming provides failover only.
Read more: Broadcom TechDocs
In the Ultra Transcenders books
Each book explains NIC teaming in context, with comparison tables and the common traps.
Terms in this definition
- Physical
Describes the concrete, real-world parts that put a logical architecture into effect.
- LEAST
Pass up to 254 expressions to this T-SQL function and it hands back whichever is smallest. Both Fabric Warehouse and SQL analytics endpoints support it.
- Virtual switch
An AHV construct for managing bridges and uplinks, made of nodes plus their uplink ports with one OVS bridge pooled across them. It covers either one cluster or several.
- VMware Cloud Foundation
Broadcom's platform for private cloud. It unifies management of NSX, vSAN, vSphere, VCF Automation and VCF Operations as one fleet; VVF, by contrast, lacks automation and cloud management.
- NIC
Network interface card, the network interface of a VM; NSGs can be associated with it.
- ELT
Extract, load, transform: raw data lands in the target system first and is transformed there. See ETL for the opposite order.
- vSAN
VMware's software-defined storage, which combines local devices across a cluster's ESX hosts into one shared datastore. Available as OSA or ESA, VCF can use it as principal storage.
- failover
Switching workloads from production VMs over to replicas at the recovery site; replica, CDP replica and storage plans do this. The plan is left in FAILOVER until it is undone, made permanent or followed by failback.