5 or 8 port switch recommendation - daisy-chained downstream from HP 1920
-
How many SONOS devices do you have and which of them are connected by copper?
I'm not convinced that a different switch will solve your problems. Start with the bridge and one Play-device while the others are shut down. Add one at a time until your problem reappears.
-
jahonix - I have 4 that are directly wired to the HP switch and 3 that attach to the Sonos 'mesh' wireless network (separate from home wifi) - and then the Connect unit that is attached to the second switch. Everything works fine with the 4 wired to the switch and the Connect not attached.
The 3 wireless units are on the edge of the range of the 4 wired units (they still transmit the wireless signal), so the Connect, which is about halfway in between, provides a better wireless connection.
You may be right and I suppose I don't have to have the Connect wired to the second switch, but it's the way I have always had it configured. If the HP 1810 doesn't work, I will try setting it up as wireless-only. It took me several days of troubleshooting to determine that the Sonos unit was causing the problems, so I'm just interested in seeing if I can get it working correctly (wired).
-
… the 4 wired units (they still transmit the wireless signal)
THAT is your packet storm problem saturating the channel.
so I'm just interested in seeing if I can get it working correctly (wired).
AFAIK you either go wired OR wireless with a single bridge inbetween segments. No other unit than the bridge is supposed to be dual-linked (or one device like a Playbar acting as bridge).
Simply relying on (R)STP is bad by design and obviously doesn't work.The inability to configure the SONOS-Mesh to client's needs is what I really dislike about their philosophy.
-
Well, for me, Sonos was the most cost effective system to provide multi-room audio with multiple sources and independent room output in an existing home. Some areas are accessible via wire, but others had to be wireless. YMMV
Back to the Netgear switch: enabling STP did not fix the problem. I'm looking at ordering the HP 1820-8G, currently $80 on NewEgg as a replacement.
I’m not sure it’ll solve your issue but I have a fairly complex home network with pfSense as the firewall, an HP 1920-48G switch as the core, and Ubiquiti UniFi access points for WiFi. Each room in the home has a switch - some are little 5-port HP 1410’s all the way up to an 1810-24G in the main media area.
Some of my Sonos devices are hard-wired (4x Connects driving the outdoors, as well as the TV Playbars) and some are wireless (Play:1’s and Play:5’s, plus Subs.). We’re using SonosNet, no bridge or anything.
All is working together absolutely splendidly. I didn’t have to adjust my STP on the switches - everything is passing along fine.
It’s a clean, solid setup. Strongly recommend the HPE switches; they seem to work just great with Sonos.
I don’t even have issues with my TiVo devices, and those are just as finicky - if not more so - than Sonos.
-
dmurphy - thanks. I have a couple HP 1810-8G coming in and will test this weekend. Are all of your wired Sonos connected to the HP 1920-48G, or are some connected to the other 'room' switches?
-
Update - I finally had a chance to try the HP 1810-8G and it works great with the Sonos Connect, no configuration changes needed.
-
Update - I finally had a chance to try the HP 1810-8G and it works great with the Sonos Connect, no configuration changes needed.
Excellent, good as a reference for everyone who might run in to this issue later on as well.
-
dmurphy - thanks. I have a couple HP 1810-8G coming in and will test this weekend. Are all of your wired Sonos connected to the HP 1920-48G, or are some connected to the other 'room' switches?
My apologies for getting back to you so late! I totally missed this reply.
My Sonos devices are all over the network - some to the "core" 1920-48G, and a bunch to other switches in the LAN as well. No issues whatsoever. Workin' like a champ!
-
dmurphy - thanks for the reply. I was about to post an update and am curious how you managed with your HP switch setup.
I was premature on posting that the 1810 worked without any configuration. It turns out that STP was enabled on the 1920 by default and I had to manually enable it on the 1810. This worked, but when I reviewed the Sonos logs, it wasn't working as expected - for example, it was using sonos mesh when a wired connection existed.
First, I had to tell the 1920 to use 802.1d-1998 path costs and use STP 'mode' (not RSTP).
More importantly, the 1810 doesn't correctly set STP Path Costs when the STP 802.1d (legacy) mode is selected - it continues to use the 802.1w path costs and you have to manually set the path costs for ports that (1) connect the switch to the primary 'core' switch (path cost = 4) and (2) to ports that are connected to a sonos unit (path cost = 19).
After relevant ports on all switches are using the old path costs, the sonos logs and matrix show that all the devices are working as expected - using wired when available and sonos mesh when required.
I had read a number of guides that said you need to disable sonos mesh on any unit that is wired to a switch, but that is not true.
Hope this helps anyone trying to configure sonos with managed switches (and happen to be looking for help in the pfSense forum) :D. As a side benefit, I learned a lot about STP over the past couple weeks!
-
I have a HP-1820 "Backbone" , and my favourite (cheap & slim) manageable switch is the D-Link DGS-1100-08.
I have 9 of them now.I have a few Linksys LGS-308's too.
But they're almost 2 x the D-Link price ($35) , and i don't use the Linksys features ie. 802.1x in most of the places.Even the 1100-08 can do RSTP , only "quirk" i have seen on the D-Links , are that they tend to "loose" their dhcp address.
So use a static ip for mgmt./Bingo
-
+1 on the DGS-1100-08. I have two or three.
I also saw a quirk in a DGS-1210-10P. Accessing the web gui same-subnet fails to load properly/consistently. Accessing it from another subnet so the traffic is out the management default gateway works fine. Weird.
But other than that it powers a couple phones and an AP and carries all my traffic just fine from my desk over an LACP on the SFP ports to my "core" (lol) switch.
LIGHT YEARS better than the HUGE, STEAMING PILE OF EXCREMENT that is the Netgear GS108PE it replaced.
-
I also saw a quirk in a DGS-1210-10P. Accessing the web gui same-subnet fails to load properly/consistently. Accessing it from another subnet so the traffic is out the management default gateway works fine. Weird.
I experienced somewhat the same, configuring an 1100-08 yesterday.
After moving the mgmt vlan to the "final" vlan , i got a "White screen" , even after several refreshes etc. (Using firefox)
No hangs or errors , so the 1100-08 was answering on http.I didn't want to shutdown FF , so just opened a Chromium (Linux Chrome) , and entered the samme ip that gave white screen in FF.
Everything was ok in Chromium.After (saving the new mgmt vlan change to flashcfg) , and a a reload of the 1100-08 … FF was ok too ???
/Bingo
