Instant On - Wired

Hello,

Anyone familiar with multicast and IGMP snooping on the 1930?
I have a "Aruba 1930 Instant on 24G 4SFP+" with software version 2.7.0. IGMP Snooping is enabled but the switch is still flooding multicast.
Any suggestion what to do or test?

Setup:
1. On switch port 1 I have connected a server which is transmitting multicast feeds on address 239.1.1.n where n is 1 - 9 . The server also runs a igmp querier.
2. On switch port 2 I have connected a client listening / Join on 239.1.1.1
3. On switch port 3 I have connected a laptop running wireshark
The switch configuration is default. The only changes I made (section switching/igmp snooping) is to enable the global igmp snooping function and also enable igmp on the VLAN.

Result:
The result is that on port 3 (laptop+wireshark) I receive all multicast feeds that are transmitted by the server into port 1. i.e. 239.1.1.1 - 9.
This is not what should happen, the switch should not forward any of the multicast’s to port 3 since the laptop has not joined any of the multicast groups.

Details:
On webgui page “IGMP Snooping Multicast Router Interface Configuration” it says "Dynamic: 1”. I guess this is correct. The switch understands that on port 1 we have incoming multicast traffic.
On page “Multicast Forwarding Database” I see one row saying that “239.1.1.1” is forwarded to port 2. This is also correct because the client has joined this group address.
So the status information in the UI looks OK but the reality as seen on port 3 with laptop+wireshark shows that the switch is flooding multicast traffic to all ports.

Kind Regards
Johan

Hi Johan,

I have my team looking into this for you. I appreciate your patience. 

------------------------------
Aruba Instant On Communications
------------------------------

Original Message:
Sent: 02-25-2023 10:21 AM
From: JT6
Subject: 1930 IGMP Snooping enabled but still multicast flooding

Hello,

Anyone familiar with multicast and IGMP snooping on the 1930?
I have a "Aruba 1930 Instant on 24G 4SFP+" with software version 2.7.0. IGMP Snooping is enabled but the switch is still flooding multicast.
Any suggestion what to do or test?

Setup:
1. On switch port 1 I have connected a server which is transmitting multicast feeds on address 239.1.1.n where n is 1 - 9 . The server also runs a igmp querier.
2. On switch port 2 I have connected a client listening / Join on 239.1.1.1
3. On switch port 3 I have connected a laptop running wireshark
The switch configuration is default. The only changes I made (section switching/igmp snooping) is to enable the global igmp snooping function and also enable igmp on the VLAN.

Result:
The result is that on port 3 (laptop+wireshark) I receive all multicast feeds that are transmitted by the server into port 1. i.e. 239.1.1.1 - 9.
This is not what should happen, the switch should not forward any of the multicast's to port 3 since the laptop has not joined any of the multicast groups.

Details:
On webgui page "IGMP Snooping Multicast Router Interface Configuration" it says "Dynamic: 1". I guess this is correct. The switch understands that on port 1 we have incoming multicast traffic.
On page "Multicast Forwarding Database" I see one row saying that "239.1.1.1" is forwarded to port 2. This is also correct because the client has joined this group address.
So the status information in the UI looks OK but the reality as seen on port 3 with laptop+wireshark shows that the switch is flooding multicast traffic to all ports.

Kind Regards
Johan

Hey Johan,

My apologies for the delay, but I was advised that you should contact our customer support team. https://www.arubainstanton.com/contact-support/ 

------------------------------
Aruba Instant On Communications
------------------------------

Original Message:
Sent: 02-28-2023 04:39 PM
From: JM52
Subject: 1930 IGMP Snooping enabled but still multicast flooding

Hi Johan,

I have my team looking into this for you. I appreciate your patience. 

------------------------------
Aruba Instant On Communications

Original Message:
Sent: 02-25-2023 10:21 AM
From: JT6
Subject: 1930 IGMP Snooping enabled but still multicast flooding

Hello,

Anyone familiar with multicast and IGMP snooping on the 1930?
I have a "Aruba 1930 Instant on 24G 4SFP+" with software version 2.7.0. IGMP Snooping is enabled but the switch is still flooding multicast.
Any suggestion what to do or test?

