Timeline for Inconsistent behavior of link aggregation
Current License: CC BY-SA 4.0
4 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Nov 8, 2022 at 1:13 | comment | added | Elliott B | I tried some tests with different iperf source ports and I don't think that's the issue. It actually looks like this is related to current bandwidth on the switch. If bandwidth is very low, then it sends both streams through 1 path. If bandwidth is even slightly elevated, then it splits. I'm still trying to figure out the exact logic but it's something like that. | |
| Nov 7, 2022 at 19:53 | comment | added | OlofL | I said "could" as an example. I don't know the exact detail on how their hashing algorithms work, but it was an example to show there is a tuple of values that sets the transmit interface. This tuple will always be the same every time it has the same value. The only difference of your iperf3 tests is the src-port you use to do tcp-connection, and therefor it is likely that is why youre getting different results, because iperf3 used a random port on your -P2, and sometimes they hashed to the same interface, and sometimes they hashed to different interfaces. | |
| Nov 7, 2022 at 18:09 | comment | added | Elliott B | I can't find any reference to even/odd in the Arista docs. I believe the hash should be different any time the port numbers are not the same, even if they both have the same "evenness". I updated the question to show my hash settings. | |
| Nov 7, 2022 at 15:44 | history | answered | OlofL | CC BY-SA 4.0 |