NKnusperer Posted May 4, 2017 Share Posted May 4, 2017 Hello, I've configured two NIC's in 802.3ad bonding mode and so far everything works as expected. Now I want to change the 'xmit_hash_policy' from 'layer2' to 'layer2+3' to get a more balanced distribution of traffic but I cant figure out where to set this. Quote Link to comment
ken-ji Posted May 9, 2017 Share Posted May 9, 2017 You'll need to add it to the /boot/config/go file # enable layer2+3 in bonding 802.3ad echo layer2+3 > /sys/class/net/bond0/bonding/xmit_hash_policy Quote Link to comment
klamath Posted May 11, 2017 Share Posted May 11, 2017 (edited) you may need to ifdown and ifup the interface after that echo. #setup bonding for layer2+3 #ifconfig bond0 down;echo 'layer2+3' >/sys/class/net/bond0/bonding/xmit_hash_policy;ifconfig bond0 up Edited May 11, 2017 by klamath Quote Link to comment
ken-ji Posted May 11, 2017 Share Posted May 11, 2017 I didn't notice that. Also I've stopped lacp in favor of dedicated nic for containers. Quote Link to comment
L0rdRaiden Posted July 20, 2020 Share Posted July 20, 2020 It would be nice to have this settings in the network configuration UI. Usually if you do a bond you will want to change the xmit_hash_policy 1 Quote Link to comment
L0rdRaiden Posted July 20, 2020 Share Posted July 20, 2020 (edited) On 5/12/2017 at 12:59 AM, klamath said: you may need to ifdown and ifup the interface after that echo. #setup bonding for layer2+3 #ifconfig bond0 down;echo 'layer2+3' >/sys/class/net/bond0/bonding/xmit_hash_policy;ifconfig bond0 up this is only executed at the boot time of unraid, right? Do i have to add #ifconfig? or starting with "bond0 down...." is enough? Edited July 20, 2020 by L0rdRaiden Quote Link to comment
L0rdRaiden Posted July 21, 2020 Share Posted July 21, 2020 (edited) @klamath @ken-ji Should it look like this? Thanks in advance Edited July 21, 2020 by L0rdRaiden Quote Link to comment
L0rdRaiden Posted July 21, 2020 Share Posted July 21, 2020 Just for the record cat /proc/net/bonding/bond0 Quote Link to comment
ken-ji Posted July 23, 2020 Share Posted July 23, 2020 On 7/22/2020 at 2:26 AM, L0rdRaiden said: @klamath @ken-ji Should it look like this? Thanks in advance Unless you absolutely know what you are doing, emhttp is usually last as that will start the array and other related services. you are in effect quickly restarting the network as containers and vms powerup (though in practice, the array is still mounting at this point) 1 Quote Link to comment
bonienl Posted July 24, 2020 Share Posted July 24, 2020 On 7/20/2020 at 7:10 PM, L0rdRaiden said: Usually if you do a bond you will want to change the xmit_hash_policy 802.3ad LACP only supports layer2 (MAC) hashing. The other modes for hashing on layer 3 and layer 4 are not official part of the IEEE standard. Use with caution. Remember that you manipulate only one side of the bond and this may lead to asymmetric traffic. Quote Link to comment
L0rdRaiden Posted July 25, 2020 Share Posted July 25, 2020 21 hours ago, bonienl said: 802.3ad LACP only supports layer2 (MAC) hashing. The other modes for hashing on layer 3 and layer 4 are not official part of the IEEE standard. Use with caution. Remember that you manipulate only one side of the bond and this may lead to asymmetric traffic. I understand that at least my switch has to be layer3+4 compatible, right? Quote Link to comment
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.