Menu
Home
People
Places
Arts
History
Plants & Animals
Science
Life & Culture
Technology
Reference.org
EtherChannel
open-in-new
<h2 id="benefits">Benefits</h2> <p>Using an EtherChannel has numerous advantages, and probably the most desirable aspect is the bandwidth. Using the maximum of 8 active ports a total bandwidth of 800 Mbit/s, 8 Gbit/s or 80 Gbit/s is possible depending on port speed. This assumes there is a traffic mixture, as those speeds do not apply to a single application only. It can be used with Ethernet running on twisted pair wiring, single-mode and multimode fiber. </p><p>Because EtherChannel takes advantage of existing wiring it makes it very scalable. It can be used at all levels of the network to create higher bandwidth links as the traffic needs of the network increase. All Cisco switches have the ability to support EtherChannel. </p><p>When an EtherChannel is configured all adapters that are part of the channel share the same Layer 2 (MAC) address. This makes the EtherChannel transparent to network applications and users because they only see the one logical connection; they have no knowledge of the individual links. </p><p>EtherChannel aggregates the traffic across all the available active ports in the channel. The port is selected using a Cisco-proprietary hash algorithm, based on source or destination <a href="/facts/MAC_address/SVcTfgUH">MAC addresses</a>, <a href="/facts/IP_address/z9V22Sw9">IP addresses</a> or <a href="/facts/TCP_and_UDP_port/ygoHVKNC">TCP and UDP port</a> numbers. The hash function gives a number between 0 and 7, and the following table shows how the 8 numbers are distributed among the 2 to 8 physical ports. In the hypothesis of real random hash algorithm, 2, 4 or 8 ports configurations lead to fair load-balancing, whereas other configurations lead to unfair load-balancing. </p> <table><tbody><tr><th>Number of Ports<p>in the EtherChannel </p></th><th>Load Balancing<p>ratio between Ports</p></th></tr><tr><td>8</td><td>1:1:1:1:1:1:1:1</td></tr><tr><td>7</td><td>2:1:1:1:1:1:1</td></tr><tr><td>6</td><td>2:2:1:1:1:1</td></tr><tr><td>5</td><td>2:2:2:1:1</td></tr><tr><td>4</td><td>2:2:2:2</td></tr><tr><td>3</td><td>3:3:2</td></tr><tr><td>2</td><td>4:4</td></tr></tbody></table> <p>Fault-tolerance is another key aspect of EtherChannel. Should a link fail, the EtherChannel technology will automatically redistribute traffic across the remaining links. This automatic recovery takes less than one second and is transparent to network applications and the end user. This makes it very resilient and desirable for mission-critical applications. </p><p><a href="/facts/Spanning_Tree_Protocol/ofHHMBuM">Spanning Tree Protocol</a> (STP) can be used with an EtherChannel. STP treats all the links as a single one and <a href="/facts/Bridge_Protocol_Data_Unit/7aCmFLjU">BPDUs</a> are only sent down one of the links. Without the use of an EtherChannel, STP would effectively shutdown any redundant links between switches until one connection goes down. This is where an EtherChannel is most desirable, it allows use of all available links between two devices. </p><p>EtherChannels can be also configured as <a href="/facts/Virtual_LAN/QhdJNaWX">VLAN trunks</a>. If any single link of an EtherChannel is configured as a VLAN trunk, the entire EtherChannel will act as a VLAN trunk. <a href="/facts/Cisco_Inter-Switch_Link/9kVRqMWA">Cisco ISL</a>, <a href="/facts/VTP/lsg00Vd3">VTP</a> and <a href="/facts/IEEE_802.1Q/nxc5VxI2">IEEE 802.1Q</a> are compatible with EtherChannel. </p> <h2 id="limitations">Limitations</h2> <p>A limitation of EtherChannel is that all the physical ports in the aggregation group must reside on the same switch except in the case of a <a href="/facts/Switch_stack/yaBTy9RV">switch stack</a>, where they can reside on different switches on the stack. <a href="/facts/Avaya/FcS0TJcg">Avaya's</a> <a href="/facts/SMLT/n5D9HW90">SMLT</a> protocol removes this limitation by allowing the physical ports to be split between two switches in a triangle configuration or 4 or more switches in a mesh configuration. Cisco's Virtual Switching System (VSS) allows the creation of a Multichassis Etherchannel (MEC) similar to the <a href="/facts/DMLT/n5D9HW90">DMLT</a> protocol allowing ports to be aggregated towards different physical chassis that form a single <i>virtual switch</i> entity. Also Extreme Networks may do this functionality via M-LAG Multilink Agreggation. Cisco Nexus series of switches allow the creation of a Virtual PortChannel (vPC) between a remote device and two individual Nexus switches. The two Cisco Nexus switches involved in a vPC differ from stacking or VSS technology in that stacking and VSS create a single data and control plane across the multiple switches, whereas vPC creates a single data plane across the two Nexus switches while keeping the two control planes separate. </p> <h2 id="components">Components</h2> <p>EtherChannel is made up of the following key elements: </p> <ul><li>Ethernet links — EtherChannel works over links defined by the <a href="/facts/IEEE_802.3/Q9jxNSNT">IEEE 802.3</a> standard, including all sub-standards. All links in a single EtherChannel must be the same speed.</li> <li>Compatible hardware — the entire line of <a href="/facts/Catalyst_switch/S8pCJH0o">Cisco Catalyst switches</a> as well as <a href="/facts/Cisco_IOS/jwcRuzX8">Cisco IOS</a> software-based routers support EtherChannel. Configuring an EtherChannel between a switch and a computer requires support built into the operating system; FreeBSD, for example, supports EtherChannel via LACP. Multiple EtherChannels per device are supported; the number depends on the type of equipment. <a href="/facts/Catalyst_6500/nGWXIGWA">Catalyst 6500</a> and 6000 switches support a maximum of 64 EtherChannels.<a class="footnote-ref" id="fnref:3" href="#fn:3"><sup>3</sup></a></li> <li>Configuration — an EtherChannel must be configured using the Cisco IOS on switches and router, and using specific drivers when connecting a server. There are two main ways an EtherChannel can be set up. The first is by manually issuing a command on each port of the device that is part of the EtherChannel. This must be done for the corresponding ports on both sides of the EtherChannel. The second way is by using Cisco's <a href="/facts/Port_Aggregation_Protocol/usH7RW40">Port Aggregation Protocol</a> (PAgP) or the IETF's LACP for the automated aggregation of Ethernet ports.</li></ul> <h2 id="etherchannel-vs-8023ad">EtherChannel vs. 802.3ad</h2> <p>EtherChannel and <a href="/facts/Link_aggregation/3BE3qHDT">IEEE 802.3ad</a> standards are very similar and accomplish the same goal. There are a few differences between the two, other than the fact that EtherChannel is Cisco proprietary and 802.3ad is an open standard, listed below: </p><p>Both technologies are capable of automatically configuring this logical link. EtherChannel supports both <a href="/facts/Link_Aggregation_Control_Protocol/3BE3qHDT">LACP</a> and <a href="/facts/Port_Aggregation_Protocol/usH7RW40">Cisco's PAgP</a>, whereas 802.3ad uses <a href="/facts/Link_Aggregation_Control_Protocol/3BE3qHDT">LACP</a>. </p><p>LACP allows for up to 8 active and 8 standby links, whereas <a href="/facts/Port_Aggregation_Protocol/usH7RW40">PAgP</a> only allows for 8 active links. </p> <h2 id="see-also">See also</h2> <ul><li><a href="/facts/Distributed_Split_Multi-Link_Trunking/n5D9HW90">Distributed Split Multi-Link Trunking</a></li> <li><a href="/facts/Link_aggregation/3BE3qHDT">Link aggregation</a></li> <li><a href="/facts/Link_Aggregation_Control_Protocol/3BE3qHDT">Link Aggregation Control Protocol</a></li> <li><a href="/facts/Multi-link_trunking/n5D9HW90">Multi-link trunking</a></li> <li><a href="/facts/R-SMLT/n5D9HW90">R-SMLT</a></li></ul> <ul><li><a href="http://www.intel.com/support/network/sb/CS-009747.htm">"Network Connectivity: Advanced Networking Services — Teaming"</a>. <i><a href="/facts/Intel/SMF0gJJX">Intel</a></i>. 2007-09-13. Retrieved 2007-02-27.</li> <li><a href="http://publib.boulder.ibm.com/infocenter/pseries/v5r3/index.jsp?topic=/com.ibm.aix.commadmn/doc/commadmndita/etherchannel_intro.htm">"EtherChannel and IEEE 802.3ad Link Aggregation"</a>. <i>pSeries and AIX Information Center</i>. <a href="/facts/IBM/QszA7nwd">IBM</a>. 2006. Retrieved 2007-02-27.</li> <li><a href="http://www.cisco.com/en/US/products/hw/switches/ps5023/products_configuration_example09186a00806cb982.shtml">"Cross-Stack EtherChannel on a Catalyst 3750 Switch Configuration Example"</a>.</li></ul> <h2 id="references">References</h2> <ol> <li id="fn:1"><p>"Kalpana Claims A Simple Method For Tackling Ethernet Bottlenecks". Computer Business Review. 1994-03-04. Retrieved 2024-05-24. <a href="https://techmonitor.ai/technology/kalpana_claims_a_simple_method_for_tackling_ethernet_bottlenecks" target="_blank">https://techmonitor.ai/technology/kalpana_claims_a_simple_method_for_tackling_ethernet_bottlenecks</a> <a href="#fnref:1" class="footnote-back-ref">↩</a></p></li> <li id="fn:2"><p>"IEEE 802.3ad Link Aggregation Task Force". www.ieee802.org. Archived from the original on 27 October 2017. Retrieved 9 May 2018. <a href="http://www.ieee802.org/3/ad/" target="_blank">http://www.ieee802.org/3/ad/</a> <a href="#fnref:2" class="footnote-back-ref">↩</a></p></li> <li id="fn:3"><p>Understanding EtherChannel Load Balancing and Redundancy on Catalyst switches — Cisco Systems <a href="http://www.cisco.com/en/US/tech/tk389/tk213/technologies_tech_note09186a0080094714.shtml#ioscat4k" target="_blank">http://www.cisco.com/en/US/tech/tk389/tk213/technologies_tech_note09186a0080094714.shtml#ioscat4k</a> <a href="#fnref:3" class="footnote-back-ref">↩</a></p></li> </ol>