Setup:
1. On switch port 1 I have connected a server which is transmitting multicast feeds on address 239.1.1.n where n is 1 - 9 . The server also runs a igmp querier.
2. On switch port 2 I have connected a client listening / Join on 239.1.1.1
3. On switch port 3 I have connected a laptop running wireshark
The switch configuration is default. The only changes I made (section switching/igmp snooping) is to enable the global igmp snooping function and also enable igmp on the VLAN.

Result:
The result is that on port 3 (laptop+wireshark) I receive all multicast feeds that are transmitted by the server into port 1. i.e. 239.1.1.1 - 9.
This is not what should happen, the switch should not forward any of the multicast's to port 3 since the laptop has not joined any of the multicast groups.

Details:
On webgui page "IGMP Snooping Multicast Router Interface Configuration" it says "Dynamic: 1". I guess this is correct. The switch understands that on port 1 we have incoming multicast traffic.
On page "Multicast Forwarding Database" I see one row saying that "239.1.1.1" is forwarded to port 2. This is also correct because the client has joined this group address.
So the status information in the UI looks OK but the reality as seen on port 3 with laptop+wireshark shows that the switch is flooding multicast traffic to all ports.

Kind Regards
Johan

Was wondering @JT6 , @JM52 what ever came of this, was there a bugfix ?

------------------------------
A.N.
------------------------------

Original Message:
Sent: 02-25-2023 10:21 AM
From: JT6
Subject: 1930 IGMP Snooping enabled but still multicast flooding

Hello,

Anyone familiar with multicast and IGMP snooping on the 1930?
I have a "Aruba 1930 Instant on 24G 4SFP+" with software version 2.7.0. IGMP Snooping is enabled but the switch is still flooding multicast.
Any suggestion what to do or test?

Setup:
1. On switch port 1 I have connected a server which is transmitting multicast feeds on address 239.1.1.n where n is 1 - 9 . The server also runs a igmp querier.
2. On switch port 2 I have connected a client listening / Join on 239.1.1.1
3. On switch port 3 I have connected a laptop running wireshark
The switch configuration is default. The only changes I made (section switching/igmp snooping) is to enable the global igmp snooping function and also enable igmp on the VLAN.

Result:
The result is that on port 3 (laptop+wireshark) I receive all multicast feeds that are transmitted by the server into port 1. i.e. 239.1.1.1 - 9.
This is not what should happen, the switch should not forward any of the multicast's to port 3 since the laptop has not joined any of the multicast groups.

Details:
On webgui page "IGMP Snooping Multicast Router Interface Configuration" it says "Dynamic: 1". I guess this is correct. The switch understands that on port 1 we have incoming multicast traffic.
On page "Multicast Forwarding Database" I see one row saying that "239.1.1.1" is forwarded to port 2. This is also correct because the client has joined this group address.
So the status information in the UI looks OK but the reality as seen on port 3 with laptop+wireshark shows that the switch is flooding multicast traffic to all ports.

Kind Regards
Johan

Was wondering @JT52  @JT6 was this fixed ?

------------------------------
A.N.
------------------------------

Original Message:
Sent: 02-25-2023 10:21 AM
From: JT6
Subject: 1930 IGMP Snooping enabled but still multicast flooding

Hello,

Anyone familiar with multicast and IGMP snooping on the 1930?
I have a "Aruba 1930 Instant on 24G 4SFP+" with software version 2.7.0. IGMP Snooping is enabled but the switch is still flooding multicast.
Any suggestion what to do or test?

Setup:
1. On switch port 1 I have connected a server which is transmitting multicast feeds on address 239.1.1.n where n is 1 - 9 . The server also runs a igmp querier.
2. On switch port 2 I have connected a client listening / Join on 239.1.1.1
3. On switch port 3 I have connected a laptop running wireshark
The switch configuration is default. The only changes I made (section switching/igmp snooping) is to enable the global igmp snooping function and also enable igmp on the VLAN.

Result:
The result is that on port 3 (laptop+wireshark) I receive all multicast feeds that are transmitted by the server into port 1. i.e. 239.1.1.1 - 9.
This is not what should happen, the switch should not forward any of the multicast's to port 3 since the laptop has not joined any of the multicast groups.

