Link aggregation
From Wikipedia, the free encyclopedia
Link aggregation, or IEEE 802.3ad, is a computer networking term which describes using multiple Ethernet network cables/ports in parallel to increase the link speed beyond the limits of any one single cable or port, and to increase the redundancy for higher availability. Other terms for this include "Ethernet trunk", "NIC teaming", "port teaming", "port trunking", "EtherChannel", "MLT", "NIC bonding", and "link aggregate group" (LAG). Most implementations now conform to clause 43 of IEEE 802.3 standard, informally referred to as "802.3ad".
Contents |
[edit] Trunking and the network backbone
Link aggregation is an inexpensive way to set up a high-speed backbone network that transfers much more data than any one single port or device can deliver. This allows several devices to communicate simultaneously at their full single-port speed while not allowing any one single device to monopolize all available backbone capacity.
Link aggregation also allows the network's backbone speed to grow incrementally as demands on the network increase without having to replace everything and buy all-new, more expensive hardware.
For most backbone installations, it is common to install more cabling or fiber optic pairs than are initially necessary, even if there is no immediately projected need for the additional cabling. This is done because the cost of labor is much higher than that of the cable and avoids the need for a complete rewiring with more cable, if networking needs change. Link aggregation can allow the use of these extra cables to increase backbone speeds for little or no extra cost.
As of June 2006, 10-gigabit network equipment is becoming available but remains comparatively expensive. With trunking, a network backbone can be established with a speed of up to 8 gigabits while using the much more common gigabit Ethernet switches.
[edit] Trunk size and using ports efficiently
Trunking becomes inefficient beyond a certain bandwidth depending on the total number of ports on the switch equipment. A 24-port gigabit switch with two 8-gigabit trunks is using sixteen of its available ports just for the two trunks, and leaves only eight of its 1-gigabit ports for other devices. This same configuration on a 48-port gigabit switch leaves 32 1-gigabit ports available, and so it is much more efficient (assuming of course that those ports are actually needed at the switch location).
When 40-50% of the switch ports are being utilized for backbone trunking, upgrading to a switch with either more ports or a higher base-operating speed may be a better option than simply adding more switches, especially if the old switch can be re-used elsewhere on a less performance critical part of the network.
[edit] Trunking of network interface cards
Trunking is not just for the core switching equipment. Network interface cards (NICs) can also sometimes be trunked together to form network links beyond the speed of any one single NIC. For example, this allows a central file server to establish a 2-gigabit connection using two 1-gigabit NICs trunked together.
Note that when using Microsoft Windows, establishing a trunk with NICs usually only works among certain NIC types, and all must usually be of the same brand.[citation needed] The trunk itself is typically established at the device driver or NDIS level.
In Linux, Ethernet bonding (trunking) is implemented on a higher level, and can hence deal with NICs from different manufacturers or drivers, as long as the NIC is supported by the kernel.
[edit] Trunking of different types of cabling and speeds
Typically the ports used in a trunk should be all of the same type, such as all copper ports (CAT-5E/CAT-6), all multi-mode fiber ports (SX), or all single-mode fiber ports (LX).[citation needed]
The ports also need to operate at the same speed. It is possible to trunk 100-megabit ports together, but trunking a 100-megabit port and a gigabit port together will most likely not work,[citation needed] even though mixing port sizes within a trunk is technically supported in the 802.3ad standard.
[edit] Trunking support and cross-brand compatibility
 |
This article or section may be confusing or unclear for many readers. Please improve the article or discuss this issue on the talk page. This article has been tagged since February 2007. |
A limitation on link aggregation is that an Ethernet network must maintain the sequential order of Ethernet packets.[citation needed] Different techniques have been used to maintain this order.
Most gigabit trunking is now based on clause 43 of the IEEE 802.3 standard added in March 2000 by the IEEE 802.3ad task force.[1] Other proprietary trunking protocols existed before this standard was established. Some examples include Cisco's Port Aggregation Protocol (PAgP), Adaptec's Duralink trunking, and Nortel MLT MultiLink Trunking. These custom trunking protocols typically only work for interconnecting equipment from the same manufacturer or product line.
Even though many manufacturers now implement the standard, issues may occur (for example Ethernet auto-negotiation[2]). Testing before production implementation is prudent.
Intel has released a package for Linux called Advanced Networking Services (ANS) to bind Intel Fast Ethernet and Gigabit cards.[3] Also, newer Linux kernels support bonding between NICs of the same type.
[edit] References
- ^ IEEE 802.3ad Link Aggregration Task Force
- ^ Carrier Ethernet World Congress Interoperability Report p11
- ^ Intel Advanced Networking Services
