Download This Guide
Related Documentation
Example: Configuring Ingress Replication for IP Multicast Using MBGP MVPNs
Requirements
The routers used in this example are Juniper Networks M Series Multiservice Edge Routers, T Series Core Routers, or MX Series 3D Universal Edge Routers. When using ingress replication for IP multicast, each participating router must be configured with BGP for control plane procedures and with ingress replication for the data provider tunnel, which forms a full mesh of MPLS point-to-point LSPs. The ingress replication tunnel can be selective or inclusive, depending on the configuration of the provider tunnel in the routing instance.
Overview
The ingress-replication provider tunnel type uses unicast tunnels between routers to create a multicast distribution tree.
The mpls-internet-multicast routing instance type uses ingress replication provider tunnels to carry IP multicast data between routers through an MPLS cloud, using MBGP (or Next Gen) MVPN. Ingress replication can also be configured when using MVPN to carry multicast data between PE routers.
The mpls-internet-multicast routing instance is a non-forwarding instance used only for control plane procedures. It does not support any interface configurations. Only one mpls-internet-multicast routing instance can be defined for a logical system. All multicast and unicast routes used for IP multicast are associated only with the default routing instance (inet.0), not with a configured routing instance. The mpls-internet-multicast routing instance type is configured for the default master instance on each router, and is also included at the [edit protocols pim] hierarchy level in the default instance.
For each mpls-internet-multicast routing instance, the ingress-replication statement is required under the provider-tunnel statement and also under the [edit routing-instances routing-instance-name provider-tunnel selective group source] hierarchy level.
When a new destination needs to be added to the ingress replication provider tunnel, the resulting behavior differs depending on how the ingress replication provider tunnel is configured:
- create-new-ucast-tunnel—When this statement is configured, a new unicast tunnel to the destination is created, and is deleted when the destination is no longer needed. Use this mode for RSVP LSPs using ingress replication.
- label-switched-path-template—When this statement is configured, an LSP template is used for the for the point-to-multipoint LSP for ingress replication.
The IP topology consists of routers on the edge of the IP multicast domain. Each router has a set of IP interfaces configured toward the MPLS cloud and a set of interfaces configured toward the IP routers. See Figure 1. Internet multicast traffic is carried between the IP routers, through the MPLS cloud, using ingress replication tunnels for the data plane and a full-mesh IBGP session for the control plane.
Figure 1: Internet Multicast Topology
Configuration
CLI Quick Configuration
To quickly configure this example, copy the following commands, paste them into a text file, remove any line breaks, change any details necessary to match your network configuration, and then copy and paste the commands into the CLI at the [edit] hierarchy level.
Step-by-Step Procedure
The following example requires you to navigate various levels in the configuration hierarchy. For information about navigating the CLI, see Using the CLI Editor in Configuration Mode in the Junos OS CLI User Guide .
The following example shows how to configure ingress replication on IP multicast instance IM-A with the routing instance type mpls-internet-multicast. Additionally, this example shows how to configure a selective provider tunnel that selects a new unicast tunnel each time a new destination needs to be added to the multicast distribution tree.
- Configure the routing instance type for IM-A to be mpls-internet-multicast.
[edit routing-instances]user@host# set IM-A instance-type mpls-internet-multicast - Configure the ingress replication provider tunnel to create
a new unicast tunnel each time a destination needs to be added to
the multicast distribution tree.
[edit routing-instances]user@host# set IM-A provider-tunnel ingress-replication create-new-ucast-tunnel
Note: Alternatively, use the label-switched-path-template statement to configure a point-point LSP for the ingress tunnel.
- Configure the point-to-point LSP to use the default template
settings (this is needed only when using RSVP tunnels).
[edit routing-instances]user@host# set IM-A provider-tunnel ingress-replication label-switched-path label-switched-path-template default-template - Configure selective ingress replication provider tunnels.
[edit routing-instances]user@host# set IM-A provider-tunnel selective group 232.1.1.1/32 source 192.168.195.145/32 ingress-replication label-switched-path - Configure the MVPN Protocol in the routing instance.
[edit routing-instances]user@host# set IM-A protocols mvpnuser@host# up - Add the mpls-internet-multicast configuration
statement under the [edit protocols pim] hierarchy level
in the master instance.
[edit protocols]user@host# set pim mpls-internet-multicast - Commit the configuration.
[edit]user@host# commit - Use the show ingress-replication mvpn command
to check the ingress replication status.
[edit]user@host# run show ingress-replication mvpnIngress Tunnel: mvpn:1 Application: MVPN Unicast tunnels Leaf Address Tunnel-type Mode State 10.255.245.2 P2P LSP New Up 10.255.245.4 P2P LSP New Up - Use the show mvpn instance command to show the
ingress replication tunnel type.
[edit]user@host# run show mvpn instance IM-AMVPN instance: Legend for provider tunnel I-P-tnl -- inclusive provider tunnel S-P-tnl -- selective provider tunnel Legend for c-multicast routes properties (Pr) DS -- derived from (*, c-g) RM -- remote VPN route Instance : IM-A MVPN Mode : SPT-ONLY Provider tunnel: S-P-tnl:INGRESS-REPLICATION:MPLS Label 18:10.255.245.6 Neighbor S-P-tnl 10.255.245.2 INGRESS-REPLICATION:MPLS Label 22:10.255.245.2 10.255.245.7 INGRESS-REPLICATION:MPLS Label 19:10.255.245.7
