I'm concerned that I'm misunderstanding how aggregators work in the scenario below:
I have a project where I need 40 Gbps links between switches. My plan was to have my three switches use all four of the 10Gb uplink ports to a fourth "aggregator switch" so that I'd have the necessary bandwidth for a total of 12 10Gb links to the aggregator.
Does link aggregation truly work as if you have an aggregated link? Is this how I want to achieve the 40Gb uplink between switches?
According to IEEE 802.1ad specification, it strikes me as being more about failsafe/failover than about using multiple links to achieve a larger pipe.
If this is not the correct approach can someone suggest a better and more common approach?
Best Answer
What really happens is that any one flow only uses one of the links. Different flows are assigned to different links based on a hashing algorithm, so, in aggregate, you get the full bandwidth of the combined links, but any one flow will only get the bandwidth of a single link.
You don't want to spread a single flow across multiple links because that will create problems with out-of-order packet delivery. Protocols, like TCP, can deal with that, but it can slow them down. Other protocols like UDP cannot deal with that, and it is complete death to real-time protocols that use UDP, such as voice or video.
It does provide redundancy, too, but you really are getting the full bandwidth of all the links in the channel, but in aggregate over all flows.
If that doesn't work for you, then you need to get devices with 40 or 100 Gbps interfaces.