Related Documentation
Example: Configuring LDP-Based H-VPLS Using a Single Mesh Group to Terminate the Layer 2 Circuits
This example shows how to configure a single mesh group to terminate the Layer 2 circuits into an LDP-based VPLS. This is one type of hierarchical virtual private LAN service (H-VPLS) configuration possible in the Juniper Networks implementation. For information about the alternate type of configuration see Example: Configuring BGP-Based H-VPLS Using Different Mesh Groups for Each Spoke Router.
This example provides step-by-step configuration instructions and also provides steps for verifying and troubleshooting the configuration.
This example is organized into the following sections:
Requirements
This example uses the following hardware components:
- Four MX Series 3D Universal Edge Routers for Routers PE1, PE2, PE3, and PE4
- Two M Series Multiservice Edge Routers for Routers CE4 and PE5
- Two EX Series Ethernet Switches for Devices CE1 and CE2
- Two T Series Core Routers for Routers P1 and the route reflector
- One J Series Services Router for Router CE3
Overview and Topology
Figure 1 shows the physical topology used in this example.
Figure 1: Physical Topology of H-VPLS using a Single Mesh Group
In Figure 1:
- Local switching is used to switch traffic between Layer 2 circuit pseudowires from the different spoke PE routers.
- The spoke PE routers are configured with the same virtual circuit ID and VPLS ID pair in a mesh group.
- The spoke PE routers are configured in an LDP-signaled VPLS routing instance.
- The layer 2 circuits are terminated into the LDP-based VPLS.
Configuration
To configure a single mesh group to terminate the Layer 2 circuits into an LDP-based VPLS, perform the following tasks:
Configuring the Spoke PE Routers
Step-by-Step Procedure
Configure a single mesh group to terminate all the Layer 2 circuit pseudowires and enable local switching between the pseudowires.
- On Router PE1, configure the Layer 2 circuit by including
the l2circuit statement at the [edit protocols] hierarchy level. Include the neighbor statement and specify
the IPv4 address of the hub PE router. Also configure the logical
interface by including the interface statement and specify
the interface connected to Router CE1.
Configure the virtual circuit ID by including the virtual-circuit-id statement and specifying 100 as the ID value at the [edit protocols l2circuit neighbor 5.5.5.5 interface ge-1/0/0.0] hierarchy level.
Configure the backup neighbor by including the backup-neighbor statement and specifying the IPv4 address of the backup hub PE router. Router PE3 is the backup neighbor in this example. Also include the standby statement at the [edit protocols l2circuit neighbor 5.5.5.5 interface ge-1/0/0.0 backup-neighbor 3.3.3.3] hierarchy level.
[edit protocols]l2circuit {neighbor 5.5.5.5 {interface ge-1/0/0.0 {virtual-circuit-id 100;backup-neighbor 3.3.3.3 {standby;}}}} - On Router PE2, configure the Layer 2 circuit by including
the l2circuit statement at the [edit protocols] hierarchy level. Include the neighbor statement and specify
the IPv4 address of the hub PE router. Configure the logical interface
by including the interface statement and specifying the
interface connected to Router CE2.
Configure the virtual circuit ID by including the virtual-circuit-id statement and specifying 100 as the ID value at the [edit protocols l2circuit neighbor 5.5.5.5 interface ge-1/0/2.0] hierarchy level. Include the encapsulation statement and specify ethernet as the type.
Configure the backup neighbor by including the backup-neighbor statement and specifying the IPv4 address of the backup hub PE router. Router PE3 is the backup neighbor in this example. Also include the standby statement at the [edit protocols l2circuit neighbor 5.5.5.5 interface ge-1/0/0.0 backup-neighbor 3.3.3.3] hierarchy level.
[edit protocols]l2circuit {neighbor 5.5.5.5 {interface ge-1/0/2.0 {virtual-circuit-id 100;encapsulation-type ethernet;backup-neighbor 3.3.3.3 {standby;}}}} - On Router PE4, configure the Layer 2 circuit by including
the l2circuit statement at the [edit protocols] hierarchy level. Include the neighbor statement and specify
the IPv4 address of the hub PE router. Configure the logical interface
by including the interface statement and specify the interface
connected to Router CE4.
Configure the virtual circuit ID by including the virtual-circuit-id statement and specifying 100 as the ID value at the [edit protocols l2circuit neighbor 5.5.5.5 interface ge-1/2/0.0] hierarchy level.
Configure the backup neighbor by including the backup-neighbor statement and specifying the IPv4 address of the backup hub PE router. Router PE3 is the backup neighbor in this example. Also include the standby statement at the [edit protocols l2circuit neighbor 5.5.5.5 interface ge-1/2/0.0 backup-neighbor 3.3.3.3] hierarchy level.
[edit protocols]l2circuit {neighbor 5.5.5.5 {interface ge-1/2/0.0 {virtual-circuit-id 100;backup-neighbor 3.3.3.3 {standby;}}}}
Configuring the Hub PE Router
Step-by-Step Procedure
Configure a single mesh group to terminate all the Layer 2 circuit pseudowires and enable local switching between the pseudowires.
- On Router PE3, configure the Gigabit Ethernet interface
connected to Router CE3 by including the encapsulation statement
and specifying the ethernet-vpls option. Also configure
the logical interface by including the family statement
and specifying the vpls option.[edit interfaces]ge-1/0/1 {encapsulation ethernet-vpls;unit 0 {family vpls;}}
- On Router PE3, configure the logical loopback interface
by including the family statement and specifying the inet option. Include the address statement and specify
the IPv4 address for the interface.[edit interfaces]lo0 {unit 0 {family inet {address 3.3.3.3/32;}}}
- On Router PE3, configure the LDP-based VPLS routing instance
by including the instance-type statement at the [edit routing-instances H-VPLS] hierarchy level and specifying the vpls option. Include the interface statement and
specify the Gigabit Ethernet interface connected to Router CE3.
Configure the VPLS protocol by including the vpls statement at the [edit routing-instances H-VPLS protocols] hierarchy level. Include the no-tunnel-services statement to enable the router to use an LSI interface.
[edit routing-instances]H-VPLS {instance-type vpls;interface ge-1/0/1.0;protocols {vpls {no-tunnel-services;}}} - On Router PE3, configure the mesh group by including the mesh-group statement at the [edit routing-instances H-VPLS protocols vpls] hierarchy level and specifying L2-Circuits as the name of the group. Include the vpls-id statement
and specify 100 as the ID value. Include the local-switching statement to enable the router to switch traffic between the pseudowires.
For each neighbor in the mesh group, include the neighbor statement and specify the IPv4 address of the spoke PE router.
[edit routing-instances H-VPLS protocols vpls]mesh-group L2-Circuits {vpls-id 100; <<< Same VPLS ID on all MTUslocal-switching; << Local-switching enabledneighbor 1.1.1.1; <<MTU IP addressesneighbor 2.2.2.2;neighbor 4.4.4.4;}
Verification
Step-by-Step Procedure
- On Router PE5, use the show ldp neighbor command
to verify that LDP sessions have been created to each of the spoke
PE routers.
user@PE5# show ldp neighborAddress Interface Label space ID Hold time 1.1.1.1 lo0.0 1.1.1.1:0 33 2.2.2.2 lo0.0 2.2.2.2:0 37 4.4.4.4 lo0.0 4.4.4.4:0 39
- On Router PE5, use the show vpls connections extensive command to verify that the mesh group neighbor session is Up, that inbound and outbound labels have been assigned, that the VPLS
ID is correct, and that the virtual tunnel interface is being used.
user@PE5# show vpls connections extensive... Instance: H-VPLS Number of local interfaces: 1 Number of local interfaces up: 1 Number of VE mesh-groups: 2 Number of VE mesh-groups up: 1 ge-2/0/0.0 Mesh-group interfaces: L2-Circuits State: Up ID: 2 vt-2/1/0.1048848 Intf - vpls H-VPLS neighbor 4.4.4.4 vpls-id 100 vt-2/1/0.1048849 Intf - vpls H-VPLS neighbor 2.2.2.2 vpls-id 100 vt-2/1/0.1048850 Intf - vpls H-VPLS neighbor 1.1.1.1 vpls-id 100 Mesh-group interfaces: __ves__ State: Dn ID: 0 Mesh-group connections: L2-Circuits Neighbor Type St Time last up # Up trans 4.4.4.4(vpls-id 100) rmt Up Jan 3 16:46:26 2010 1 Remote PE: 4.4.4.4, Negotiated control-word: No Incoming label: 800011, Outgoing label: 301088 Local interface: vt-2/1/0.1048848, Status: Up, Encapsulation: ETHERNET Description: Intf - vpls H-VPLS neighbor 4.4.4.4 vpls-id 100 Connection History: Jan 3 16:46:26 2010 status update timer Jan 3 16:46:26 2010 PE route changed Jan 3 16:46:26 2010 In lbl Update 800011 Jan 3 16:46:26 2010 Out lbl Update 301088 Jan 3 16:46:26 2010 In lbl Update 800011 Jan 3 16:46:26 2010 loc intf up vt-2/1/0.1048848 2.2.2.2(vpls-id 100) rmt Up Jan 3 16:46:26 2010 1 Remote PE: 2.2.2.2, Negotiated control-word: No Incoming label: 800010, Outgoing label: 301488 Local interface: vt-2/1/0.1048849, Status: Up, Encapsulation: ETHERNET Description: Intf - vpls H-VPLS neighbor 2.2.2.2 vpls-id 100 Connection History: Jan 3 16:46:26 2010 status update timer Jan 3 16:46:26 2010 PE route changed Jan 3 16:46:26 2010 In lbl Update 800010 Jan 3 16:46:26 2010 Out lbl Update 301488 Jan 3 16:46:26 2010 In lbl Update 800010 Jan 3 16:46:26 2010 loc intf up vt-2/1/0.1048849 1.1.1.1(vpls-id 100) rmt Up Jan 3 16:46:26 2010 1 Remote PE: 1.1.1.1, Negotiated control-word: No Incoming label: 800009, Outgoing label: 301296 Local interface: vt-2/1/0.1048850, Status: Up, Encapsulation: ETHERNET Description: Intf - vpls H-VPLS neighbor 1.1.1.1 vpls-id 100 Connection History: Jan 3 16:46:26 2010 status update timer Jan 3 16:46:26 2010 PE route changed Jan 3 16:46:26 2010 In lbl Update 800009 Jan 3 16:46:26 2010 Out lbl Update 301296 Jan 3 16:46:26 2010 In lbl Update 800009 Jan 3 16:46:26 2010 loc intf up vt-2/1/0.1048850
