Network Management

 View Only

  • 1.  Multicast issue on the new 6100 switch.

    Posted Oct 10, 2022 09:18 AM
    Hello community.
    We have a customer with 20+ switches. 5 of these have devices whitch uses multicast.
    Of these switches there are 3 x 2540, and 1 x 5406 with one 4 x 10 gig module. These switches are connected with one tagged 1G fiber for all other VLAN's and one 10G fiber for the multicast vlan (607). IGMP is configured for vlan 607, the 5406 is configured as the querier. This is a setup whitch works flawlessly.
    Now her's the kicker. We are trying to connect a new switch, on a new floor, for more mulicast devices. Since the 2540 are virtually impossible to get hold of theses days, we are trying to install a new Aruba 6100. As soon as this switch is connected through the configured multicast port, everything else are slowed down, and ping drops are frequent througout.

    The VLAN configuration on the 5406 and the 2540 are more or less equal, like this:

    ## Example of a normal 1G UPLINK port ##
    interface A21
    name "UPLINK"
    tagged vlan 600-606,608-610,613
    untagged vlan 1
    loop-protect
    exit
    ##  Multicast port configuration  ##
    interface D1
    name "VLAN607-PDATA-UPLINK-2540-PORT51"
    tagged vlan 607
    untagged vlan 699
    exit
    interface D2
    name "VLAN607-PDATA-UPLINK-S2540-PORT51"
    tagged vlan 607
    untagged vlan 699
    exit
    interface D3
    name "VLAN607-PDATA-UPLINK-2540-PORT51"
    tagged vlan 607
    untagged vlan 699
    exit
    interface D4
    disable  ##  Currently disabled  ##
    ##  Multicast VLAN configuration  ##
    name "VLAN607-PDATA-UPLINK-6100-PORT26"
    tagged vlan 607
    untagged vlan 699
    exit
    vlan 607
    name "LAN-AUDIO"
    tagged A1,A3,D1-D4
    ip address XX.YY.ZZ.3 255.255.255.0
    ip igmp
    ip igmp querier interval 60
    exit
    ### As soon as the D4 link is activated, there are lots of broadcasts on all the other vlans ###


    Config on the 6100:
    ### Example of a normal 1G UPLINK port ###
    interface 1/1/25
    no shutdown
    vlan trunk native 1
    vlan trunk allowed 600-606,608-613,617
    ### Uplink for multicast vlan, 10Gb ###
    interface 1/1/26
    no shutdown
    vlan trunk native 699
    vlan trunk allowed 607
    vlan 607
    name LAN-AUDIO
    ip igmp snooping enable
    ip igmp snooping version 2
    interface vlan 607
    ip address XX.YY.ZZ.21/24
    ip igmp enable
    ip igmp version 2
    no ip igmp querier

    We are hopeing that there are some gurues out there, on the new 6X00-series switches.
    Is there something special about IGMP Snooping on the 6X00-series?

    ​


  • 2.  RE: Multicast issue on the new 6100 switch.

    Posted Oct 11, 2022 04:53 AM
    Edited by caugdahl Oct 11, 2022 04:54 AM
    Hi! What is the output of the following commands?
    show ip igmp snooping vlan 607 detail
