While troubleshooting a Multicast issue, you want to check if traffic from the Multicast source or client is being received by the EX switch.

For firewall filter examples on a Junos Layer 3 device, refer to KB28405 - Firewall Filter Examples to verify Multicast traffic is reaching the Layer 3 Junos OS device.

Apply Firewall Filter to EX switch in order to confirm that Multicast traffic is reaching the EX switch

Two Firewall Filter examples related to the network diagram below are provided in this article:

• Example 1:  Firewall Filter used to determine if the L2 EX is receiving Multicast traffic on the ge-0/0/15 interface from the Server (Source)


• Example 2:  Firewall Filter used to determine if the L2 EX is receiving IGMP Reports on the ge-0/0/10 interface from Client 1 (Receiver)

Note: Refer to KB21591 - Sample Multicast Network Topology with EX devices for definitions of the components.

For detailed information on Firewall Filters for EX Series switches, refer to the Technical Documentation: Firewall Filters for EX Series Switches Overview

Example 1 - Firewall Filter:

This example shows you how determine if the L2 EX is receiving Multicast traffic on the ge-0/0/15 interface from the Server (Source) address 192.168.200.10.

This Firewall Filter will accept and count the traffic for the Multicast group 224.100.100.100, from the server 192.168.200.10:

Config:
 
Note:  Firewall Filters have to be mapped to the Interfaces in order to activate.

This command maps the filter Monitor-Ingress-Traffic to the ge-0/0/15 interface (the interface connected to the Server):
 
Verifying the Counters:

The following command reports the packets that match the Firewall Filter.  In this case, the Multicast-Counter has 0 matched packets.  Therefore, it can be concluded that the Multicast stream is not reaching the EX switch.
 

Example 2 - Firewall Filter

This example shows determine if the L2 EX is receiving IGMP Reports on the ge-0/0/10 interface from Client 1 (Receiver).

This Firewall Filter will accept and count the traffic from the Client1 to the Multicast Group address 224.100.100.100.

Config:

[edit]
root@Juniper-L2_EX# set firewall family ethernet-switching filter Monitor-ClientReports term Two from destination-address 224.100.100.100
root@Juniper-L2_EX# set firewall family ethernet-switching filter Monitor-ClientReports term Two from source-address 192.168.100.10
root@Juniper-L2_EX# set firewall family ethernet-switching filter Monitor-ClientReports term Two then count Multicast-Report-Counter
root@Juniper-L2_EX# set firewall family ethernet-switching filter Monitor-ClientReports term Two then accept
root@Juniper-L2_EX# set firewall family ethernet-switching filter Monitor-ClientReports term Default then count Default-Counter
root@Juniper-L2_EX# set firewall family ethernet-switching filter Monitor-ClientReports term Default then accept

Note:  Firewall Filters have to be mapped to the Interfaces in order to activate.

This command maps the filter Monitor-ClientReports to the ge-0/0/10 interface (the interface connected to the receiver):

Verifying the Counters:

The following command reports the packets that match the Firewall Filter.  In this case, the Multicast-Reports-Counter has 0 matched packets.  Therefore, it can be concluded that the Multicast Client IGMP reports are not reaching the EX switch.

2020-04-30: Updated links and minor changes to the config.