Cloud Managed Networks

 View Only
last person joined: 2 days ago 

Forum to discuss all things related to HPE Aruba Networking Central and UXI Network Management, including deployment of managed networks, configuration, best practices, APIs, Cloud Guest, AIOps, Presence Analytics, and other included Applications
Back to discussions
Expand all | Collapse all

ARUBA CX Switch + Dante Audinate Configuration

This thread has been viewed 33 times

  • 1.  ARUBA CX Switch + Dante Audinate Configuration

    Posted 23 days ago

    I have been having issues discovering Dante devices in the Dante Controller software.

    Our network consists of a CX 6200 Stack and CX 6100 edge switches.

    L3 routing happens on the 6200 stack with a seperate vlan dedicated to the Dante network.  Dante devices get IP addresses and ping request work to them both on that vlan and others.

    I have been through and done the Multicast setup's ( hopefully correctly) and can see multicast groups being established on that vlan.
    When directly connected to a switch with a Dante box on the same vlan, Dante Controller can discover that device, but no others on the network.

    Any thoughts on where I could be going wrong? is the mdns-sd blocking the discover? any example configurations?

    Thank you in advanced.



  • 2.  RE: ARUBA CX Switch + Dante Audinate Configuration

    EMPLOYEE
    Posted 22 days ago

    whats the the switch config for it? have you enabled IGMP snooping ?



    ------------------------------
    If my post was useful accept solution and/or give kudos.
    Any opinions expressed here are solely my own and not necessarily that of HPE or Aruba.
    ------------------------------

    Original Message


  • 3.  RE: ARUBA CX Switch + Dante Audinate Configuration

    Posted 21 days ago

    Hi Aruyap thank you for getting back.

    Code snippets of the IGMP Configurations, 

    Switch 1 ( querier )
    vlan 40
        name security
        ip igmp snooping enable

    interface 1/1/48
        description Dante System
        no shutdown
        vlan trunk native 40
        vlan trunk allowed all
        ip igmp snooping fastleave vlan 40


    interface vlan 40
        ip address 10.113.132.2/24
        ip igmp enable
        ip igmp version 2
        ip igmp querier interval 5
        ip igmp robustness 5                                       
        ip igmp last-member-query-interval 2
        ip igmp query-max-response-time 50
        ip igmp static-group 239.254.3.3
        ip igmp static-group 239.255.255.255

    //Outputs

    IGMP group information for group 239.254.3.3

    Interface Name   : vlan40
    VRF Name         : default

    Group Address    : 239.254.3.3
    Last Reporter    :  

                                  V1        V2        Sources   Sources 
    Vers Mode Uptime    Expires   Timer     Timer     Forwarded Blocked 
    ---- ---- --------- --------- --------- --------- --------- --------
                                                                          

    IGMP group information for group 239.255.255.255

    Interface Name   : vlan40
    VRF Name         : default

    Group Address    : 239.255.255.255
    Last Reporter    : 10.113.132.15

                                  V1        V2        Sources   Sources 
    Vers Mode Uptime    Expires   Timer     Timer     Forwarded Blocked 
    ---- ---- --------- --------- --------- --------- --------- --------
    2         2h 29m    0m 35s                        

    Switch 2 
    vlan 40
        name security
        ip igmp snooping enable
        ip igmp snooping version 2

    interface 1/1/18
        no shutdown
        vlan trunk native 40
        vlan trunk allowed all
        ip igmp snooping forward vlan 40
        ip igmp snooping fastleave vlan 40

    interface vlan 40
        ip igmp enable
        ip igmp version 2
        no ip igmp querier
        ip igmp robustness 5
        ip igmp last-member-query-interval 2
        ip igmp query-max-response-time 50



    Original Message


  • 4.  RE: ARUBA CX Switch + Dante Audinate Configuration

    Posted 22 days ago

    Hi,

    Dante does not go trough routing so to use DC (dante controller) you need to be in same L2 network with dante gear.

    Dante's 224.0.0.230-234 multicasts and audio packets TTL is 1 so it will not go through router. Dante Domain Manager changes game but it is bit expensive to have only routed streams.



    ------------------------------
    Jori Luoto
    AV-IT Specialist
    ------------------------------

    Original Message


  • 5.  RE: ARUBA CX Switch + Dante Audinate Configuration

    Posted 21 days ago

    Hi Jori,

    Thank you for responding, All devices are on the same vlan. I can see multicast traffic on the 224.0.0.230-234 ranges.  After running some packet captures I found that MDNS traffic was being blocked even on the same vlan.

    I tried adding the services to our mdns-service allows but it still didn't work.

    Services added
        id _netaudio-arc._udp.local
        id _netaudio-cmc._udp.local

    After disabling mdns-sd globally Dante Controller can now see the devices but only in Device Info | Clock Status | Network Status when you try to expand a devices config it can't pull any information :/

    In the Wireshark pictures 10.113.132.15 is the controller .10 .11 .12 are the Dante boxes.



    Original Message


  • 6.  RE: ARUBA CX Switch + Dante Audinate Configuration

    Posted 21 days ago

    Good Morning,

    Sorry, while you talked about routing in core I thought you are trying to have separate device network.
    Just to be clear your topolgy is normal star topology and igmp querier is in core? (=6200 stack is core and 6100's connecting to 6200 stack and Switch 1 mentioned in previous messages is 6200 stack) 

    In dante perspective, mDNS distributes names and capabilities for other devices so that one should should run freely in whole vid40.

    Thing I noted from Wireshark capture is that it's missing PTP clocking streams (224.0.1.129) Should have several high priority packets in second...

    Also if you network is large, please do proper QoS configurations there too (PTP clocking to second highest prio and audio to 3rd...)

    This goes off topic but from your osx try to switch off firewall and all other network connections than dante connection and try again...
    If you see devices in Device info but device info/networking/clocking tabs is mostly empty it usually means that you dont get 224.0.0.230-234 streams to dante controller.



    ------------------------------
    Jori Luoto
    AV-IT Specialist
    ------------------------------

    Original Message