show vlan 607
show spanning-tree​
show interface utilization



  • 3.  RE: Multicast issue on the new 6100 switch.

    Posted Oct 11, 2022 05:11 AM
    Hi.  These are the results on the 6100 switch.  Port 26 is obviously down at the moment, due to traffic overload when opened:

    SW-21# show ip igmp snooping vlan 607 detail
    IGMP Snooping Protocol Info

    Total VLANs with IGMP enabled : 1
    Current count of multicast groups joined : 0

    IGMP Drop Unknown Multicast : Global
    VLAN ID : 607
    VLAN Name : LAN-AUDIO
    IGMP Configured Version : 2
    IGMP Operating Version : 2
    Querier Address :
    Querier Port :
    Querier UpTime :
    Querier Expiration Time :
    Router Detected Port(s) :


    SW-21# show vlan 607

    --------------------------------------------------------------------------------------------------------------
    VLAN Name Status Reason Type Interfaces
    --------------------------------------------------------------------------------------------------------------
    607 LAN-AUDIO up ok static 1/1/3-1/1/6,1/1/24,
    1/1/26-1/1/28

    SW-21# show spanning-tree
    Spanning tree status : Enabled Protocol: MSTP

    MST0
    Root ID Priority : 32768
    MAC-Address: ec:02:73:xx:yy:zz
    This bridge is the root
    Hello time(in seconds):2 Max Age(in seconds):20
    Forward Delay(in seconds):15

    Bridge ID Priority : 32768
    MAC-Address: ec:02:73:xx:yy:zz
    Hello time(in seconds):2 Max Age(in seconds):20
    Forward Delay(in seconds):15

    Port Role State Cost Priority Type BPDU-Tx BPDU-Rx TCN-Tx TCN-Rx
    ------------ -------------- ---------- -------------- ---------- ---------------- ---------- ---------- ---------- ----------
    1/1/1 Disabled Blocking 20000 128 P2P 0 0 0 0
    1/1/2 Disabled Blocking 20000 128 P2P 0 0 0 0
    1/1/3 Designated Forwarding 20000 128 P2P 1248715 0 0 0
    1/1/4 Designated Forwarding 20000 128 P2P 170754 0 0 0
    1/1/5 Disabled Blocking 20000 128 P2P 0 0 0 0
    1/1/6 Disabled Blocking 20000 128 P2P 0 0 0 0
    1/1/7 Disabled Blocking 20000 128 P2P 0 0 0 0
    1/1/8 Disabled Blocking 20000 128 P2P 0 0 0 0
    1/1/9 Disabled Blocking 20000 128 P2P 0 0 0 0
    1/1/10 Disabled Blocking 20000 128 P2P 0 0 0 0
    1/1/11 Disabled Blocking 20000 128 P2P 0 0 0 0
    1/1/12 Disabled Blocking 20000 128 P2P 0 0 0 0
    1/1/13 Disabled Blocking 20000 128 P2P 0 0 0 0
    1/1/14 Disabled Blocking 20000 128 P2P 0 0 0 0
    1/1/15 Disabled Blocking 20000 128 P2P 0 0 0 0
    1/1/16 Disabled Blocking 20000 128 P2P 0 0 0 0
    1/1/17 Disabled Blocking 20000 128 P2P 0 0 0 0
    1/1/18 Disabled Blocking 20000 128 P2P 0 0 0 0
    1/1/19 Disabled Blocking 20000 128 P2P 0 0 0 0
    1/1/20 Disabled Blocking 20000 128 P2P 0 0 0 0
    1/1/21 Disabled Blocking 20000 128 P2P 0 0 0 0
    1/1/22 Disabled Blocking 20000 128 P2P 0 0 0 0
    1/1/23 Disabled Blocking 20000 128 P2P 0 0 0 0
    1/1/24 Disabled Blocking 20000 128 P2P 0 0 0 0
    1/1/25 Designated Forwarding 20000 128 P2P 8 1245659 53 0
    1/1/26 Disabled Blocking 20000 128 P2P 978 622 36 0
    1/1/27 Disabled Blocking 20000 128 P2P 0 0 0 0
    1/1/28 Disabled Blocking 20000 128 P2P 0 0 0 0
    lag1 Disabled Blocking 20000 64 Shr 0 0 0 0

    Number of topology changes : 5
    Last topology change occurred : 1549160 seconds ago

    SW-21#
    Original Message


  • 4.  RE: Multicast issue on the new 6100 switch.

    Posted Oct 11, 2022 05:24 AM
    Edited by caugdahl Oct 11, 2022 05:42 AM
    The command output doesn't paint the picture unless you enable the 10G link.
    Could spanning-tree be blocking the 10G uplink, and sending the multicast stream over the 1G link maybe? You could try tagging my management VLAN on the 10G link and disabling the 1G link.

    EDIT: Just realized the vlan is not tagged on 1G link. Take a look at your spanning-tree configuration across the L2 domain.


    Original Message


  • 5.  RE: Multicast issue on the new 6100 switch.

    Posted Oct 11, 2022 06:33 AM
    Actually, I think Spanning tree is blocking the 10G link, just don't know why.
    I tried to add management vlan to the 10G link, then disable the 1G link and enable the 10G link.  Result was no connection to the switch, and a device connected to vlan 601, on another switch, also lost connection (no answer to ping).
    It's almost as if vlan 1 is running everything (which we don't use).

    At this point we are trying very hard to find another 2540 ;-)
    Original Message


  • 6.  RE: Multicast issue on the new 6100 switch.

    Posted Oct 11, 2022 06:53 AM
    That sounds like MSTP running in default settings on the 6100, and there are possibly multiple instances on the existing switches. In that case you will have the same issues with a brand new 2540. Do "show run spanning-tree" on the 5406.
    Original Message


  • 7.  RE: Multicast issue on the new 6100 switch.

    Posted Oct 11, 2022 07:03 AM
    We don't have spanning tree running.  We have enabled loop-protect.
    Which I just realized.... is't running on the 10G module (D1 to D4)

    SW-3# sh spanning-tree

 Multiple Spanning Tree (MST) Information

  STP Enabled   : No

SW-3# sh run | inc loop
loop-protect A1-A24,B1-B24,C1-C24
loop-protect trap loop-detected
loop-protect disable-timer 3600
HBN-SW-3#
​

    Original Message


  • 8.  RE: Multicast issue on the new 6100 switch.

    Posted Oct 11, 2022 07:12 AM
    Edited by caugdahl Oct 11, 2022 07:13 AM
    I believe loop-protect would still work on just the one link. MSTP on the 6100 should block one of the links eitehr way. As you're not running the same VLAN on both 1G and 10G, I think broadcast storms shouldn't happen. I would opt for further troubleshooting with both links enabled in a planned degraded state. That said I would also migrate to spanning tree if all your devices allows you. Maybe you could use just the 10G link with all VLANs for this switch as a workaround, unless the stream is almost at 10G.

    Original Message


  • 9.  RE: Multicast issue on the new 6100 switch.

    Posted Oct 11, 2022 08:05 AM
    Thank you for your input.
    This is a problem that we can not figure out.  All of the 2540's are configured the same way.  No problem.  It's only when we try to connect the ICMP enabled port on the 6100 that the problem starts.
    You're probably right about running everything on the 10G link.  Won't do that though, until we are onsite.  Just in case ;-)
    Original Message


  • 10.  RE: Multicast issue on the new 6100 switch.

    Posted Oct 11, 2022 08:10 AM
    I understand, hard to troubleshoot the issue while it's not ongoing. Running all traffic on the 10G is probably fine as a workaround.
    Original Message


Related Content