Odd Switch/LAG behavior

6 posts in this topic Last Reply

Recommended Posts

Hi all, i'm experiencing some odd behavior on my unraid server while trying to set up link aggregation.  The short version is that when i enable bonding for eth1-4 (4 interfaces on a 4-port addon card) the only bonding mode i can choose is "active-backup".  If i choose anything else and hit apply (such as 802.3AD, which is what i actually want to use), it just flips back to active-backup.  I've got the 4 ports that they are plugged into set up as "aggregate" on my unifi switch, but the mode refuses to change.  Can't seem to figure it out.  Attached are screenshots of my configurations, can anyone take a look?  Thanks!






Link to post

...first Pic shows you have bridging enabled (in your case only for eth0)..second Pic shows, you want to switch over from bridging to bonding.

There is no need to switch bridging mode off in order to enable bonding.

Try and (re-)enable bridging as well when activating bonding (and add all eth-x to the bonding interface)

Link to post

Right, the intent of that way i have it would be for eth0 (which is on the motherboard) to be the primary interface for management and docker functions, and then eth1-4 to be bonded for all other functions (file access, primarily).  Would that be the correct way to accomplish this?

Link to post

no, the bridge will carry the IP and the bridge will be "linked" to the bonding interface which, in case of 802.3AD, will transfer the packets per stream in a more-or-less round robin like manner across the physical interfaces attached to the bond.

So bonding is for increasing available bandwidth, not traffic separation.

You cannot separate traffic like that....use VLANs for establishing that.

Again, you can have both, VLANs on the bridge(s) and a bonding interface.


Edit: for 802.3AD, you need to configure the Switch ports on the other side in the same manner


Edited by Ford Prefect
Link to post

Understood.  So ideally i would just bond everything and then use VLANs to separate traffic.  

That being said, any idea why the bond is stuck in "active/backup" mode?


(also love your nick, it's "nicely inconspicuous")

Link to post

...see my edit above...802.3AD is a managed bond and you need to configure your Switch accordingly.


Of course, you *could* try and do what you described, but addressing your server with different IPs within the same subnet is not really a way of separating the things.

If your Switch and Router support VLANs, I'd go that route.


Link to post

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.

Reply to this topic...

×   Pasted as rich text.   Restore formatting

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.