Rate and give feedback:  Feedback Received. Thank You!

Rate and give feedback: 

X

This document helped resolve my issue

Yes No

Additional Comments

800 characters remaining

May we contact you if necessary?

Name:  

E-mail: 

Enter a valid Email ID

Need product assistance? Contact Juniper Support

Submit

This site is protected by hCaptcha and its Privacy Policy and Terms of Service apply.

Configuring Internet Multicast Using Ingress Replication Provider Tunnels

Figure 1: Internet Multicast Topology

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

1. Configure the routing instance type for VPN-B as mpls-internet-multicast:
   user@host# set routing-instances VPN-B instance-type 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:
   user@host# set routing-instances VPN-B provider-tunnel ingress-replication create-new-ucast-tunnel
3. Configure the point-to-point LSP to use the default template settings.
   user@host# set routing-instances VPN-B provider-tunnel ingress-replication label-switched-path label-switched-path-template default-template
4. Configure the ingress replication provider tunnel to be selective:
   user@host# set routing-instances VPN-B provider-tunnel selective group 232.1.1.1/32 source 192.168.195.145/32 ingress-replication label-switched-path
5. Configure MVPN protocol in the routing instance:
   user@host# set routing-instances VPN-B protocols mvpn
6. Commit the configuration:
   user@host# commit
7. Use show command to verify the instance has been created:
   user@host# run show mvpn instance VPN-B

   MVPN 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 : VPN-B
      MVPN Mode : SPT-ONLY
      Provider tunnel: I-P-tnl:INGRESS-REPLICATION:MPLS Label 18:10.255.245.6
      Neighbor               I-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
      C-mcast IPv4 (S:G)     Ptnl                           St
      192.168.195.145/32:232.1.1.1/32 INGRESS-REPLICATION:MPLS Label 
   18:10.255.245.6         RM

8. Add the mpls-internet-multicast configuration statement under the [edit protocols pim] hierarchy level in the master instance:
   user@host# set protocols pim mpls-internet-multicast
9. Commit the configuration:
   user@host# commit
10. Use show ingress-replication mvpn command to verify configuration settings:
    user@host# run show ingress-replication mvpn

    Ingress Tunnel: mvpn:1l
      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
    Ingress Tunnel: mvpn:2
      Application: MVPN
      Unicast tunnels
        Leaf Address       Tunnel-type       Mode       State
        10.255.245.2       P2P LSP           Existing   Up
    

11. Use this if you want to configure the ingress replication provider tunnel to be inclusive:
    user@host# set routing-instances VPN-B provider-tunnel ingress-replication create-new-ucast-tunnel

    user@host# set routing-instances VPN-B provider-tunnel ingress-replication label-switched-path label-switched-path-template default-template
12. Use show mvpn instance command to verify tunnel is inclusive:
    user@host# run show mypn instance VPN-B

    MVPN 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 : VPN-A
      MVPN Mode : SPT-ONLY
      Provider tunnel: I-P-tnl:INGRESS-REPLICATION:MPLS Label 18:10.255.245.6
      Neighbor               I-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
      C-mcast IPv4 (S:G)     Ptnl                           St
      192.168.195.145/32:232.1.1.1/32 INGRESS-REPLICATION:MPLS Label 18:10.255.245.6         RM