I am on 6.9.1, 802.3ad was working before upgrading. Now when I try to set it back to 802.3ad it will revert back to active-backup when I click on save 

Edited June 15, 20215 yr by demonmaestro

I had also noticed that its not putting a bond4 in the "ip a" list.

 

Just as proof 6.9.1 is not good i downgraded to 6.8.3 and it worked\

at least the 802.3

but its still not setting it right in the actual networking config

deleted the networking. 
then went in and reconfigured the networks.

restarted.

networking.cfg gone for good.

rebooted.

nothing

This box is in a DC. Don't have local access.

I do have IPMI to the box.

Edited March 23, 20215 yr by demonmaestro

5 hours ago, demonmaestro said:

networking.cfg gone for good.

 

There is no networking.cfg file so don't worry about not being able to find it. If you delete your network.cfg file and reboot it will be re-created with default values, which you should then be able to edit in the GUI. Perhaps your boot flash device is corrupt or failing, but you'd need local access to test it.

 

2 hours ago, John_M said:

 

There is no networking.cfg file so don't worry about not being able to find it. If you delete your network.cfg file and reboot it will be re-created with default values, which you should then be able to edit in the GUI. Perhaps your boot flash device is corrupt or failing, but you'd need local access to test it.

 

Good day,

So I had rebooted the machine multiple of times and it never did recreate it.

I had went up to the DC and "reinstalled" the backup (6.8.3) that I had of the Thumb drive.

everything was working as entended.

I had then installed 6.9.1 and it broke the 802.3ad again and set it to active-backup.

I had reverted back to 6.8.3 and things are back working.

 

Thank you for responding John_M

I am trying this again on a fresh new install of 6.9.2 and still same issue on a brand new machine.

Select 802.3ad and hit save.

Once I hit save it will revert to active-backup.

 

I've also notice that its saying the Interface Ethernet port 2 is down.

but when I go to terminal and do a "ip a" its showing the eth2 and eth3 as up and showing the bond2 as up.

The switch is also showing the connections as up and is configured for 802.3ad.

Edited June 14, 20215 yr by demonmaestro

Anyone?

Post your diagnostics.

52 minutes ago, John_M said:

Post your diagnostics.

Here you go.

It's a brand new install.

This has happened on a couple different Supermicro systems. Both with onboard NICS. 

tower-diagnostics-20210618-1942.zip

To make this work, you need to enable bonding on eth0 as well. So you have bond0 (eth0) and bond2 (eth2, eth3).

 

3 minutes ago, bonienl said:

To make this work, you need to enable bonding on eth0 as well. So you have bond0 (eth0) and bond2 (eth2, eth3).

 

That didn't work.

 

tower-diagnostics-20210619-0224.zip

11 hours ago, demonmaestro said:

That didn't work.

What doesn't work?

 

Your configuration is okay and bond2 is configured as LACP.

 

On 6/19/2021 at 1:30 PM, bonienl said:

What doesn't work?

 

Your configuration is okay and bond2 is configured as LACP.

 

When I go to set eth2 (along with eth3) to 802.3ad it still keeps reverting it to Active-backup

2 hours ago, demonmaestro said:

When I go to set eth2 (along with eth3) to 802.3ad it still keeps reverting it to Active-backup

 

There is actually a bug in displaying the correct bonding mode. It is using 802.3ad but it is wrongly displayed.

 

I made a correction for this in the upcoming Unraid version.

 

Thx

On 6/24/2021 at 9:57 AM, demonmaestro said:

When I go to set eth2 (along with eth3) to 802.3ad it still keeps reverting it to Active-backup

 

Just for information if someone stumble over this post.

 

I struggled with it and a lot of posts found by google actual gave the me the impression of there is a deeper technical problem or not supported well (especially with the Unifi switches as in my case).

Also the "Warning: No 802.3ad response from the link partner for any adapters in the bond" message lead to the wrong direction.

I started to believe it's just not working.

 

But the truth here is... it actually works and that without a problem.

But took me a while to find this post about it's just a GUI bug 

 

You can prove it for yourself with the following commands.

 

Executing in the shell (change the bond number to your bond) to see if the bond is active:

# show current active mode
cat /sys/class/net/bond0/bonding/mode
# show more details abount the bond
cat /proc/net/bonding/bond0

 

In my case also the switch reports the LACP bond as working and up.

 

 

 

@Moderators 

Maybe this should be pinned till it is fixed (I assume in 6.10 , I found tons of posts without a solution (except suggestions to use multi channel or another bond mode), but none except this after hours of reading such posts and try and error.

 

I've been trying to get this to work forever and nothing.  Glad I found this post.  Super aggravating seeing the ui go back to active_backup.

Just posting here to signal boost the thread, having the same issue and took me a while to find this and that it's just a GUI thing and working fine in the background.