Details:
On webgui page "IGMP Snooping Multicast Router Interface Configuration" it says "Dynamic: 1". I guess this is correct. The switch understands that on port 1 we have incoming multicast traffic.
On page "Multicast Forwarding Database" I see one row saying that "239.1.1.1" is forwarded to port 2. This is also correct because the client has joined this group address.
So the status information in the UI looks OK but the reality as seen on port 3 with laptop+wireshark shows that the switch is flooding multicast traffic to all ports.

Kind Regards
Johan

Original Message:
Sent: 4/1/2024 1:59:00 PM
From: virtualistic
Subject: RE: 1930 IGMP Snooping enabled but still multicast flooding

Was wondering @JT52  @JT6 was this fixed ?

------------------------------
aleks nikolic
------------------------------

Original Message:
Sent: 02-25-2023 10:21 AM
From: JT6
Subject: 1930 IGMP Snooping enabled but still multicast flooding

Hello,

Anyone familiar with multicast and IGMP snooping on the 1930?
I have a "Aruba 1930 Instant on 24G 4SFP+" with software version 2.7.0. IGMP Snooping is enabled but the switch is still flooding multicast.
Any suggestion what to do or test?

Setup:
1. On switch port 1 I have connected a server which is transmitting multicast feeds on address 239.1.1.n where n is 1 - 9 . The server also runs a igmp querier.
2. On switch port 2 I have connected a client listening / Join on 239.1.1.1
3. On switch port 3 I have connected a laptop running wireshark
The switch configuration is default. The only changes I made (section switching/igmp snooping) is to enable the global igmp snooping function and also enable igmp on the VLAN.

Result:
The result is that on port 3 (laptop+wireshark) I receive all multicast feeds that are transmitted by the server into port 1. i.e. 239.1.1.1 - 9.
This is not what should happen, the switch should not forward any of the multicast's to port 3 since the laptop has not joined any of the multicast groups.

Details:
On webgui page "IGMP Snooping Multicast Router Interface Configuration" it says "Dynamic: 1". I guess this is correct. The switch understands that on port 1 we have incoming multicast traffic.
On page "Multicast Forwarding Database" I see one row saying that "239.1.1.1" is forwarded to port 2. This is also correct because the client has joined this group address.
So the status information in the UI looks OK but the reality as seen on port 3 with laptop+wireshark shows that the switch is flooding multicast traffic to all ports.

Kind Regards
Johan

Try switching to IGMP v3 and see if that helps

------------------------------
Richard Simpkins
------------------------------

Original Message:
Sent: 04-02-2024 12:05 PM
From: JT6
Subject: 1930 IGMP Snooping enabled but still multicast flooding

Hi,

No it was not fixed.

/JT6

Original Message:
Sent: 4/1/2024 1:59:00 PM
From: virtualistic
Subject: RE: 1930 IGMP Snooping enabled but still multicast flooding

Was wondering @JT52  @JT6 was this fixed ?

------------------------------
aleks nikolic

Original Message:
Sent: 02-25-2023 10:21 AM
From: JT6
Subject: 1930 IGMP Snooping enabled but still multicast flooding

Hello,

Anyone familiar with multicast and IGMP snooping on the 1930?
I have a "Aruba 1930 Instant on 24G 4SFP+" with software version 2.7.0. IGMP Snooping is enabled but the switch is still flooding multicast.
Any suggestion what to do or test?

Setup:
1. On switch port 1 I have connected a server which is transmitting multicast feeds on address 239.1.1.n where n is 1 - 9 . The server also runs a igmp querier.
2. On switch port 2 I have connected a client listening / Join on 239.1.1.1
3. On switch port 3 I have connected a laptop running wireshark
The switch configuration is default. The only changes I made (section switching/igmp snooping) is to enable the global igmp snooping function and also enable igmp on the VLAN.

Result:
The result is that on port 3 (laptop+wireshark) I receive all multicast feeds that are transmitted by the server into port 1. i.e. 239.1.1.1 - 9.
This is not what should happen, the switch should not forward any of the multicast's to port 3 since the laptop has not joined any of the multicast groups.

Details:
On webgui page "IGMP Snooping Multicast Router Interface Configuration" it says "Dynamic: 1". I guess this is correct. The switch understands that on port 1 we have incoming multicast traffic.
On page "Multicast Forwarding Database" I see one row saying that "239.1.1.1" is forwarded to port 2. This is also correct because the client has joined this group address.
So the status information in the UI looks OK but the reality as seen on port 3 with laptop+wireshark shows that the switch is flooding multicast traffic to all ports.

