Hi Blaszlo

"Switch start blinking like a madness." It seems that your network has loop. You can check the LAG. If LAG doesn't establish normally, it will form the loop.

I used the tp-link switch before. After I configured the LAG, I need to re-configure the layer2 function. Such as the following. I need to re-configure VLAN and need to click LAGS to configure VLAN for LAG group. Just remind you that we need to re-configure the layer2 function.

Hi!

Thank you the answer, but the lag is configured. Before write here, i read lot of post of this forum and other sites. 

I set the lag untagged vlan, lag port primary vlan, the included ports untagged vlan AND primary vlan. 

Same vlan = not working

if the ports other vlan (an unused techical) = not vorking.

I set up the last 2 ports on switches AND lag untagged 512 vlan THEN i set the last 2 ports on swithes AND the LAG PVID to 512.

the switches last 2 ports in the lag (23-24 to 47-48)

AND i set up port 1 untagged 512 and pvid 512. Nothing else. all other ports in system vlan. 

I can't reach the secondary switch, trough, the primary switch. The packet capture show a thing: No ARP reply from switches. The lot of ARP query is blinking the leds, but no ARP reply.

So?

blaszlo wrote

Hi!

 

Thank you the answer, but the lag is configured. Before write here, i read lot of post of this forum and other sites. 

 

I set the lag untagged vlan, lag port primary vlan, the included ports untagged vlan AND primary vlan. 

 

Same vlan = not working

if the ports other vlan (an unused techical) = not vorking.

 

I set up the last 2 ports on switches AND lag untagged 512 vlan THEN i set the last 2 ports on swithes AND the LAG PVID to 512.

 

the switches last 2 ports in the lag (23-24 to 47-48)

 

AND i set up port 1 untagged 512 and pvid 512. Nothing else. all other ports in system vlan. 

 

I can't reach the secondary switch, trough, the primary switch. The packet capture show a thing: No ARP reply from switches. The lot of ARP query is blinking the leds, but no ARP reply.

 

So?

If you mean that you cannot access the secondary switch thorugh the primary switch, please make sure that the interface of vlan 512 is up and you can see the related routing entry on routing table. I remember that we need to enable admin status for VLAN interface.

Hi!

I'm use LOT of TP-Link switches. (cca 100 - 150 pcs mostly has more then one LAG). We have never problems until v2. Now in V3 vs V3 and V3 vs V2 is a horror.We buy cca 15 pcs V3, but the lags in all v3 is random (this is the most milder expression). BUT if the lag is die, the switch working on one link. It's not good.

Now i fighting a v3 vs v2 LAG. I set up properly. (this settings working good, if i transport it two v2 switch.) if i use the config between a v3 to a v2, not working. Oh i'm wrong. Worked cca one day if the admin keys is same on both switch, and it fell apart by morning and never work again. 

If i put in the LAG's two link, the lag is dead. the v2 shows to me 2 menber port and all ok. the v2 not show ports, in LAG, and the connection is broken.if i pull out one of links, the connection is ok and both switch show one port in LAG. Whatever which one pulled out.If i put in the link broken, and game over.

The v3 is a junk. 

Can anybody see like this?

Hello!

Seeing the same issue when trying to connect two T1600G-28TS (UN, v3.0) together using a 2-link LAG.

Firmware is "3.0.0 Build 20180130 Rel. 33015(s)". Using "SRC MAC + DST MAC" hash algorithm, VLAN ID 1 on all ports and the LAG (i.e. not really making use of VLAN yet).

Tried both static LAG and LACP but they lead to the same result, which is LEDs rapidly blinking upon plugging in the 2nd link, CPU going from ~10% to ~40% and web interface starting to become slower and slower to the point that it's not usable any longer (impossible to log in, if not already logged in while connecting 2nd link). Using only one or even better no link resolves the issue...

Not happy about this, as we just bought the switches in order to realize some sort of LAG / port trunking backbone between two office parts.

Is there a later firmeware that resolves the issue? I thought I checked and found the one on the switch to be the latest available already, but I might have missed something there.

I found the source code for v1 and v2 of the switch on the TP-Link website, but v3 seems to be not available freely?

Did you find any solution to this in the meantime, blaszlo?

Thanks and hope this can be made to work somehow.

quantum wrote

Hello!

 

Seeing the same issue when trying to connect two T1600G-28TS (UN, v3.0) together using a 2-link LAG.

 

Firmware is "3.0.0 Build 20180130 Rel. 33015(s)". Using "SRC MAC + DST MAC" hash algorithm, VLAN ID 1 on all ports and the LAG (i.e. not really making use of VLAN yet).

 

Tried both static LAG and LACP but they lead to the same result, which is LEDs rapidly blinking upon plugging in the 2nd link, CPU going from ~10% to ~40% and web interface starting to become slower and slower to the point that it's not usable any longer (impossible to log in, if not already logged in while connecting 2nd link). Using only one or even better no link resolves the issue...

 

Not happy about this, as we just bought the switches in order to realize some sort of LAG / port trunking backbone between two office parts.

 

Is there a later firmeware that resolves the issue? I thought I checked and found the one on the switch to be the latest available already, but I might have missed something there.

I found the source code for v1 and v2 of the switch on the TP-Link website, but v3 seems to be not available freely?

 

Did you find any solution to this in the meantime, blaszlo?

 

Thanks and hope this can be made to work somehow.

Do you mean that T1600====(LAG)====T1600? If you use static LAG, just make sure that LAG table has the switch ports you set. If you use LACP, please note that as least one switch should be active mode.

And the rapidly blinking should means that your LAG fail, so has the loop.