I had some serious issues with SONOS Equipment connected to OMADA SDN, seems to be a common problem with any sophisticated network,
e.g. port blocking, loops, ...
I tried 2 approaches
A) All WiFi - meaning all SONOS Clients run on one of the WiFi provided by OMADA EAPs
B) Linked via SONOS Speaker / AMP - meaning 1! SONOS Client is wired, beeing the root of a seperate SONOS NET
C) Multiple Linked - meaning 2 or more SONOS Clients are wired, others connect via SONOS NET.
P.i.t.A - causing multiple loops, port blocks...
Works as designed, but will definately put some traffic on WiFi
Works best for me, but also caused some issues, sometimes port blocking, leading to disconnection of switches, readoption...
I have several questions - maybe we could use this thread to document good practices...
Should all the SONOS clients appear in the client list? Obviously all got their IP-addresses via DHCP..., and I am pretty shure I had all of them in the client list, even in the history, funny enough, nothing visiable since I restarted the whole setup.
At the Moment all SONOS clients have to be in the same subnet as the managing app,
would be better to have them on a seperat VLAN, but then the managing app eg. on iPhone or Laptop will not find SONOS
Probably this can be solved with proper Spanning Tree Configuration, read about this in other Network Forums,
has anyone tried this configuration with success?
I researched this topic a little bit further, as it's more or less the same with other network infrastructure a lot has been documented already,
e.g. you may want to google
Mike Connolly Sonos
Optimal Configuration Managed Network Sonos
(unfortunately the direct links to the relevant articles weren't accepted here ;-)