Kind Regards
Johan

I have been looking to replace my current core switch with a 1930, but if IGMP support is broken, I will need to reconsider.

------------------------------
Jim
------------------------------

Original Message:
Sent: 04-02-2024 12:05 PM
From: JT6
Subject: 1930 IGMP Snooping enabled but still multicast flooding

Hi,

No it was not fixed.

/JT6

Original Message:
Sent: 4/1/2024 1:59:00 PM
From: virtualistic
Subject: RE: 1930 IGMP Snooping enabled but still multicast flooding

Was wondering @JT52  @JT6 was this fixed ?

------------------------------
aleks nikolic

Original Message:
Sent: 02-25-2023 10:21 AM
From: JT6
Subject: 1930 IGMP Snooping enabled but still multicast flooding

Hello,

Anyone familiar with multicast and IGMP snooping on the 1930?
I have a "Aruba 1930 Instant on 24G 4SFP+" with software version 2.7.0. IGMP Snooping is enabled but the switch is still flooding multicast.
Any suggestion what to do or test?

Setup:
1. On switch port 1 I have connected a server which is transmitting multicast feeds on address 239.1.1.n where n is 1 - 9 . The server also runs a igmp querier.
2. On switch port 2 I have connected a client listening / Join on 239.1.1.1
3. On switch port 3 I have connected a laptop running wireshark
The switch configuration is default. The only changes I made (section switching/igmp snooping) is to enable the global igmp snooping function and also enable igmp on the VLAN.

Result:
The result is that on port 3 (laptop+wireshark) I receive all multicast feeds that are transmitted by the server into port 1. i.e. 239.1.1.1 - 9.
This is not what should happen, the switch should not forward any of the multicast's to port 3 since the laptop has not joined any of the multicast groups.

Details:
On webgui page "IGMP Snooping Multicast Router Interface Configuration" it says "Dynamic: 1". I guess this is correct. The switch understands that on port 1 we have incoming multicast traffic.
On page "Multicast Forwarding Database" I see one row saying that "239.1.1.1" is forwarded to port 2. This is also correct because the client has joined this group address.
So the status information in the UI looks OK but the reality as seen on port 3 with laptop+wireshark shows that the switch is flooding multicast traffic to all ports.

Kind Regards
Johan

Im having this exact problem on a customer site with IPTV. despite having a querier set and all the switches having snooping turned on. Im still getting mulkticast flooding. Is there any update regarding this????

------------------------------
Richard Simpkins
------------------------------

Original Message:
Sent: 02-25-2023 10:21 AM
From: JT6
Subject: 1930 IGMP Snooping enabled but still multicast flooding

Hello,

Anyone familiar with multicast and IGMP snooping on the 1930?
I have a "Aruba 1930 Instant on 24G 4SFP+" with software version 2.7.0. IGMP Snooping is enabled but the switch is still flooding multicast.
Any suggestion what to do or test?

Setup:
1. On switch port 1 I have connected a server which is transmitting multicast feeds on address 239.1.1.n where n is 1 - 9 . The server also runs a igmp querier.
2. On switch port 2 I have connected a client listening / Join on 239.1.1.1
3. On switch port 3 I have connected a laptop running wireshark
The switch configuration is default. The only changes I made (section switching/igmp snooping) is to enable the global igmp snooping function and also enable igmp on the VLAN.

Result:
The result is that on port 3 (laptop+wireshark) I receive all multicast feeds that are transmitted by the server into port 1. i.e. 239.1.1.1 - 9.
This is not what should happen, the switch should not forward any of the multicast's to port 3 since the laptop has not joined any of the multicast groups.

Details:
On webgui page "IGMP Snooping Multicast Router Interface Configuration" it says "Dynamic: 1". I guess this is correct. The switch understands that on port 1 we have incoming multicast traffic.
On page "Multicast Forwarding Database" I see one row saying that "239.1.1.1" is forwarded to port 2. This is also correct because the client has joined this group address.
So the status information in the UI looks OK but the reality as seen on port 3 with laptop+wireshark shows that the switch is flooding multicast traffic to all ports.

Kind Regards
Johan

