Help us improve your experience.

Let us know what you think.

Do you have time for a two-minute survey?


Example: Configuring BGP Autodiscovery for LDP VPLS with User-Defined Mesh Groups

This example describes how to configure user-defined mesh groups for BGP autodiscovery for LDP VPLS, as specified in forwarding equivalency class (FEC) 129. FEC 129 uses BGP autodiscovery to convey endpoint information, so you do not need to manually configure pseudowires. You configure mesh groups on the border router to group the sets of PE routers that are automatically fully meshed and that share the same signaling protocol, either BGP or LDP. You can configure multiple mesh groups to map each fully meshed LDP-signaled or BGP-signaled VPLS domain to a mesh group.


Before you begin, configure BGP autodiscovery for LDP VPLS. See Example: Configuring BGP Autodiscovery for LDP VPLS.

The hardware and software requirements for this example are the same as the requirements for the Example: Configuring BGP Autodiscovery for LDP VPLS. You will need to adapt the example configuration to the topology used in this example.


Configuration for a mesh group for FEC 129 is very similiar to the mesh-group configuration for FEC 128.

Note the following differences for FEC 129:

  • Each user-defined mesh group must have a unique route distinguisher. Do not use the route distinguisher that is defined for the default mesh group at the [edit routing-intances] hierarchy level.

  • Each user-defined mesh group must have its own import and export route target.

  • Each user-defined mesh group can have a unique Layer 2 VPN ID. By default, all the mesh groups that are configured for a VPLS routing instance use the same Layer 2 VPN ID as the one that you configure at the [edit routing-instances] hierarchy level.

Topology Diagram

Figure 1 shows a topology that includes a user-defined mesh group.

Figure 1: BGP Autodiscovery for LDP VPLS with a User-Defined Mesh GroupBGP Autodiscovery for LDP VPLS with a User-Defined Mesh Group


CLI Quick Configuration

To quickly configure a mesh group, copy the following commands, remove any line breaks, and then paste the commands into the CLI of each device.

Device CE1

Device CE3

Device CE4

Device R2

Device R3

Device R4


Step-by-Step Procedure

To configure a mesh group:

  1. Configure the interfaces.

  2. Configure MPLS on the interfaces.

  3. Configure BGP.

  4. Set the import and export route target for the default mesh group.

  5. Configure LDP on the core-facing interfaces and on the loopback interface.

  6. Configure the VPLS routing instance.

    Make sure that the route distinguisher in the mesh group is unique.

  7. Configure the autonomous system (AS) number.

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


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


Confirm that the configuration is working properly.

Verifying the Routes


Verify that the expected routes are learned.


From operational mode, enter the show route command.


The output shows all the learned routes, including the autodiscovered (AD) routes.

Checking Connectivity


Verify that Device CE1 can ping Device CE2 and Device CE3.



The output shows that VPLS is operational.

Checking the VPLS Connections


Make sure that all of the FEC 129 VPLS connections come up correctly.



As expected, the connections are up.

Display Learned VPLS MAC Address Information


Verify that all CE devices’ MAC addresses are learned and installed.