Help us improve your experience.

Let us know what you think.

Do you have time for a two-minute survey?

 
 

Example: Configuring Multipoint LDP Recursive FEC

Note:

Our content testing team has validated and updated this example.

Use this configuration example to configure and verify Multipoint Label Distribution Protocol (LDP) Recursive forwarding equivalence class (FEC) in an OSPF network. This enables to form MLDP point-to-multipoint (P2MP) tunnels between two autonomous systems (ASs) when the backbone has no direct route to the root node.

Tip:
Table 1: Readability Score and Time Estimates

Reading Time

45 minutes

Configuration Time

1 hour

Example Prerequisites

Hardware requirements

MX Series routers as CE, PE, and intermediate routers.

Software requirements

Junos OS Release 23.4R1 or later running on all devices.

Before You Begin

Benefits

The Multipoint LDP (MLDP) Recursive Forwarding Equivalence Class (FEC) is useful in a deployment in which the intermediate routers do not have the route to reach the root node.

Know more

Understanding Multipoint LDP Recursive FEC.

Functional Overview

Technologies used

  • Service Family:Layer 3 VPN

  • Protocols:BGP, IS-IS, LDP, MPLS, OSPF, PIM

  • Transport Tunnels: MLDP P2MP,

Primary verification tasks

  • Verify LDP P2MP tunnel is formed.

  • Verify the formation of LDP recursive FEC

  • Verify the recursive opaque value functionality in the ingress and transit routers.

Topology Overview

This configuration example depicts a host system capable of sending multicast traffic and a host system capable of receiving multicast traffic. It shows two autonomous systems (ASes); AS65010 that consists of PE1, P1, and ASBR1 routers and AS65020 that consists of PE2, P2, and ASBR2 routers. All routers within an AS run OSPF as the IGP. All routers belong to area 0. The customer edge (CE) devices use EBGP peering to exchange routes with their provider edge device as part of a Layer 3 VPN service. The PE devices use IBGP to exchange IPv4 routes with the remote PE.

The Provider edge (PE2) and AS border router (ASBR2) routers have route to the root PE1. However, The P (P1 and P2) routers do not have a route towards the root. The MLDP P2MP tunnel is formed from the egress (PE2) to ingress (PE1) routers to pass the FEC element through mLDP.

Hostname

Role

Function

CE1

Remote CE device.

EBGP peer to PE1 router to advertise and learn CE device loopback addresses.

PE1 (DUT)

Local PE device.

The root node that intermediate routers of another AS try to reach in a scenario where there is no direct route to PE1.

P1

Intermediate device P1.

Intermediate router that has no route to PE2 router. It receives PE1-FEC from ASBR1 and processes it as a normal LDP P2MP FEC.

ASBR1

AS border router ASBR1

EBGP peer to ASBR2 router to advertise and learn IGP routes. The ASBR1 finds the route to the root (which is an IGP route) and replaces ASBR1-FEC with the contents of the Recursive Opaque Value (PE1-FEC) before doing any further processing.

ASBR2

AS border router ASBR2

EBGP peer to ASBR1 router to advertise and learn IGP routes. Acts as root node for P2 and does a lookup to find the route to actual root (PE1). Determines the route to PE1 is a BGP route and forms a LDP Recursive FEC with ASBR1 to PE1.

P2

Intermediate device P2.

Intermediate router that has no route to PE1 router. It receives the FEC element from PE2 through mLDP. However, it cannot use the same FEC element, because it does not have route to PE1.

PE2

Local PE device.

PE2 creates an MP FEC element with the address of PE1 as the root node address to form a P2MP tunnel from PE2 to root PE1.

CE2

Remote CE device.

EBGP peering to PE2 router to advertise and learn CE device loopback addresses.

Topology Illustration

Figure 1: MLDP FEC for Inter-AS with Recursive Opaque Value in MVPN Option C scenario MLDP FEC for Inter-AS with Recursive Opaque Value in MVPN Option C scenario

PE1 Configuration Steps

This section highlights the main configuration tasks needed to configure the PE1 device for this example. The first step is common to configuring a basic Layer 3 VPN service. The following set of steps are specific to configuring recursive FEC. Both PE devices have a similar configuration, here we focus on PE1.

  1. First, provision the general Layer 3 VPN:

    1. Configure and number the loopback, core facing, and CE-facing interfaces for IPv4. Be sure to enable the mpls family on the core-facing interfaces connecting to the P devices to support MPLS switching.

    2. Configure an autonomous system number.

    3. Configure single area OSPF on the loopback and core-facing interfaces.

    4. Configure LDP, MPLS on all the interfaces.

    5. Configure the IBGP peering session to include the inet-vpn address family to support IPv4 layer 3 VPN.

    6. Configure a VRF based routing-instance for the CE1 device. Use EBGP as the PE-CE routing protocol.

  2. Configure the mode for C-PIM join messages to use rendezvous-point trees, and switch to the shortest-path tree after the source is known.

  3. Configure PIM to enable PE to CE multicast routing.

  4. Enable PIM on the interfaces connected to the CE router.

  5. Configure dynamic selective point-to-multipoint LSP and specify the data threshold required before the new tunnel is created.

  6. Configure point-to-multipoint recursive LDP FEC.

  7. Configure the routing policies.

Verification

Command Verification Task
show ldp overview Verify Recursive fec enabled in the LDP overview information.
show ldp database Verify the labels advertised point-to-multipoint binding information in the LDP database.
show ldp p2mp path Verify LDP P2MP FEC information.
show ldp p2mp fec Verify LDP P2MP LSPs.

Verify Recursive FEC in the LDP overview information.

Purpose

To confirm recursive FEC is enabled and is displayed in PE1 LDP overview information.

Action

From operational mode, enter the show ldp overview command.

Meaning

The output confirms that recursive fec is enabled on PE1.

Verify the Advertised Label

Purpose

Verify the labels advertised from ASBR1 and received by PE1.

Action

From operational mode, enter the show ldp database command.

On ASBR1

On PE1

Meaning

You can see label 3 advertised from ASBR1 and label 3 received by PE1.

Verify P2MP FEC Information

Purpose

Verify the LDP P2MP FEC information from ASBR2.

Action

From operational mode, enter the show ldp p2mp fec extensive command.

Meaning

The output shows that PE2 forms a LDP recursive FEC to find the route to actual root (PE1).

Verify P2MP Path Information

Purpose

Verify the LDP P2MP path information from PE2.

Action

From operational mode, enter the show ldp p2mp path extensive command.

Meaning

The output shows PE2 with the FEC element, in which the root node address is the address of protocol nexthop ASBR2.

Appendix 1: Set Commands on All Devices

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.

Note:

We use logical systems to represent the source and receiver for this example.

CE1

PE1

P1

ASBR1

ASBR2

P2

PE2

CE2

Appendix 2: Show Configuration Output on PE1 and ASBR2

The Complete PE1 configuration in Curly Brace Format

The Complete ASBR2 configuration in Curly Brace Format