The way a teacher of mine at uni explained LACP to us was: you can have a motorway with 4 or 5 lanes, but you only use one lane at a time and you can never exceed the speed limit.
How did I miss this video?! Paul is a mad network engineer, he just breaks stuff down to the core! Just wanted to share Trader make UV resistance covers for all your Clipsal classic gear that's getting the nicotine stain to it.
awesome demonstration! reminds me of a lab some five years ago bonding two wifi adaptars, never did figure out a way to set up any any kind of load balancing over it
Oh great, now you've got me thinking about that :) I hope you were using two different APs on two different channels, otherwise would be rather pointless
@tallpaul Brotip: if you start to see issues with multicast: we had this issue with LACP and Intel chipsets. Had to remove one of the 2 links of the bond to stop multicast packet-order/jitter/pixelation issues. 👍
Thank you very much. This is what I am looking for. Many learning materials are just switch connects to switch, but actually I want lean how Linux using bond with LCAP, i.e., Linux server connects to switch.
Great content Paul! Out of curiosity, are the bridge interfaces needed? Wouldn't you have been able to configure an IP address on the bond0.X interface (X being the VLAN ID)? Keep up the good content!
I've been doing lacp on all my servers for a while, but I have to admit that I just trusted the concept without testing it with iperf or observing ot with wireshark. Now what I'm wondering is what are the different hashing algorithm and if there is such a configuration where you can maximize the bandwidth usage to 2gig when you initiate 2 sessions from the same server\client.
That was just the default I used. It depends on switch, but on that switch I could choose: l2-src-dst Base the hash on l2-src-dst (Default:l3-src-dst) l3-src-dst Base the hash on l3-src-dst (Default) l4-src-dst Base the hash on l4-src-dst (Default:l3-src-dst) So, if you just have the same server and client, you can base it on a different layer.
You are limited to basing it off of specific packet header fields, some hardware is/featured better at balancing then others, some hardware that supports more "line-rate" features give you more options to change the hash too. We played with all of them in different applications: usually came to the conclusion that upgrading the NIC is the best option. For the case where there are lots of unique addresses or mac's with high bandwidth requirements: then this is the clear option. If your dst-mac is all one router interface: then best to use L3-dst-ip instead of MAC. 👍
Thanks for your vids.. just found you. you're hilarious. "do what you want. take it easy. if you want" When 10gb? as for the dust in your pc.. get a room filter.. (don't make your pc's and your lungs do the filtering)
The way a teacher of mine at uni explained LACP to us was: you can have a motorway with 4 or 5 lanes, but you only use one lane at a time and you can never exceed the speed limit.
"If you want to know how things work, just look at packet captures" That's why you are at the top of the game, everyone else is watching netflix!
Just wanted to say I appreciate and learn from your videos. Thank you 🙏🏼
Thanks Paul watching from Algeria in north Africa
I'm not American, so I know some world geography ;)
@@TallPaulTech Yeah same here. that sht be crazy
How did I miss this video?! Paul is a mad network engineer, he just breaks stuff down to the core!
Just wanted to share Trader make UV resistance covers for all your Clipsal classic gear that's getting the nicotine stain to it.
awesome demonstration! reminds me of a lab some five years ago bonding two wifi adaptars,
never did figure out a way to set up any any kind of load balancing over it
Oh great, now you've got me thinking about that :) I hope you were using two different APs on two different channels, otherwise would be rather pointless
To the point. I would gladly love to meet you in person. You are a cool Aussie :D
Thanks for the nice things you showed us today.
I am watching your video from Iraq.
Thanks.
@tallpaul
Brotip: if you start to see issues with multicast: we had this issue with LACP and Intel chipsets. Had to remove one of the 2 links of the bond to stop multicast packet-order/jitter/pixelation issues. 👍
My IPv6 multicast through that LACP is working fine :)
Thank you very much. This is what I am looking for. Many learning materials are just switch connects to switch, but actually I want lean how Linux using bond with LCAP, i.e., Linux server connects to switch.
Now you're talking.
as usual top content
LACP for the win
Bone-mode ftw :D
It's working thanks my friend
Very cool.
can you chuck destination port in to the hash as well so it can use different streams to the same destination ip?
Nice. Got another switch for MLAG? I wonder why my local google doesn't respond to ping6 anymore. The Sydney address in your video one still works.
I've been having the same issue in Chicago for around a week now
Great content Paul! Out of curiosity, are the bridge interfaces needed? Wouldn't you have been able to configure an IP address on the bond0.X interface (X being the VLAN ID)? Keep up the good content!
As I said, they're for VMs to use.
I've been doing lacp on all my servers for a while, but I have to admit that I just trusted the concept without testing it with iperf or observing ot with wireshark. Now what I'm wondering is what are the different hashing algorithm and if there is such a configuration where you can maximize the bandwidth usage to 2gig when you initiate 2 sessions from the same server\client.
That was just the default I used. It depends on switch, but on that switch I could choose:
l2-src-dst Base the hash on l2-src-dst (Default:l3-src-dst)
l3-src-dst Base the hash on l3-src-dst (Default)
l4-src-dst Base the hash on l4-src-dst (Default:l3-src-dst)
So, if you just have the same server and client, you can base it on a different layer.
You are limited to basing it off of specific packet header fields, some hardware is/featured better at balancing then others, some hardware that supports more "line-rate" features give you more options to change the hash too.
We played with all of them in different applications: usually came to the conclusion that upgrading the NIC is the best option.
For the case where there are lots of unique addresses or mac's with high bandwidth requirements: then this is the clear option.
If your dst-mac is all one router interface: then best to use L3-dst-ip instead of MAC.
👍
U are using an Aruba 6300 switch?
Thanks for your vids.. just found you.
you're hilarious. "do what you want. take it easy. if you want"
When 10gb?
as for the dust in your pc.. get a room filter.. (don't make your pc's and your lungs do the filtering)