Help us improve your experience.

Let us know what you think.

Do you have time for a two-minute survey?


Configuring Internet Multicast Using Ingress Replication Provider Tunnels

The routing instance type mpls-internet-multicast uses ingress replication provider tunnels to carry IP multicast data between routers through an MPLS cloud, enabling a faster path for multicast traffic between sender and receiver routers in large-scale implementations.

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 Internet multicast are associated only with the master instance (inet.0), not with the routing instance.

Each router participating in Internet multicast must be configured with BGP MPLS-based Internet multicast 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, matching the configuration of the provider tunnel in the routing instance.

The topology consists of routers on the edge of the IP multicast domain that have a set of IP interfaces and a set of MPLS core-facing interfaces, 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 IGBP session for the control plane.

The mpls-internet-multicast routing instance type is configured for the default master instance on each router to support Internet multicast over MPLS. When using PIM as the multicast protocol, the mpls-internet-multicast configuration statement is also included at the [edit protocols pim] hierarchy level in the master instance. This creates a pseudo-interface that associates PIM with the mpls-internet-multicast routing instance.

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 (Multicast)—When this statement is configured, an LSP template is used for the for the point-to-multipoint LSP for ingress replication.

Figure 1: Internet Multicast TopologyInternet Multicast Topology

Example: Configure Internet Multicast Using Ingress Replication Tunnels

This example configures VPN-B with the instance type mpls-internet-multicast. This example also uses PIM for the multicast protocol.

  1. Configure the routing instance type for VPN-B as mpls-internet-multicast:
  2. Configure the ingress replication provider tunnel to create a new unicast tunnel each time an application requests to add a destination:
  3. Configure the point-to-point LSP to use the default template settings.
  4. Configure the ingress replication provider tunnel to be selective:
  5. Configure MVPN protocol in the routing instance:
  6. Commit the configuration:
  7. Use show command to verify the instance has been created:
  8. Add the mpls-internet-multicast configuration statement under the [edit protocols pim] hierarchy level in the master instance:
  9. Commit the configuration:
  10. Use show ingress-replication mvpn command to verify configuration settings:
  11. Use this if you want to configure the ingress replication provider tunnel to be inclusive:
  12. Use show mvpn instance command to verify tunnel is inclusive: