This is a public Discussion Forum  public

Topic

    oldhippie
    Ethernet switch ACN protocol
    Topic posted February 10, 2014 by oldhippieNovice, tagged WWB 6.8.1 
    947 Views, 7 Comments
    Title:
    Ethernet switch ACN protocol
    Personal Computer:
    Panasonic CF 50
    Shure Hardware:
    ULXD
    Description:

    Having a terrible time getting a ethernet switch that will work reliably with wireless workbench 6 and 8 ULXD receivers.

    Is there any way to tell if the ACN protocol would be supported if the switch doesn't specifically say so? We are trying to use Cisco SG 200 series managed switches. Will work ocasionally but won't stay connected.  Network is known good as it's used constantly for our station's automation.

    All of the receivers have the latest firmware in them, are set to static IPs and are given unique IDs.

    Thanks in advance.

     

     

    Answer

     

    • buhmanb

      Hi, Recently there have been a couple different root causes for cases of WWB6 losing connection.  

      1. MacOS 10.9 - added a feature called "App Nap" that puts applications in the background to sleep, thus stopping the heartbeat mechanism that keeps the ACN connection alive.  Solution: Disable "App Nap" for the WWB6 application.

      2. "Green Ethernet" switches that go into a low power mode for ports that it does not think are active.  Solution: Disable "Green Ethernet" features on the switch.  
      Refer to the user guide for the switch.  Example - Chapter 9, page 124- of the Cisco SG 200 administrators guide:
      http://www.cisco.com/c/dam/en/us/td/docs/switches/lan/csbss/sf20x_sg20x/administration_guide/78-21139.pdf

      3. More specific your question about ACN.  ACN utilizes multicast messaging.  Your switch may have been configured to use IGMP or MDL snooping, which if not setup could be blocking some of the multicast traffic to the devices and/or WWB.  Try disabling the IGMP and MDL snooping.  (See chapter 15 of the user guide listed above for the SG200 series.)

      We use the SG200 series in our network labs consisting of 100+ ACN based devices.  So it can work.  

      One thing you can try is to eliminate the SG200 from the equation and see of the problems follow the switch (e.g. its settings) or if problem continues.

      While I would not recommend this for a normal setup, it works for debugging if the ULXD is set to "Switched" mode.
      Connect the Ethernet cable from the PC directly to ULXD4#1's primary port.  Then ULXD4#1's secondary port to ULXD4#2's primary port, etc..
      This creates a "daisy chain" of units.   Now run WWB and see if the problems persist.

      I only use daisy chaining in a pinch - for small configurations or trouble shooting.

      Hope that helps!

    • oldhippie

      Thank you for the quick response. Just for more info, we are using this on windows machines and have the same issue on machines running XP or Win 7 connected right at the switch that's connected to the receivers or further down the chain.

      I'll be trying the suggestions and post back here the results. It's a great learning experience for an old analog TV and Audio Engineer. Thanks again.

    • oldhippie

      Greetings again,

       I've not had any luck after checking the switch settings and have also discoverd the following which is getting me away from suspecting the switches. 

      I can't get the receivers to talk even directly connected to a laptop. Our ULXD4s only have one Ethernet port so I can't daisy chain them. If I connect a receiver directly to the laptop, I can ping it no problem but Wireless workbench will not see it.  Firmware  is 1.4.8.

      Again, Thanks in advance. 

    • buhmanb

      Ah - I assumed you had ULXD4D or ULXD4Q units.  Sorry about that.

      If the turnaround of posting to the forum / waiting for reply is getting too long - please contact support directly.  In the US: (847) 600-8541

      If you can ping, but WWB is failing to discover:

      1.  Confirm the network preferences in WWB:

      Menu > Tools > Preferences > Network 

      Make sure the desired network adapter has been chosen.

       

      AND/OR:  2. Disable or turn OFF any firewall or network security tool on the computer that may be blocking traffic.  Or make sure the Firewall has been configured to allow WWB.

       

      AND/OR: 3. In some cases WWB can get confused if there are multiple adapters on the computer, all connected to the same network.

      e.g. WiFi adapter at IP: 192.168.1.12,  and a wired adapter configured to 192.168.1.15.

      For troubleshooting I often disable all "other" adapters via the control panel, and only enable the adapter that is connected to the gear.  This just eliminates the variables.  Once working, start adding back the other adapters and see when things start failing.  Then you'll have a better idea what might be wrong.

       

      And just to confirm - what version of WWB6 are you running?  Menu: Help > About

      The most recent release is 6.9.0.45. 

      Best luck!

       

       

    • oldhippie

      I apologize for the delay in updating this thread but we are two people down in staff so been pretty busy.

      I've worked on the Cisco CS200 settings some more and have the receivers talking to the laptop right now for testing. When you start the program it doesn't always see all of the receivers unless you power cycle them.  After setting the Green settings and the ACN settings to I hope the proper ones, the switch will let the receicers talk to the laptop but the link lights only blink once every few minutes.

      Is there by chance a list of the proper CS200 switch settings available.  I'm not an IT guy and don't understand the inner workings of these switches enough yet to be comfortable with them. I'm studying but any help would be greatly appreciated.   Thanks again. 

    • buhmanb

      Hi, It sounds like there is something else going on.   A factory default configuration on the switch plus the ULXD4 devices and WWB should simply work.  One should not need to be an IT guy to get this working.  My hunch is there is something simple that we're overlooking.   

      My approach is to eliminate variables, get a simple configuration working, then add other components to the system.

      1. Start with 1 ULXD4, verify the version (1.4.8 or greater) then set the manual IP address to e.g. 10.0.1.11, Subnet Mask: 255.255.255.0, Gateway: 0.0.0.0
      2. Set the Computer's IP address to e.g. 10.0.1.5, Subnet Mask: 255.255.255.0, Gateway: 0.0.0.0.  Then connect the Ethernet cable directly between the ULXD4 and the computer.
      3. With the ULXD4 powered on, start WWB 6.9 (or greater) and make sure the network preference has chosen the adapter "10.0.1.5"
      4. Make sure this "works" consistently before moving on.
      5. Disconnect the Ethernet cable.  Factory default the Switch (unless you have some specific settings you need)
      6. Connect the computer to port 1 of the switch, connect the same ULXD4 unit to port 2 of the switch.  Nothing else.  Power on.
      7. Start WWB and make sure this "works" consistently before moving on.
      8. Now add the next ULXD4 unit to the switch and setup the IP settings (e.g. IP: 10.0.1.12, Sub:255.255.255.0, GW:0.0.0.0) 
      9. Make sure this works consistently before moving on.
      10. Repeat for the rest of the ULXD4 units.
      11. Then start adding any other connections to the switch.  Make note of what was added when things stopped working.

      The most common problems people (including myself) have are a misconfigured setting, or firewall/security utilities on the computer blocking traffic.

      Hope this helps - please give the service department a call if you continue to run into problems.  The team is extremely helpful.  In the US: (847) 600-8541

       

    • oldhippie

      Thank you so much for the quick response. I'll be trying your suggestion and will report back here as well as getting with the support folks if needed. So far it's holding through several reboots of the computer but I'm interested in trying the "default" settings.

      Thanks again.  

     

    © 2009-2014 Shure Incorporated All rights reserved.
    • Privacy
    • Powered by RightNow