Switching

Hi,

I have some issue over igmp-snooping with a QFX5100. Setup is simple 😉 (keep in mind, I did try to make it work only with the switch)

I receive multicast stream over interface xe-0/0/1.0 wich is configured as trunk with a native-vlan-id 12. I have 10 interface like that included in the vlan 12.

I have my private subnet on the switch 10.0.0.0/24 (host that will use the multicat stream). The multicast stream comes from my carrier, connected in port xe-0/0/0 and They gave me a 10.20.20.2/29 ip to connect together over the interface.

I did created an irb.12 with those 2 subnet so I can ping both network from the switch. I also configure PIM in wich I had set a static rp with the ip given by my carrier (I did created a static route for this) that include also all the group range. About igmp, I did set it on the irb interface.

From all previous configuration, multicast works like a charm. My probleme is I will get about 2.5Gbps multicast traffic that I want to share accross 10 servers and those have only 1G interfaces. You understand that I need igmp-snooping to work. Probleme is, it doesn't :(. The second I enable snooping, all traffic goes down.

yes, it's very simple:

Yes, here we are. I dont think the first interface is needed:  

vlan CARRIER {

    interface xe-0/0/1.0 {

        multicast-router-interface;

    }

    interface irb.12 {

        multicast-router-interface;

    }

}

Hi !

you wrote:

The second I enable snooping, all traffic goes down"

Did you wait 3 minutes and look what happens then, or did you close and reopen the receiver application, as...

all Multicast protocols are softstate with a typical timeout of 180 sec

when you start IGMP-snooping, the database is empty (the only entry is a multicast wildcard pointing to multicast-router interfaces), so therefore the MC-stream is not forwarded by the switch.

after 120-150 seconds the MC-Router alias QUERIER sends out a general query and then the reciver answer with a report, which the switch uses to fill the snooping database and thus opening ports for specific MC-streams.

So pls check

regards

alexander

I did removed my snooping and my servers was able to see the stream again. Let me try to wait and restart the application.

Ok, I did try to wait and restart my application.. stil noting works.

From what I see, the traffic on the CARRIER port, from wich multicast is comming didn't stopped compared to all other ports

when I was running snooping, i did run some commandes:

show igmp snooping statistics   
Vlan: CARRIER
IGMP Message type      Received       Sent  Rx errors
Membership Query              0         48          0
V1 Membership Report          4          0          0
DVMRP                         0          0          0
PIM V1                        0          0          0
Cisco Trace                   0          0          0
V2 Membership Report          0          0          0
Group Leave                   1          0          0
Mtrace Response               0          0          0
Mtrace Request                0          0          0
Domain Wide Report            0          0          0
V3 Membership Report         63          0          0
Other Unknown types                                 0

IGMP Global Statistics
Bad Length                    0
Bad Checksum                  0
Bad Receive If              152
Rx non-local                  0
Timed out                     0

AND

run show igmp snooping membership                                
Instance: default-switch

Vlan: CARRIER

Learning-Domain: default
Interface: ge-0/0/19.0, Groups: 15      
    Group: 235.1.1.38                   
        Group mode: Include             
        Source: 10.187.124.10           
        Source timeout: 248             
        Last reported by: 10.0.0.104    
        Group timeout:       0 Type: Dynamic
    Group: 235.1.1.59                   
        Group mode: Include             
        Source: 10.187.124.10           
        Source timeout: 248             
        Last reported by: 10.0.0.104    
        Group timeout:       0 Type: Dynamic
    Group: 235.1.1.60                   
        Group mode: Include             
        Source: 10.187.124.10           
        Source timeout: 248             
        Last reported by: 10.0.0.104    
        Group timeout:       0 Type: Dynamic
    Group: 235.1.1.73                   
        Group mode: Include             
        Source: 10.187.124.10           
        Source timeout: 248             
        Last reported by: 10.0.0.104    
        Group timeout:       0 Type: Dynamic

there are some strange things in your output

1.  IGMP version ( the default is 2 ) but in the statistics I see V1 and V3 reports !!!!

which version did you configure ?

2. the interface in the snooping database is ge-0/0/19 ?!   ( you mentioned completely different interface) also those groups seems to be SSM ( group mode include), but per default any PIM router treats 235.x.x.x as ASM

what is the PIM and IGMP config on the switch? do

show pim join

show pim source

show multicast route

show igmp snooping interface

regards

alexander

Hi, 

About your point #2, I was refering about other ports receiving the multicast and the sample I shared is one of them. I didn't include all the output as it's very long. It was a sample.

I'm gonna double check all the version running and will comme back soon with the results.

Thanks for your help.

it's working now.

My mistake was using the same vlan for the source and my private network.

So now, I use 2 vlan, one for the source (only one port) and one for my private network (about 10 ports). Both have different subnet.

Then, I did created 2 irb for each VLAN, setting up my pim, igmp and igmp-snooping and everything works perfectly.