|
Question : LACP, Link Aggregation
|
|
I have a pair of Linksys SRW208MP switches, currently in a test environment, I am attempting to configure 2 or 3 of the ports on each switch in a LAG. Although it appears I have configured this correctly, I am not seeing what I expected - increased bandwidth. To test this I have a pc connected to a gigabit port on each switch. Throughput is exactly the same whether I use 1 port or multiple ports.
Does anyone have any experience with LACP, link aggregation, and can offer some advice?
|
Answer : LACP, Link Aggregation
|
|
plemieux72 is correct. Link aggregation/port bonding A to B traffic will always follow the same physical interface connection because of the binary math operation (XOR) plemieux72 referred to - its looking at the MAC or IP address and making a decision based on the result which port to use.
Therefore, it's statistical load balancing - not per packet/frame load balancing - it will always send the whole flow over one connection. It will statistically load balance flows. Even if you add a second flow, it could (50/50) use the port as the first flow. With a third connection, the odds would drop 33/67 of using the same port and a fourth flow would be 25/75. You get the idea. Theoretically, with 100 flows, statistically your flows would be more or less evenly distributed between the number of ports in your link aggretation.
So, where you get a big gain is a MANY to ONE situation - like an aggregated file server.
NOTE: There are technologies which are proprietary - such as Nortels Split Multi Link Trunking which operate in the manner you're expecting - however this is the exception rather than the rule. If you don't have a lot of traffic, the best gain from a network infrastructure perspective is that port aggregation gives you faster failover than spanning tree for purposes of resilience and redundancy.
|
|
|
|