A new firmware was released have you tried it @richard_tricky ?
https://community.arubainstanton.com/blogs/jamie-easly1/2020/06/03/instant-on-1930-switching-software-portal

------------------------------
aleks nikolic
------------------------------

Original Message:
Sent: 04-11-2024 08:14 AM
From: richard_tricky
Subject: 1930 IGMP Snooping enabled but still multicast flooding

Im having this exact problem on a customer site with IPTV. despite having a querier set and all the switches having snooping turned on. Im still getting mulkticast flooding. Is there any update regarding this????

------------------------------
Richard Simpkins

Original Message:
Sent: 02-25-2023 10:21 AM
From: JT6
Subject: 1930 IGMP Snooping enabled but still multicast flooding

Hello,

Anyone familiar with multicast and IGMP snooping on the 1930?
I have a "Aruba 1930 Instant on 24G 4SFP+" with software version 2.7.0. IGMP Snooping is enabled but the switch is still flooding multicast.
Any suggestion what to do or test?

Setup:
1. On switch port 1 I have connected a server which is transmitting multicast feeds on address 239.1.1.n where n is 1 - 9 . The server also runs a igmp querier.
2. On switch port 2 I have connected a client listening / Join on 239.1.1.1
3. On switch port 3 I have connected a laptop running wireshark
The switch configuration is default. The only changes I made (section switching/igmp snooping) is to enable the global igmp snooping function and also enable igmp on the VLAN.

Result:
The result is that on port 3 (laptop+wireshark) I receive all multicast feeds that are transmitted by the server into port 1. i.e. 239.1.1.1 - 9.
This is not what should happen, the switch should not forward any of the multicast's to port 3 since the laptop has not joined any of the multicast groups.

Details:
On webgui page "IGMP Snooping Multicast Router Interface Configuration" it says "Dynamic: 1". I guess this is correct. The switch understands that on port 1 we have incoming multicast traffic.
On page "Multicast Forwarding Database" I see one row saying that "239.1.1.1" is forwarded to port 2. This is also correct because the client has joined this group address.
So the status information in the UI looks OK but the reality as seen on port 3 with laptop+wireshark shows that the switch is flooding multicast traffic to all ports.

Kind Regards
Johan

 Even with IGMP snooping enabled in 1930 switches, multicast flooding issues may persist due to various factors. buy cox internet  Common causes include misconfigurations, network topology issues, or incompatible firmware versions. Troubleshoot by verifying IGMP snooping settings, ensuring proper VLAN configurations, and checking for multicast group membership consistency. Additionally, review switch logs for error messages and consult technical documentation or support channels for further assistance in resolving the problem effectively.    

------------------------------
daniel thomas
------------------------------

Original Message:
Sent: 02-25-2023 10:21 AM
From: JT6
Subject: 1930 IGMP Snooping enabled but still multicast flooding

Hello,

Anyone familiar with multicast and IGMP snooping on the 1930?
I have a "Aruba 1930 Instant on 24G 4SFP+" with software version 2.7.0. IGMP Snooping is enabled but the switch is still flooding multicast.
Any suggestion what to do or test?

Setup:
1. On switch port 1 I have connected a server which is transmitting multicast feeds on address 239.1.1.n where n is 1 - 9 . The server also runs a igmp querier.
2. On switch port 2 I have connected a client listening / Join on 239.1.1.1
3. On switch port 3 I have connected a laptop running wireshark
The switch configuration is default. The only changes I made (section switching/igmp snooping) is to enable the global igmp snooping function and also enable igmp on the VLAN.

Result:
The result is that on port 3 (laptop+wireshark) I receive all multicast feeds that are transmitted by the server into port 1. i.e. 239.1.1.1 - 9.
This is not what should happen, the switch should not forward any of the multicast's to port 3 since the laptop has not joined any of the multicast groups.

Details:
On webgui page "IGMP Snooping Multicast Router Interface Configuration" it says "Dynamic: 1". I guess this is correct. The switch understands that on port 1 we have incoming multicast traffic.
On page "Multicast Forwarding Database" I see one row saying that "239.1.1.1" is forwarded to port 2. This is also correct because the client has joined this group address.
So the status information in the UI looks OK but the reality as seen on port 3 with laptop+wireshark shows that the switch is flooding multicast traffic to all ports.

Kind Regards
Johan