Have now tested,
without Sonos it looks very very good.

I wrote to SONOS support yesterday.

They mean, the switches should set to STP, not RSTP.

By default, the switches are set to RSTP, which is probably due to the newer protocol.
But can I change the switches to STP without any problems???

Thanks :)

I'm having the same problem.  Recreational complex.  I have one EAP225 outdoor that is mesh tethered, but all other EAP's (225 Outdoor and 245) are wired.  Gateway feeds PoE switch.  EAP's are split between gateway LAN ports and switch ports.  The issue occurs through the MESH, and then the switch blocks the offending port connected to the GW.  Just had it happen again instantly when I redirected a MESHed EAP to a new link EAP.  As soon as the link established, the switch blocked the trunk port and all connected EAPs dropped!  Not very good for the clients.   .  

  @Tedd404 7 of 9 are wired.  2 were not....  Now all but one is wired. The unit that is not wired is an outlier, so no path back to create a loop.   The resently meshed EAP245 that is now wired, but continues to connect via MESH.  The loops are no longer happening, but despite rebooting and "forgetting" and adopting the EAP245, it reconnects via MESH.  Tested the wire OK using a LinkRunner... which connects to Google and tests connection fine.  Can't seem to force the EAP to use WIRED.  There is an RH Industries switch in between... but another EAP225 works fine through it.   This looks like a new direction for this thread... but I suspect the LOOP issue is related to mesh happening on EAP's that are wired.   

  @lukass2000 

i am also facing same same issue can u please give solution for this issue

lukass2000 wrote

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 

lukass2000 wrote

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