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.

English  

English

Example: Allowing MBGP MVPN Remote Sources

Requirements

Before you begin:

• Configure the router interfaces. See the Junos OS Network Interfaces Library for Routing Devices.
• Configure an interior gateway protocol or static routing. See the Junos OS Routing Protocols Library for Routing Devices.
• Configure the point-to-multipoint static LSP. See Configuring Point-to-Multipoint LSPs for an MBGP MVPN.

Overview

In this example, a remote CE router is the multicast source. In an MBGP MVPN, a PE router has the PIM interface hello interval set to zero, thereby creating no PIM neighborship. The PIM upstream state is None. In this scenario, directly connected receivers receive traffic in the MBGP MVPN only if you configure the ingress PE’s upstream logical interface to accept remote sources. If you do not configure the ingress PE’s logical interface to accept remote sources, the multicast route is deleted and the local receivers are no longer attached to the flood next hop.

This example shows the configuration on the ingress PE router. A static LSP is used to receive traffic from the remote source.

Figure 1 shows the topology used in this example.

Figure 1: MBGP MVPN Remote Source

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

1. On the ingress PE router, configure the interfaces in the routing instance.

   [edit routing-instances vpn-A]user@host# set instance-type vrf user@host# set interface ge-1/0/0.213 user@host# set interface ge-1/0/0.484 user@host# set interface ge-1/0/1.200 user@host# set interface ge-1/0/2.0 user@host# set interface ge-1/0/7.0 user@host# set interface vt-1/1/0.0

2. Configure the autonomous system number in the global routing options. This is required in MBGP MVPNs.

   user@host# set routing-options autonomous-system 100

3. Configure the route distinguisher and the VRF target.

   [edit routing-instances vpn-A]user@host# set route-distinguisher 10.0.0.10:04 user@host# set vrf-target target:65000:04

4. Configure the provider tunnel.

   [edit routing-instances vpn-A]user@host# set provider-tunnel rsvp-te label-switched-path-template mvpn-dynamic user@host# set provider-tunnel selective group 224.0.9.0/32 source 10.1.1.2/32 rsvp-te static-lsp mvpn-static

5. Configure BGP in the routing instance.

   [edit routing-instances vpn-A]user@host# set protocols bgp group 1a type external user@host# set protocols bgp group 1a peer-as 65213 user@host# set protocols bgp group 1a neighbor 10.2.213.9

6. Configure PIM in the routing instance, including the accept-remote-source statement on the incoming logical interface.

   [edit routing-instances vpn-A]user@host# set protocols pim interface all hello-interval 0 user@host# set protocols pim interface ge-1/0/2.0 accept-remote-source

7. Enable the MVPN Protocol in the routing instance.

   [edit routing-instances vpn-A]user@host# set protocols mvpn

8. If you are done configuring the devices, commit the configuration.

   user@host# commit

Results

From configuration mode, confirm your configuration by entering the show routing-instances and show routing-options commands. If the output does not display the intended configuration, repeat the instructions in this example to correct the configuration.

Verification

• show mpls lsp p2mp
• show multicast route instance vpn-A extensive
• show mvpn c-multicast
• show pim join instance vpn-A extensive
• show route forwarding-table destination destination
• show route table vpn-A.mvpn.0