@Fleegle61 
If i activate RSTP on the TP-Link Switches I need to fill out a Priority field.

Default is 32768.
Is this okay?

 

Hi @Fleegle61 , @btx 

Tentatively I enabled RSTP on all switches.



After activating, I get a lot of message like this every few minutes:
TL-SG2218 port Gi1/0/15 was blocked.

or

TL-SG3428 port Gi1/0/5 was blocked.

Then I tried to do some research.
It may be that I have to activate RSTP on the Switch and also on the "problem" ports switch to "Spanning Tree"?



Thanks :)

  @lukass2000 priority should be fine.  For a simple network like yours, it wont make a difference.  Larger networks would maybe require a different priority depending on which path you want to be the priority

  @lukass2000 

As you can see, if you set it up for loopback, it will detect a loop and shut down the port.  When using RSTP it will look to see which path to keep active and which path to block so that the loop cannot occur

Fleegle61 wrote

  @lukass2000 

 

As you can see, if you set it up for loopback, it will detect a loop and shut down the port.  When using RSTP it will look to see which path to keep active and which path to block so that the loop cannot occur

  @Fleegle61 But it's funny that when I activate RSTP
so every 5-10 minutes a message of the blocked port is displayed.
Wouldn't you say that RSTP really works better?

Virgo wrote

  @lukass2000 

 

Suggest turn off Loopback detection and test again.

  @Virgo 

If I disable "Loopback detection" the message will no longer come, but the apparently existing problem will not be solved by it, or not?

  @lukass2000 if you disable the loopback protection you risk storming the network and taking it down so you cant do anything.  The loopback detect at least will shut down the port, stop the storm and allow the rest of the devices to work just not the port where the loop came from, anything on that will be blocked

RSTP at least will prevent the loop by allowing one path to remain active and the ther path to be in a block state.  

The 2 check boxes behave in different ways. 

Yet, you are correct, disabling loop detect does not fix the issue, only makes it worse.  So you need to find out who is passing the data back to the originator  on a different port causing the loop in the 1st place.  

Does the "uplink port" technically have a special function?

LAN Cable from Port 14 on the SG2218 go to the T1600G
LAN Cable from Port 15 on the SG2218 go to the SG3428

Shouldn't both ports then be marked as "uplink port"?

Also on the SG3428 only port22 is marked as an upload port.
This is the Port from the R605.
Port24 where the LAN cable on the SG3428 forwards to the SG2218, is not marked as an upload port.
Or does the optical marking have no technical effect whatsoever?
Thanks :)

I do not know what to do, today alone I had four loops and blocked ports :(
 

RSTP is enabled, Mesh is turned off, but no difference :(
 

Is there no possibility found in OmadaSDN what is causing the problem?

TP-Link says OmadaSDN is a great business system with many Loggings....

But there is no chance to find any logging where i can see where is my problem...

That's extreeeeeeeemely annoying :(