- play_arrow Overview
- play_arrow Managing Group Membership
- play_arrow Configuring IGMP and MLD
- play_arrow Configuring IGMP Snooping
- IGMP Snooping Overview
- Overview of Multicast Forwarding with IGMP Snooping or MLD Snooping in an EVPN-VXLAN Environment
- Configuring IGMP Snooping on Switches
- Example: Configuring IGMP Snooping on Switches
- Example: Configuring IGMP Snooping on EX Series Switches
- Verifying IGMP Snooping on EX Series Switches
- Changing the IGMP Snooping Group Timeout Value on Switches
- Monitoring IGMP Snooping
- Example: Configuring IGMP Snooping
- Example: Configuring IGMP Snooping on SRX Series Devices
- Configuring Point-to-Multipoint LSP with IGMP Snooping
- play_arrow Configuring MLD Snooping
- Understanding MLD Snooping
- Configuring MLD Snooping on an EX Series Switch VLAN (CLI Procedure)
- Configuring MLD Snooping on a Switch VLAN with ELS Support (CLI Procedure)
- Example: Configuring MLD Snooping on EX Series Switches
- Example: Configuring MLD Snooping on SRX Series Devices
- Configuring MLD Snooping Tracing Operations on EX Series Switches (CLI Procedure)
- Configuring MLD Snooping Tracing Operations on EX Series Switch VLANs (CLI Procedure)
- Example: Configuring MLD Snooping on EX Series Switches
- Example: Configuring MLD Snooping on Switches with ELS Support
- Verifying MLD Snooping on EX Series Switches (CLI Procedure)
- Verifying MLD Snooping on Switches
- play_arrow Configuring Multicast VLAN Registration
-
- play_arrow Configuring Multicast Routing Protocols
- play_arrow Connecting Routing Domains Using MSDP
- play_arrow Handling Session Announcements with SAP and SDP
- play_arrow Facilitating Multicast Delivery Across Unicast-Only Networks with AMT
- play_arrow Routing Content to Densely Clustered Receivers with DVMRP
-
- play_arrow Configuring Multicast VPNs
- play_arrow Configuring Draft-Rosen Multicast VPNs
- Draft-Rosen Multicast VPNs Overview
- Example: Configuring Any-Source Draft-Rosen 6 Multicast VPNs
- Example: Configuring a Specific Tunnel for IPv4 Multicast VPN Traffic (Using Draft-Rosen MVPNs)
- Example: Configuring Source-Specific Draft-Rosen 7 Multicast VPNs
- Understanding Data MDTs
- Example: Configuring Data MDTs and Provider Tunnels Operating in Any-Source Multicast Mode
- Example: Configuring Data MDTs and Provider Tunnels Operating in Source-Specific Multicast Mode
- Examples: Configuring Data MDTs
- play_arrow Configuring Next-Generation Multicast VPNs
- Understanding Next-Generation MVPN Network Topology
- Understanding Next-Generation MVPN Concepts and Terminology
- Understanding Next-Generation MVPN Control Plane
- Next-Generation MVPN Data Plane Overview
- Enabling Next-Generation MVPN Services
- Generating Next-Generation MVPN VRF Import and Export Policies Overview
- Multiprotocol BGP MVPNs Overview
- Configuring Multiprotocol BGP Multicast VPNs
- BGP-MVPN Inter-AS Option B Overview
- ACX Support for BGP MVPN
- Example: Configuring MBGP MVPN Extranets
- Understanding Redundant Virtual Tunnel Interfaces in MBGP MVPNs
- Example: Configuring Redundant Virtual Tunnel Interfaces in MBGP MVPNs
- Understanding Sender-Based RPF in a BGP MVPN with RSVP-TE Point-to-Multipoint Provider Tunnels
- Example: Configuring Sender-Based RPF in a BGP MVPN with RSVP-TE Point-to-Multipoint Provider Tunnels
- Example: Configuring Sender-Based RPF in a BGP MVPN with MLDP Point-to-Multipoint Provider Tunnels
- Configuring MBGP MVPN Wildcards
- Distributing C-Multicast Routes Overview
- Exchanging C-Multicast Routes
- Generating Source AS and Route Target Import Communities Overview
- Originating Type 1 Intra-AS Autodiscovery Routes Overview
- Signaling Provider Tunnels and Data Plane Setup
- Anti-spoofing support for MPLS labels in BGP/MPLS IP VPNs (Inter-AS Option B)
- BGP-MVPN SD-WAN Overlay
- play_arrow Configuring PIM Join Load Balancing
- Use Case for PIM Join Load Balancing
- Configuring PIM Join Load Balancing
- PIM Join Load Balancing on Multipath MVPN Routes Overview
- Example: Configuring PIM Join Load Balancing on Draft-Rosen Multicast VPN
- Example: Configuring PIM Join Load Balancing on Next-Generation Multicast VPN
- Example: Configuring PIM Make-Before-Break Join Load Balancing
- Example: Configuring PIM State Limits
-
- play_arrow General Multicast Options
- play_arrow Bit Index Explicit Replication (BIER)
- play_arrow Prevent Routing Loops with Reverse Path Forwarding
- play_arrow Use Multicast-Only Fast Reroute (MoFRR) to Minimize Packet Loss During Link Failures
- play_arrow Enable Multicast Between Layer 2 and Layer 3 Devices Using Snooping
- play_arrow Configure Multicast Routing Options
- play_arrow Controller-Based BGP Multicast Signaling
-
- play_arrow Troubleshooting
- play_arrow Knowledge Base
-
- play_arrow Configuration Statements and Operational Commands
Example: Configuring SSM Maps for Different Groups to Different Sources
Multiple SSM Maps and Groups for Interfaces
You can configure multiple source-specific multicast (SSM) maps so that different groups map to different sources, which enables a single multicast group to map to different sources for different interfaces.
Example: Configuring Multiple SSM Maps Per Interface
This example shows how to assign more than one SSM map to an IGMP interface.
Requirements
This example requires Junos OS Release 11.4 or later.
Overview
In this example, you configure a routing policy, POLICY-ipv4-example1, that maps multicast group join messages over an IGMP logical interface to IPv4 multicast source addresses based on destination IP address as follows:
Routing Policy Name | Multicast Group Join Messages for a Route Filter at This Destination Address | Multicast Source Addresses |
|---|---|---|
POLICY-ipv4-example1 term 1 | 232.1.1.1 | 10.10.10.4, 192.168.43.66 |
POLICY-ipv4-example1 term 2 | 232.1.1.2 | 10.10.10.5, 192.168.43.67 |
You apply routing policy POLICY-ipv4-example1 to IGMP logical interface fe-0/1/0.0.
Configuration
The following example requires that you navigate various levels in the configuration hierarchy. For information about navigating the CLI, see the Junos OS CLI User Guide.
To configure this example, perform the following task:
CLI Quick Configuration
To quickly configure this example, copy the following
configuration commands into a text file, remove any line breaks, change
any details necessary to match your network configuration, copy and
paste the commands into the CLI at the [edit] hierarchy
level, and then enter commit from configuration mode.
set policy-options policy-statement POLICY-ipv4-example1 term 1 from route-filter 232.1.1.1/32 exact set policy-options policy-statement POLICY-ipv4-example1 term 1 then ssm-source 10.10.10.4 set policy-options policy-statement POLICY-ipv4-example1 term 1 then ssm-source 192.168.43.66 set policy-options policy-statement POLICY-ipv4-example1 term 1 then accept set policy-options policy-statement POLICY-ipv4-example1 term 2 from route-filter 232.1.1.2/32 exact set policy-options policy-statement POLICY-ipv4-example1 term 2 then ssm-source 10.10.10.5 set policy-options policy-statement POLICY-ipv4-example1 term 2 then ssm-source 192.168.43.67 set policy-options policy-statement POLICY-ipv4-example1 term 2 then accept set protocols igmp interface fe-0/1/0.0 ssm-map-policy POLICY-ipv4-example1
Procedure
Step-by-Step Procedure
To configure multiple SSM maps per interface:
Configure protocol-independent routing options for route filter 232.1.1.1, and specify the multicast source addresses to which matching multicast groups are to be mapped.
content_copy zoom_out_map[edit policy-options policy-statement POLICY-ipv4-example1 term 1] user@host# set from route-filter 232.1.1.1/32 exact user@host# set then ssm-source 10.10.10.4 user@host# set then ssm-source 192.168.43.66 user@host# set then accept
Configure protocol-independent routing options for route filter 232.1.1.2, and specify the multicast source addresses to which matching multicast groups are to be mapped.
content_copy zoom_out_map[edit policy-options policy-statement POLICY-ipv4-example1 term 2] user@host# set from route-filter 232.1.1.2/32 exact user@host# set then ssm-source 10.10.10.5 user@host# set then ssm-source 192.168.43.67 user@host# set then accept
Apply the policy map POLICY-ipv4-example1 to IGMP logical interface fe-0/1/1/0.
Results
After the configuration is committed, confirm the configuration by entering the show policy-options and show protocols configuration mode commands. If the command output does not display the intended configuration, repeat the instructions in this procedure to correct the configuration.
user@host# show policy-options
policy-statement POLICY-ipv4-example1 {
term 1 {
from {
route-filter 232.1.1.1/32 exact;
}
then {
ssm-source [ 10.10.10.4 192.168.43.66 ];
accept;
}
}
term 2{
from {
route-filter 232.1.1.2/32 exact;
}
then {
ssm-source [ 10.10.10.5 192.168.43.67 ];
accept;
}
}
}
user@host# show protocols
igmp {
interface fe-0/1/0.0 {
ssm-map-policy POLICY-ipv4-example1;
}
}
Verification
Confirm that the configuration is working properly.
- Displaying Information About IGMP-Enabled Interfaces
- Displaying the PIM Groups
- Displaying the Entries in the IP Multicast Forwarding Table
Displaying Information About IGMP-Enabled Interfaces
Purpose
Verify that the SSM map policy POLICY-ipv4-example1 is applied to logical interface fe-0/1/0.0.
Action
Use the show igmp interface operational mode command for the IGMP logical interface to which you applied the SSM map policy.
user@host> show igmp interface
Interface: fe-0/1/0.0
Querier: 10.111.30.1
State: Up Timeout: None Version: 2 Groups: 2
SSM Map Policy: POLICY-ipv4-example1;
Configured Parameters:
IGMP Query Interval: 125.0
IGMP Query Response Interval: 10.0
IGMP Last Member Query Interval: 1.0
IGMP Robustness Count: 2
Derived Parameters:
IGMP Membership Timeout: 260.0
IGMP Other Querier Present Timeout: 255.0The command output displays the name of the IGMP logical interface (fe-0/1/0.0), which is the address of the routing device that has been elected to send membership queries and group information.
Displaying the PIM Groups
Purpose
Verify the Protocol Independent Multicast (PIM) source and group pair (S,G) entries.
Action
Use the show pim join extensive 232.1.1.1 operational mode command to display the PIM source and group pair (S,G) entries for the 232.1.1.1 group.
Displaying the Entries in the IP Multicast Forwarding Table
Purpose
Verify that the IP multicast forwarding table displays the multicast route state.
Action
Use the show multicast route extensive operational mode command to display the entries in the IP multicast forwarding table to verify that the Route state is active and that the Forwarding state is forwarding.