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.
Requirements
Before you begin, configure BGP autodiscovery for LDP VPLS. See Example: Configuring BGP Autodiscovery for LDP VPLS.
Overview
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 Group
Configuration
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.
Step-by-Step Procedure
To configure a mesh group:
Set the routing instance type to VPLS.
[edit]user@PE1# set routing-instances red instance-type vplsConfigure the route distinguisher for the routing instance.
This route distinguisher is used for the default mesh group.
[edit]user@PE1# set routing-instances red route-distinguisher 10.10.10.2:3Set the Layer 2 VPN ID for the default mesh group.
user@PE1# set routing-instances red l2vpn-id l2vpn-id:100:3Set the import and export route target for the default mesh group.
user@PE1# set routing-instances red vrf-target target:100:3Set the route distinguisher for the user-defined mesh group.
user@PE1# set routing-instances red protocols vpls mesh-group regional-1 route-distinguisher 10.10.10.2:33Set the import and export route target for the user-defined mesh group.
user@PE1# set routing-instances red protocols vpls mesh-group regional-1 vrf-target target:100:33If you are done configuring the device, commit the configuration.
[edit]user@PE1# commit
Results
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.
Verification
To verify the operation, run the following commands:
- show route extensive
- show route advertising-protocol bgp neighbor
- show route receive-protocol bgp neighbor
- show route table bgp.l2vpn.0
- show route table red.l2vpn.0
- show vpls connections extensive
- show vpls mac-table detail
- show vpls statistics
AD in the routing table output indicates autodiscovery NLRI.
