Jump to content

ehidle

c4Forums Member
  • Content count

    11
  • Joined

  • Last visited

  1. Network Setup Best Practices

    Right?? It's a 24-port GbE switch with non-blocking fabric... unless Control4 is asking for more than a gigabit, it's not getting bottlenecked Anyway I've disabled all the management stuff, and the auditor was out there last night and said basically the problems are in how the first two integrators set up the system. So it seems there is light at the end of the tunnel. Maybe the third integrator is the charm? I sure hope so. Thanks again for the help!
  2. Network Setup Best Practices

    Hey I totally understand. I don't just assume that my stuff is good, and I've stated here several times that I know very little about this system, and I appreciate the learning! The managed switch was installed by the first integrator at the insistence that my unmanaged switch was the problem. That was all them, and I just picked it up after they were fired for not being able to make the system work (a decision I had no part in). I haven't changed any of the switch settings since I inherited it (and luckily the first integrator didn't change the default login on the switch). There is nothing in this network that I do that requires STP at all, so I'll turn it off and see what happens. See, This is why I am asking for a document But, I understand their hesitance in providing one. Router already supports uPNP (although secure uPNP, as I will not allow a host to set a forward for another host, and I don't let anybody open privileged ports), and we turned on Wifi multicast long ago. We'll see what happens.
  3. Network Setup Best Practices

    It could very well be that the speakers themselves are not Sonos speakers, I just need to find out. Yep, broadcast storms are definitely a bad thing, but STP are enabled on the switch and the Sonos ZPs, and indeed the wireless on one of the Sonos ZPs that is on the network is in a blocking state, so there is definitely not a loop. Just relaying what the owner said, which of course may have been paraphrased or not entirely accurate, or maybe I heard wrong. I'm sure there's an "approved list" that they've tested on, but I would really hope a pretty high zoot managed Cisco PoE switch would be up to the task. But again, this goes back to my original question, is there a networking best practices document that states on no uncertain terms how a switch/router must be setup in order to function with C4? I will actually be up there in a couple of weeks for other business so I will have a chance to switch things up when I am there.
  4. Network Setup Best Practices

    Yeah I am not that brave with doing things remotely that can't be undone remotely My mission right now is just to understand how the system works and uses the network. I am not sure the Sonos ZPs even talk directly to the speakers? There are all kinds of C4 equipment there, including a 16 channel amplifier and all sorts of other things - I have about a dozen IP addresses for C4 stuff. In any case, I think the speakers may actually be driven from this 16 channel rackmount amp that is there, but I'm not certain as I've never actually seen it in person. There is an auditor from a third A/V company going out there this afternoon to look over the system and see the state of things. It's a bit of a mess. The owner called C4 directly and the person there told her that they should be using the routers and switches that C4 sells (you don't say)... so now "omg it's the network that is causing everything." Ugh. In any case this is all incredibly helpful so I really am grateful for your time. I've learned quite a bit in the last couple of days!
  5. Network Setup Best Practices

    Stupid question (remember I know almost nothing about this system)... Is there a difference between a Zone Controller and a Zone Player? I only see ZP devices on the network (did I mention that I'm looking at this from 800 miles away and have no physical access? haha) Are these settings in the PC software or is there a magic URL? (or both?)
  6. Network Setup Best Practices

    Okay this is crazy. I can't wrap my head around this. So I checked the other two ZonePlayers. They both come into the same port on the cisco switch, and I've been able to map them out as follows: Cisco GE Port ----> .212 ZP ----> .213 ZP So I looked in the mac tables for Cisco Port GE 5 and there's a third device on that port, and there is traffic on .213's eth1 port, indicating this mysterious third device is getting on the network through .213's bridged Ethernet connector. I looked up the MAC address in the DHCP lease file on the server, and... Drum Roll Please.... It's an android device of some kind, probably a phone. So we have Cisco GE Port ----> .212 ZP ----> .213 ZP ----> Android Phone?!?! What the what??? This can't be right.
  7. Network Setup Best Practices

    Thank you! All of this is helpful for sure. While the issues don't seem to be with the Sonos part of the system, it's something I can check on nevertheless. The devices are indeed Zone Players. After talking to the owner, there are in fact four zones, two in each separate system. All four ZonePlayers are hardwired to the LAN, and the speakers are connected to the Zone Players by the Sonos mesh network. So, here's the ifconfig from one of the ZonePlayers .210 and .211, which are out in the gym, I believe. And from the .211 ZP, it looks like the .210 ZP is creating an internal Ethernet switch (br0) to connect .211 to the network. TX bytes on .211 br0 matches RX bytes on .210 eth1, anyway. Seems logical to me. So the ZonePlayers are daisy-chained, and I seem to remember someone saying not to do that? running /sbin/ifconfig ath0 Link encap:Ethernet HWaddr B8:E9:37:93:5F:AB UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:0 errors:0 dropped:0 overruns:0 frame:0 TX packets:0 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:199 RX bytes:0 (0.0 B) TX bytes:0 (0.0 B) Interrupt:19 Memory:a0000000-a0010000 br0 Link encap:Ethernet HWaddr B8:E9:37:93:5F:AA inet addr:192.168.201.210 Bcast:192.168.201.255 Mask:255.255.254.0 UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:42100270 errors:0 dropped:0 overruns:0 frame:0 TX packets:7487822 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:0 RX bytes:4052931382 (3.7 GiB) TX bytes:2540743858 (2.3 GiB) eth0 Link encap:Ethernet HWaddr B8:E9:37:93:5F:AA UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:51551786 errors:0 dropped:0 overruns:0 frame:0 TX packets:15161941 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:100 RX bytes:3583655923 (3.3 GiB) TX bytes:942572505 (898.9 MiB) Base address:0x8400 eth1 Link encap:Ethernet HWaddr B8:E9:37:93:5F:AA UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:7740362 errors:0 dropped:0 overruns:0 frame:0 TX packets:42390403 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:100 RX bytes:2721077833 (2.5 GiB) TX bytes:2877955365 (2.6 GiB) Base address:0x8500 lo Link encap:Local Loopback inet addr:127.0.0.1 Mask:255.0.0.0 UP LOOPBACK RUNNING MTU:16436 Metric:1 RX packets:322 errors:0 dropped:0 overruns:0 frame:0 TX packets:322 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:0 RX bytes:80144 (78.2 KiB) TX bytes:80144 (78.2 KiB) running /sbin/ifconfig ath0 Link encap:Ethernet HWaddr B8:E9:37:93:5F:DF UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:0 errors:0 dropped:0 overruns:0 frame:0 TX packets:0 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:199 RX bytes:0 (0.0 B) TX bytes:0 (0.0 B) Interrupt:19 Memory:a0000000-a0010000 br0 Link encap:Ethernet HWaddr B8:E9:37:93:5F:DE inet addr:192.168.201.211 Bcast:192.168.201.255 Mask:255.255.254.0 UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:41481156 errors:0 dropped:0 overruns:0 frame:0 TX packets:7740913 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:0 RX bytes:2241887386 (2.0 GiB) TX bytes:2699618232 (2.5 GiB) eth0 Link encap:Ethernet HWaddr B8:E9:37:93:5F:DE UP BROADCAST MULTICAST MTU:1500 Metric:1 RX packets:0 errors:0 dropped:0 overruns:0 frame:0 TX packets:0 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:100 RX bytes:0 (0.0 B) TX bytes:900 (900.0 B) Base address:0x8400 eth1 Link encap:Ethernet HWaddr B8:E9:37:93:5F:DE UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:42391928 errors:0 dropped:0 overruns:0 frame:0 TX packets:7741080 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:100 RX bytes:2878484513 (2.6 GiB) TX bytes:2699670303 (2.5 GiB) Base address:0x8500 lo Link encap:Local Loopback inet addr:127.0.0.1 Mask:255.0.0.0 UP LOOPBACK RUNNING MTU:16436 Metric:1 RX packets:326 errors:0 dropped:0 overruns:0 frame:0 TX packets:326 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:0 RX bytes:82013 (80.0 KiB) TX bytes:82013 (80.0 KiB)
  8. Network Setup Best Practices

    Correct. There are no Control4 wall panels in the Gym - she uses the native Sonos App on her iPads and phone to control the Gym devices (the Gym is a separate "system" from the House, and the phone app can apparently only be linked to one of them). The bridge devices are Ubiquiti Nanobridge 5G22s.
  9. Network Setup Best Practices

    I will certainly ask them about the driver version. This was a new installation last year and it has sometimes worked but not always. It's hard to say really since I've never actually laid hands on it myself, but I hear of issues frequently and have worked with them making various network changes along the way to try and help. This is actually the second A/V company to be on this job. I will try the experiment with her to see if Pause/Play will work once the song is started from the Sonos Controller on the PC. Is there a way to check driver revision from the panel? I may be able to get the info sooner if I walk the owner through that. Thank you! PS. I've attached a very crude drawing of the network topology in case it is helpful Basic_Network.pdf
  10. Network Setup Best Practices

    Thank you all for your responses. Keep in mind that I'm not the guy actually configuring the Sonos and Control4 systems themselves. I only own the network (and to make things more fun, I manage everything remotely and only visit the site a couple of times every year). But, for information's sake and to give more details about the network: Everything is hard wired (almost - buildings on the property are linked with 5GHz bridges, but everything within a building is wired). There are four Sonos devices I can see on the LAN - not sure what they are, but they are small white boxes with a couple of buttons on them. Two of them are in the main house and two are out in another building where the client runs a yoga gym. I believe the A/V company told me at one point that all of the Sonos speakers use the mesh network. The entire property is also covered with dualband Wifi, if that might have anything to do with it. All of the Control4 equipment in the house has its own Cisco switch, which is uplinked to my switch which handles everything else. All of the problems have been stuff like a panel in the house not being able to get music into a room. As an example, the other night, I could load up the Sonos control S/W on a PC on the LAN, and then when the owner picked a song with her iPhone, I could see the song get selected in Sonos, but it wouldn't play. The play animation was going on the panel as if the music were playing, but there was no sound, and Sonos did not show the song was playing. If I then manually started the song in Sonos on the PC, it would start playing just fine. The music library is stored on a Win10 PC in the house. I admit I know precious little about Sonos/Control4 but it looks like something that will be cool to learn about, so I really appreciate your feedback.
  11. Hey everyone, I am the "computer guy" for a friend who has a Control4/Sonos installation. Their A/V company is suggesting that the network setup is the source of some of the problems they're having with the system. I'd like to know if there is a thorough network best practices document that describes in detail the router facilities required by Control4, so that I can make sure the router can meet the requirements. The router is a Linux-based appliance so it is very versatile and can do whatever, but I just need to know what exactly needs to happen for Control4 to be happy. If this is documented somewhere, that's great. Thanks in advance!
×