802.3ad LAG does not work

[ElPabloMaximo]

I have a T12-450 and am trying to create a 2 port LAG on my Ubiquiti USW Pro 24 PoE switch. I already have a Synology DS916+ in a similar LAG configuration using 802.3ad as the protocol but for some reason switch seems to think that the TerraMaster is causing a loop.

[TMroy]

TOS does not support such a feature.

[Gremlin]

{L_BUTTON_AT}TMroy

Good day. You need to look at Help section linked to GUI and possibly options available when creating LAG. This is Help that I see:

Self-Adapting Load Balance; IEEE 802.3as Dynamic Link Aggregation; Balance XOR; Active / Standby.

I can't help but think that the refeence to IEEE 802.3as is confusing people. This, of course is not 802.3ad that users are expecting, but are thinking they see ....... Simple question: Is 802.3ad Dynamic Link Aggregation supported? Simple Observation: Don't include options that are not supported.

[ElPabloMaximo]

Then why is it available in the adapter bonding selection??

[TMroy]

So you are talking about link aggregation(LAGG)? We need to verify it.
Did you enable 802.3ad in your switch and configure it correctly?

[ElPabloMaximo]

So you are talking about link aggregation(LAGG)? We need to verify it.
Yes, although I have always seen Link Aggregation Group abbreviated with only one 'G', I believe I did mention the correct IEEE specification in my previous post.

Did you enable 802.3ad in your switch and configure it correctly?
Yes, my Synology is currently running a 802.3ad dynamic LAG on my Ubiquiti USW Pro 24 PoE switch without any issue. When attempting to configure this on the TM T12-450 running TOS 5.1.67 communications is spotty at best and eventually it starts producing STP errors and disabling ports.

[TMroy]

how many port? and which port on your TNAS you connected to your switch?

[ElPabloMaximo]

the bond is configured using the 2x RJ-45 Ethernet ports

[TMroy]

EEE 802.3ad Dynamic link aggregation creates aggregation groups that share the same speed and duplex settings. Utilizes all slaves in the active
aggregator according to the 802.3ad specification. This bond option aggregating multiple physical network interfaces into a logical bond increases the overall available bandwidth and throughput. We found no abnormalities in the laboratory. What is your issue? What functionality do you expect this option to provide you?

[ElPabloMaximo]

I guess I was expecting it to work like other 802.3ad aggregates in that the two links share the same IP not that each link requires it's own IP in addition to the desired IP. I configured link 1 with the desired IP and left link 2 as dynamic. When I configured the bond, I used the desired IP and that caused a duplicate IP address issue. I had to delete the bond, configure both link 1 and 2 with uniquie IP addresses, and then configure the bond with the desired IP

What I expect
Link1
> Bond:IP1
Link2

Terramaster

Link1:IP1
>Bond:IP3
Link2:IP2