Link aggregation with 802.3ad
It may be hard to believe, but 1G bit/sec is just not enough bandwidth for many network connections between LAN switches and from switches to high-demand network servers. Along with the bandwidth-consuming applications at ISPs, application service providers, streaming media providers and the like, traditional network administrators may also be feeling the bandwidth pinch at their server connections.
Relief, in the form of standards-based link aggregation technology for LAN switch ports and high-end server network interface cards (NIC), is on the way. Completed in mid-1999, the IEEE 802.3ad standard defines how two or more Gigabit Ethernet connections can be combined to load share, load balance and provide better resiliency for high-bandwidth network connections.
This is not a new concept. Many vendors have supported proprietary "trunking" schemes for 10/100M bit/sec Ethernet and FDDI for a few years. What's new this time is the standardized implementation of link aggregation. 802.3ad means the end of proprietary techniques that have been used to group together multiple slow-speed ports to get a faster point-to-point logical link.
What is link aggregation?
Cisco's proprietary Inter-Switch Link trunking (ISL) and Adaptec's Duralink port aggregation software are just a few of the popular names for aggregation techniques that have been supported by many switch and NIC manufacturers. The basic problem with these techniques, and the reason we now have 802.3ad, is that they were only designed to work with a single brand of network equipment. This meant major headaches for network administrators who needed the faster "aggregated" links but wanted to use a different brand of networking hardware.
As switch and NIC vendors begin introducing support for 802.3ad in their products, you can expect increased compatibility across different NICs and switches, as well as a few other major benefits.
First, the standard applies to 10M, 100M and 1,000M bit/sec Ethernet. Aggregated links can use a combination of these speeds on a single logical link. This increases the options available when you have one remaining gigabit port and three or four 100M bit/sec ports available between switches. You can add link bandwidth incrementally and affordably. Network traffic is dynamically distributed across ports, so administration of what data actually flows across a given port is taken care of automatically within the aggregated link.
As network bandwidth needs continue to grow, scalability is key. This is obviously a good thing for backbone connections that could benefit from the addition of a few more gigabits of throughput.
Don't overlook link aggregation for servers. High-performance servers are now beginning to support network I/O in the gigabit range.
Sign up for ITworld's Daily newsletter
Follow ITworld on Twitter @IT_world
jfruh
Apple syncing patent can't come soon enough
pasmith
New Twitter features borrow from 3rd party clients
Esther Schindler
Open Source Changes the Software Acquisition Process
mikelgan
How to set up continuous podcast play on the new iTunes
David Strom
Five important Windows 7 mobility features
sjvn
Guard your Wi-Fi for your own sake
Sandra Henry-Stocker
Grepping on Whole Words
Sidekick: The Good News & the Bad News
Either way you look at it Microsoft Data Center management did not follow standards or best practices in this failure. In which case it makes me wonder more about the outsourcing of corporate data much less personal data.
- mburton325
Join the conversation here
Quick, practical advice for IT pros. Made fresh daily.
Want to cash in on your IT savvy? Send your tip to tips@itworld.com. If we post it, we'll send you a $25 Amazon e-gift card.














Tunnel
I prefer to create a bonding and after bonding put the stream into a vpn session. So you can boost power and failover.