It's load balanced via a hash over the specified fields. So if you only got two flows there's a 50% chance that they will end up on the same link. Your real traffic will have a lot more flows so it will even out.
Paul 2018-06-21 21:48 GMT+02:00 Jacob DeGlopper <[email protected]>: > OK, that was a search-and-replace error in the original quote. This is > still something with your layer 3/4 load balancing. > > iperf2 does not support setting the source port, but iperf3 does - that > might be worth a try. > > -- jacob > > > > > On 06/21/2018 03:37 PM, mj wrote: > >> Hi Jacob, >> >> Thanks for your reply. But I'm not sure I completely understand it. :-) >> >> On 06/21/2018 09:09 PM, Jacob DeGlopper wrote: >> >>> In your example, where you see one link being used, I see an even source >>> IP paired with an odd destination port number for both transfers, or is >>> that a search and replace issue? >>> >> >> Well, I left portnumbers as they were, I edited the IPs. Actually the >> machines are not a.b.c.9 and a.b.c.10, but a.b.c.204 and a.b.c.205, for the >> rest, everyting is unedited. >> >> So a single line example: >> >> Client connecting to a.b.c.205, TCP port 5001 >> TCP window size: 85.0 KByte (default) >> ------------------------------------------------------------ >> [ 3] local a.b.c.204 port 60600 connected with a.b.c.205 port 5001 >> ------------------------------------------------------------ >> Client connecting to a.b.c.205, TCP port 5000 >> TCP window size: 85.0 KByte (default) >> ------------------------------------------------------------ >> [ 3] local a.b.c.204 port 53788 connected with a.b.c.205 port 5000 >> [ ID] Interval Transfer Bandwidth >> [ 3] 0.0-10.0 sec 746 MBytes 625 Mbits/sec >> [ ID] Interval Transfer Bandwidth >> [ 3] 0.0-10.0 sec 383 MBytes 321 Mbits/sec >> >> >> And a lucky example: >> >> Client connecting to a.b.c.205, TCP port 5001 >> TCP window size: 85.0 KByte (default) >> ------------------------------------------------------------ >> [ 3] local a.b.c.204 port 37984 connected with a.b.c.205 port 5001 >> ------------------------------------------------------------ >> Client connecting to a.b.c.205, TCP port 5000 >> TCP window size: 85.0 KByte (default) >> ------------------------------------------------------------ >> [ 3] local a.b.c.204 port 48850 connected with a.b.c.205 port 5000 >> [ ID] Interval Transfer Bandwidth >> [ 3] 0.0-10.0 sec 1.09 GBytes 936 Mbits/sec >> [ ID] Interval Transfer Bandwidth >> [ 3] 0.0-10.0 sec 885 MBytes 742 Mbits/sec >> >> (reason for the a.b.c.204 is that the IPs are public, and I'd rather not >> put them here) >> >> I don't see the odd/even port numbers thing you noticed..? (I could very >> well miss something though....) >> >> I see no way to specify what outgoing port iperf should use, otherwise I >> could try again using the same ports, to check the pattern. >> >> Thanks again! >> >> MJ >> _______________________________________________ >> ceph-users mailing list >> [email protected] >> http://lists.ceph.com/listinfo.cgi/ceph-users-ceph.com >> > > _______________________________________________ > ceph-users mailing list > [email protected] > http://lists.ceph.com/listinfo.cgi/ceph-users-ceph.com > -- Paul Emmerich Looking for help with your Ceph cluster? Contact us at https://croit.io croit GmbH Freseniusstr. 31h 81247 München www.croit.io Tel: +49 89 1896585 90
_______________________________________________ ceph-users mailing list [email protected] http://lists.ceph.com/listinfo.cgi/ceph-users-ceph.com
