Example: Allowing MBGP MVPN Remote Sources

This example shows how to configure an MBGP MVPN that allows remote sources, even when there is no PIM neighborship towards the upstream router.

• Requirements
• Overview
• Configuration
• Verification

Requirements

Before you begin:

• Configure the router interfaces. See the Network Interfaces Configuration Guide.
• Configure an interior gateway protocol or static routing. See the Routing Protocols Configuration Guide.
• 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 point-to-multipoint LSP (flood next hop).

This example shows the configuration on the ingress PE router.

Figure 49 shows the topology used in this example.

Configuration

CLI Quick Configuration

To quickly allow remote sources, copy the following commands and paste them into the CLI of the ingress PE router.

Step-by-Step Procedure

To allow remote sources:

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

   [edit]user@host# edit routing-instances vpn-A[edit routing-instances vpn-A]user@host# set instance-type vrf [edit routing-instances vpn-A]user@host# set interface ge-1/0/0.213[edit routing-instances vpn-A]user@host# set interface ge-6/0/0 [edit routing-instances vpn-A]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[edit routing-instances vpn-A]user@host# set vrf-target target:65000:04

4. Configure the provider tunnel.

   [edit routing-instances vpn-A]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[edit routing-instances vpn-A]user@host# set protocols bgp group 1a peer-as 65213[edit routing-instances vpn-A]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 [edit routing-instances vpn-A]user@host# set protocols pim interface ge-1/0/0.213 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.

   [edit routing-instances vpn-A]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 configuration instructions in this example to correct it.

Verification

To verify the configuration, run the following commands:

• 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

Related Topics

• Example: Configuring a PIM-SSM Provider Tunnel for an MBGP MVPN
• Configuring the Interface to Accept Traffic from a Remote Source