Loop detection again and again on different switches and ports
Hi,
I've been using OmadaSDN for a year.
Used to have a WRT54, then three WRT54 with Tomato in "mesh" operation, so to speak, Then an Asus router with three access points, then a Fritzbox, four access points with several managed netgear switches, but I've never had anything as unreliable and unstable as my current OmadaSDN, and the whole thing then scolds itself as a business solution.
Several loop detections and port blockings are detected several times a week, then everything is not available again for a short time because it is newly integrated into OmadaSDN, sometimes hours later, sometimes days later everything starts all over again.
e.g. added a SG2008P to OmadaSDN yesterday.
No device is connected to the switch, only the uplink cable to Port1, two hours later I had a loop detection message on Port8 for the first time...
That can not be?
I switched off Mesh so that a loop doesn't occur somewhere via an EAP.
Have testet RSTP on and off, used Loopback detection or Spanning Tree,... no difference
Is there no technical possibility in Omada SDN to determine why this loop occurs?
It's a business system?????
What can i do, those loops are annoying
Here is a simple sketch of my OmadaSDN
I primarily get the loop detection on SG2218 port 15 and T1600G port 24, but also always on other ports.
What i forgot, the OC200 is still connected to the R605 port4.
Maybe someone has a tip for me?
THANKS
Recently:
Everything just annoying