A server with one network cable has one point of failure that has nothing to do with the server itself — a bad cable, a failed switch port, or a dead NIC takes the whole machine off the network even though every other component is fine. NIC teaming (also called bonding on Linux) combines two or more physical network ports into one logical connection so that failure doesn't happen.
This sits alongside our NIC speed guide (1GbE through 100GbE) and out-of-band management guide — speed decides throughput, out-of-band management decides remote recoverability, and teaming decides whether a single network fault takes the server offline at all.
Two or more physical NICs are presented to the operating system as one logical network interface. Depending on the mode configured, this delivers one or both of two benefits:
| Mode | What it does | Switch requirement |
|---|---|---|
| Active-backup | One NIC active, the other idle until failure — pure redundancy, no throughput gain | None — works with any switch, even unmanaged |
| LACP (802.3ad) | Aggregates bandwidth across links and provides failover | Managed switch with LACP configured on the matching ports |
| Balance-alb / balance-tlb | Software-based load balancing without special switch configuration | None required, but generally less robust than LACP |
Teaming protects against a NIC, cable or switch-port failure. It does not protect against the switch itself failing, unless the two teamed links are deliberately connected to two different switches (a configuration some teaming modes support and others don't) — worth confirming specifically if switch-level redundancy is the actual goal, not just port-level redundancy.
Do I need a managed switch for NIC teaming? Only for LACP. Active-backup mode works with any switch, including an unmanaged one, because only one link carries traffic at a time.
Does teaming double my network speed? Only in aggregation modes like LACP, and even then, a single connection's throughput is typically still limited to one link's speed — aggregation mainly benefits many simultaneous connections, not one large transfer.
Is NIC teaming the same as a redundant PSU? No — different failure domain entirely. A redundant PSU protects against a power-supply failure; NIC teaming protects against a network-path failure. A server built for genuine high availability typically has both.
Do refurbished enterprise servers already have the NICs needed for teaming? Most Dell PowerEdge, HPE ProLiant and Cisco UCS servers from the last decade ship with onboard dual- or quad-port NICs specifically because teaming is an expected use case — check the exact card on the unit you're buying.
Whether it's NIC teaming, redundant power, or RAID-protected storage, a refurbished server should be spec'd for the uptime your business actually needs — not assembled from whatever's cheapest. Browse refurbished servers or talk to us about configuring redundancy correctly, and keep it running with an independent server AMC.
Serverwale · Phone +91-87962-44410 · WhatsApp https://wa.me/918796244410 · Burari, Delhi 110084, India.