The Sub and Surrounds should be getting their signal directly from the Arc (they all bond on their own 5ghz network)… 

When you set them up, did you use Add Surrounds and Add Sub from the Arc settings?

I did originally and had to reset all to the factory settings and start all over. Then when I went to add them to the arc, they were not available. 

Here’s the latest adventure with my Sonos install.  I have reset everything and started over. I installed the Arc first, and then reset the surround and sub (green lights) and I go to the Arc and select Set up Surrounds and the One SL surrounds are not detected, but it does see two of my Play:1 speakers. 

I then try to add the Sub and I get “Sub not found.”  If I go to the main menu for all components and add Speakers or Components I see the Sub and Surrounds Speakers, but it will not allow me to add them to the Arc.  I have gone to Manage/Network/Managed Networks/Update Networks and it keeps wanting to setup the Arc even thought it is already connected and working.  It doesn’t see the Surrounds or Sub.  I’m at a loss as I have wasted days / 20+ hours and about ready to find another solution.  

Appreciate any help. BTW, I have over 30 years experience with IT and Networking and if I cannot figure this out, I feel bad for those with little to no experience with these type products. 

Aruba switches are generally used in the enterprise, and not in home environment. There is a link here that may help:

Also check here, possible issues with latest Aruba software, affecting other things, like Apple HomeKit etc, some other options to try:

https://www.reddit.com/r/ArubaInstantOn/comments/1eda40d/software_ap_3_aruba_ap_22_problems/

Part if the issue is trying to use a network products designed for ‘enterprise’ where use cases will be different that use cases / protocols in a consumer/home environment. The enterprise network products may not be rigorously tested with consumer devices, and vis versa. I’m sure it can be made to work.

One other possible solution is to setup a temporary network with same SSID & password as your Aruba on a consumer WiFi router, and setup Sonos on that to test, maybe you can bond your HT system on that network and then move to the Aruba?

I understand your point, but I’ve been using this same Aruba network products in my home for 5+ years and it has worked perfectly and all of the Sonos equipment has worked except for the Sonos Arc/Surrounds and Sub.  And, I am familiar with the installation of the Aruba network.

I haven’t had issues with any other product on my network except the Sonos mentioned above, so I don’t need it seems to be related just to this specific product IMO.  I may try your last recommendation.  Thank you!

Same products for 5+ years, what products? What firmware versions?

Another link here re 3.0.0, affecting connectivity:

https://www.reddit.com/r/ArubaInstantOn/comments/1eiarrp/issues_since_firmware_300/

Just had another thought, when you bond HT devices to the Arc, the Arc will proxy its interface to the Sub / Surrounds. The Aruba software maybe blocking this as it will see multiple IP with same MAC address, something similar recently, unfortunately, lost in a mega thread, hopefully my link below will work to the relevant post:

Have you tried hardwiring the Arc to your switch? Sonos doesn’t recommend hardwiring surrounds or the Sub unless the main speaker is also hardwired. Maybe all you need to do is to hardware the Arc with its WIFI left on. That’s how I have my HT system setup with no issues. Also , try resetting everything again, setup the Arc then add the Sub before you add the surrounds.

Well, I finally got it working, but it was doing some of the same things as before and it took several attempts to finally get all of the Sonos components (Arc/Surrounds/Sub) bonded together.

What did I do.  I moved just the Arc/Surround/Sub to the SSID to my ISP Router/AP instead of the SSID on my Aruba AP’s.  Even with it all working if I go to manage/network/manage network it finds the Arc and other devices and wants me to set them up again.  

All of my other Sonos speakers are on the Aruba SSID and working great. 

So does this mean you have one set of speakers on S1 (Platbar,Play 3 and Connect Amp), and your other speakers on the new app?

This could be one of the reasons so many users have connection issues: multiple routers

And while many will not admit to this, they blame Sonos in an attempt to hide this fact. You do not have to be a network engineer for Sonos to work. You just need to follow recommendations.

No, all speakers are on the latest version of the Sonos app - the Arc+Surriound+Sub (my home theater setup) are on one SSID - that is the wireless AP provided by my ISP and all other speakers are on a different SSID provided by the Aruba AP’s.  I did this because my basement is on the wireless AP provided by my ISP while the other levels of my home are on the Aruba setup.  My house requires multiple AP’s.  

This wouldn't be a supported configuration. It would be recommended to turn off the ISP router WiFi and have all Sonos products connecting to your Aruba WiFi, maybe addition AP required in basement?

There is an installer on reddit that claims he has 100 customers using Aruba with no issues?

https://www.reddit.com/r/sonos/comments/1de6ipu/my_experience_with_the_update_so_far_as_an/

Sounds good, but your recommendation was my initial configuration that didn’t work, so as long as it is working, I’m not touching it :)  I spent 30+ hours trying to get it to working under one SSID. 

I'm having the same problem with Aruba.  This is 100% an Aruba issue.  It happened after the latest firmware upgrade.

For me, all of my Sonos equipment works on the Aruba network except the Arc+Surrounds, Sub.  I can get them to work as separates, but not bonded together.  Seems like more of an issue with Sonos than Aruba. Either way, I got it working now, but just two separate SSID’s for the bonded components.  

hey all,

I have over the years collected plenty of Sonos gear beam,arc,ones,5s, 3s and ran it and still am running it on various “pre-loved” enterprise gear.

Here are my findings:

1. Cisco Catalyst switches
Older gear prior to IOS 15 needed work on getting DLNA working. After 15.x I had no probs.

2. HP / Aruba AOS-S just work. AOS-CX switches detto.
Wireless needs configuring:
a) Instant APs on OS 6.5.x needed disabling ARP filtering and enabling AirGroup and services such as DLNA, Bonjour for apple, etc on the controller.
b) Instant APs on OS 8.12.x however the above was not enough and for some silly reason one has to add Sonos services manually, this helped me plus a reboot of all APs afterwards (who has patience these days...)
https://community.arubanetworks.com/discussion/help-sonos-with-aruba

3. Ubiquiti switches are simple and both older black and the newer silver/white seem to just work. Wireless however, don’t do mixed mode WPA2/WPA3 and from memory the worst thing to enable is any smarts/automation, something along “optimise” or so, that just kills most things.


General rule, if you can ping the IP of a unit and the phone or windows/OSX app struggles, it is broadcast being blocked or “optimised” somewhere.
You may also be fond of VLANs, no problem getting say Sonos on 1 vlan and phones, laptops on another, casting and streaming across them.The hint is to make sure you configure rendezvous points for multicast on your firewalls. Here Aruba can help as it can route locally on APs, if that suits. I got it working further up on a Palo Alto FW as an example just to have visibility and apply ACLs at that level.