About L2VPN access to L3VPN or IP backbone
Both MPLS L2VPN and VPLS support the L2VPNaccess to L3VPN or IP backbone feature. MPLS L2VPN provides point-to-point connections,and VPLS provides point-to-multipoint connections.
Unless otherwise specified, the term"MPLS L2VPN" in this document refers toboth MPLS L2VPN and VPLS.
Benefits of L2VPN access to L3VPN or IP backbone
An MPLS L2VPNaccess network has the following features:
·Transparency—MPLS L2VPN is transparent to users and can be regarded as aphysical link that directly connects users to the backbone.
·Cost reduction—MPLS L2VPN only requires PEs to identify users and user services,and P devices only forward packets based on labels. Therefore, you can uselow-end devices as P devices to reduce your investment.
·Flexible networking—MPLS L2VPN supports various user access modes, such as Ethernet,ATM, and frame relay. It allows links that run different link layer protocolsto communicate with each other through interworking.
Implementation modes of L2VPN access toL3VPN or IP backbone
L2VPN access to L3VPN or IP backbone can beimplemented in two modes: conventional and improved.
Conventional L2VPNaccess to L3VPN or IP backbone
In the conventional networking mode, two devices are required toconnect the MPLS L2VPN and the MPLS L3VPN or IP backbone. One device terminatesthe MPLS L2VPN, and the other device provides access to the MPLS L3VPN or IPbackbone.
As shown in Figure 1, the access network isan MPLS L2VPN. PE 1 and PE 2 are PE devices in the MPLS L2VPN. PE 1 isconnected to VPN site 1. PE 2 is connected to the MPLS L3VPN/IP backbonethrough PE 3. PE 3 acts as a PE in the MPLS L3VPN/IP backbone and as a CE inthe MPLS L2VPN at the same time.
A packet from VPN site 1 to VPN site 2 isforwarded as follows:
1.A user in VPN site 1 sends a packet to PE 1.
2.PE 1 adds an MPLS label to the packet andsends the packet through a PW to PE 2.
3.PE 2 removes the MPLS label from the packetto obtain the original Layer 2 packet, and sends the packet to the connected CE(PE 3).
4.PE 3 looks up the routing table, andforwards the packet to the destination through the MPLS L3VPN or IP backbone.
Improved L2VPN access to L3VPN or IPbackbone
As shown in Figure 2, thePE Aggregation (PE-agg) device connects the MPLS L2VPN with the MPLS L3VPN orIP backbone. PE-agg terminates the MPLS L2VPN and provides access to the MPLSL3VPN or IP backbone.
Configure the PE-agg as follows so thePE-agg can implement the functions of both PE 2 and PE 3 in Figure 1:
1.Create a terminating virtual Ethernet (VE)interface on the PE-agg to terminate MPLS L2VPN packets.
This interface is referred to as the VE-L2VPN(L2VE) interface. The functions and configurations of the interface are similarto those of the terminating interface (Terminating int) in Figure 1.
2.Create an access VE interface on the PE-aggto provide access to the backbone, and configure the interface and the L2VEinterface have the same interface number.
This interface is referred to as theVE-L3VPN (L3VE) interface. The functions and configurations of the interfaceare similar to those of the access interface (Access int) in Figure 1. The IPaddress of the L3VE interface must be in the same network segment as the ACinterface of CE 1. When the backbone is an MPLS L3VPN, bind the VPN instance tothe L3VE interface. The interface can then forward user packets through the VPNroutes.
The L2VE interface directly delivers theobtained Layer 2 packets to the L3VE interface. The two VE interfaces can beconsidered directly connected through a physical link.
The PE-agg connects the MPLS L2VPN and thebackbone through the L2VE interface and the L3VE interface. You can assume thatthe MPLS L2VPN is connected to the backbone through an Ethernet or VLAN link.If a user is not connected to the MPLS L2VPN through Ethernet or VLAN, you mustconfigure MPLS L2VPN interworking on the user access PE (PE 1) and the L2VEinterface of the PE-agg.
Restrictions: Hardware compatibility with L2VPN access to L3VPN orIP backbone
| Hardware | Feature compatibility |
| MSR810, MSR810-W, MSR810-W-DB, MSR810-LM, MSR810-W-LM, MSR810-10-PoE, MSR810-LM-HK, MSR810-W-LM-HK, MSR810-LM-CNDE-SJK, MSR810-CNDE-SJK | Yes |
| MSR810-LMS, MSR810-LUS | No |
| MSR810-LMS-EA, MSR810-LME | Yes |
| MSR2600-6-X1, MSR2600-10-X1 | Yes |
| MSR 2630 | Yes |
| MSR3600-28, MSR3600-51 | Yes |
| MSR3600-28-SI, MSR3600-51-SI | No |
| MSR3600-28-X1, MSR3600-28-X1-DP, MSR3600-51-X1, MSR3600-51-X1-DP | Yes |
| MSR3610-I-DP, MSR3610-IE-DP, MSR3610-IE-ES, MSR3610-IE-EAD, MSR3610-I-IG, MSR3610-IE-IG | Yes |
| MSR3610-X1, MSR3610-X1-DP, MSR3610-X1-DC, MSR3610-X1-DP-DC | Yes |
| MSR 3610, MSR 3620, MSR 3620-DP, MSR 3640, MSR 3660 | Yes |
| MSR3610-G, MSR3620-G | Yes |
| Hardware | Feature compatibility |
| MSR810-W-WiNet, MSR810-LM-WiNet | Yes |
| MSR830-4LM-WiNet | Yes |
| MSR830-5BEI-WiNet, MSR830-6EI-WiNet, MSR830-10BEI-WiNet | Yes |
| MSR830-6BHI-WiNet, MSR830-10BHI-WiNet | Yes |
| MSR2600-6-WiNet, MSR2600-10-X1-WiNet | Yes |
| MSR2630-WiNet | Yes |
| MSR3600-28-WiNet | Yes |
| MSR3610-X1-WiNet | Yes |
| MSR3610-WiNet, MSR3620-10-WiNet, MSR3620-DP-WiNet, MSR3620-WiNet, MSR3660-WiNet | Yes |
| Hardware | Feature compatibility |
| MSR2630-XS | Yes |
| MSR3600-28-XS | Yes |
| MSR3610-XS | Yes |
| MSR3620-XS | Yes |
| MSR3610-I-XS | Yes |
| MSR3610-IE-XS | Yes |
| Hardware | Feature compatibility |
| MSR810-LM-GL | Yes |
| MSR810-W-LM-GL | Yes |
| MSR830-6EI-GL | Yes |
| MSR830-10EI-GL | Yes |
| MSR830-6HI-GL | Yes |
| MSR830-10HI-GL | Yes |
| MSR2600-6-X1-GL | Yes |
| MSR3600-28-SI-GL | No |
Configuring conventional L2VPN access to L3VPN or IP backbone
As shown in Figure 1, perform the following tasksto configure conventional L2VPN access to L3VPN or IP backbone:
1.Configure the MPLS L2VPN:
¡ConfigurePE 1 and PE 2 as PE devices in the MPLS L2VPN.
¡ConfigureCE 1 and PE 3 as CE devices in the MPLS L2VPN.
For more information about MPLS L2VPNconfiguration, see "Configuring MPLS L2VPN" and "ConfiguringVPLS."
2.Configure the MPLS L3VPN or IP backbone:
¡ConfigurePE 3 and PE 4 as PE devices in the MPLS L3VPN or IP backbone.
¡ConfigureCE 1 and CE 2 as CE devices in the MPLS L3VPN or IP backbone.
For more information about MPLS L3VPNconfiguration, see "Configuring MPLS L3VPN."
Configuring improved L2VPN access toL3VPN or IP backbone
Restrictions andguidelines
The L2VE interface and L3VE interface createdon the PE-agg must have the same interface number.
Procedure
Configurations required on PEs and CEs aresimilar to those on the devices in the conventional L2VPN access scenario. ThePE-agg requires the following configurations:
1.Create an L2VE interface:
a.Enter system view.
system-view
b.Create an L2VE interface and enter its view.
interface ve-l2vpn interface-number
c.Bring up the interface.
undo shutdown
By default, the interface is up.
2.Create an L3VE interface:
a.Enter system view.
system-view
b.Create an L3VE interface and enter its view.
interface ve-l3vpn interface-number
c.Bring up the interface.
undo shutdown
By default, the interface is up.
3.Configure MPLS L2VPN.
For more information, see "ConfiguringMPLS L2VPN" and "Configuring VPLS."
4.Configure MPLS L3VPN or IP routes.
For more information about MPLS L3VPNconfiguration, see "Configuring MPLS L3VPN."
Configuring an L2VE or L3VE interface
Configuring an L2VE interface
1.Enter system view.
system-view
2.Enter L2VE interface view.
interface ve-l2vpn interface-number
3.Configure the description of the interface.
description text
By default, the description of the interfaceis VE-L2VPNnumber Interface, for example, VE-L2VPN100 Interface.
4.Set the MTU for the interface.
mtu size
The default MTU of an interface is 1500bytes.
5.Set the expected bandwidth for theinterface.
bandwidth bandwidth-value
By default, the expected bandwidth of aninterface is 100000 kbps.
Configuringan L3VE interface
1.Enter system view.
system-view
2.Enter L3VE interface view.
interface ve-l3vpn interface-number
3.Configure the description of the interface.
description text
By default, the description of the interfaceis VE-L3VPNnumber Interface, forexample, VE-L3VPN100 Interface.
4.Set the MTU for the interface.
mtu size
The default MTU of an interface is 1500bytes.
5.Set the expected bandwidth for theinterface.
bandwidth bandwidth-value
By default, the expected bandwidth of aninterface is 100000 kbps.
Restoring the default settings for an interface
Restrictions andguidelines
Restoring the default settings for aninterface might interrupt ongoing network services. Make sure you are fullyaware of the impact of the default command whenyou use it on a live network.
Procedure
1.Enter system view.
system-view
2.Enter L2VE interface view or L3VE interfaceview.
interface interface-type interface-number
3.Restore the default settings for theinterface.
default
Displayand maintenance commands for L2VPN access to L3VPN or IP backbone
Execute displaycommands in any view and reset commands in userview.
| Task | Command |
| Display information about L2VE interfaces interfaces. | display interface [ ve-l2vpn [ interface-number ] ] [ brief [ description | down ] ] |
| Display information about L3VE interfaces interfaces. | display interface [ ve-l3vpn [ interface-number ] ] [ brief [ description | down ] ] |
| Clear L2VE interface statistics. | reset counters interface [ ve-l2vpn [ interface-number ] ] |
| Clear L3VE interface statistics. | reset counters interface [ ve-l3vpn [ interface-number ] ] |
Improved L2VPN access to L3VPN or IP backbone configuration examples (on routers)
Example: Configuring access to MPLS L3VPNthrough an LDP MPLS L2VPN
The MPLS L2VPN in this configurationexample is a point-to-point MPLS L2VPN that provides PPP-to-Ethernetinterworking.
Network configuration
The backbone is an MPLS L3VPN, whichadvertises VPN routes through BGP and forwards VPN packets based on MPLSlabels.
CE 1 and CE 2 belong to VPN 1 whose route targetis 111:1 and RD is 200:1. CE 1 is connected to PE 1 through interface Serial2/1/0, which uses PPP encapsulation. CE 2 is connected to the MPLS L3VPNthrough interface GigabitEthernet 1/0/1.
Perform the following configurations toallow communication between CE 1 and CE 2:
·Set up an LDP PW between PE 1 and PE-agg, sothat CE 1 can access the MPLS L3VPN through MPLS L2VPN.
·Configure MPLS L2VPN interworking on interfaceSerial 2/1/0 of PE 1 and the L2VE interface of PE-agg.
This configuration is required because CE1 is connected to the MPLS L2VPN through PPP, not Ethernet or VLAN.
·Run EBGP between CE 1 and PE-agg and between CE2 and PE 2 to exchange VPN routing information.
·Run MP-IBGP between PE-agg and PE 2 to exchangeVPN routing information.
·Run IS-IS between PE-agg and PE 2 to ensure IPconnectivity within the backbone.
·Run OSPF among PE 1, P, and PE-agg to ensure IPconnectivity between the PEs.
Figure 3 Network diagram
Table 1 Interface and IP address assignment
| Interface | IP address | Device | Interface | IP address | |
| CE 1 | Ser2/1/0 | 100.1.1.1/24 | PE-agg | Loop0 | 3.3.3.9/32 |
| PE 1 | Loop0 | 1.1.1.9/32 | POS2/2/0 | 10.2.2.2/24 | |
| POS2/2/0 | 10.2.1.1/24 | POS2/2/1 | 10.3.3.1/24 | ||
| P | Loop0 | 2.2.2.9/32 | VE-L3VPN1 | 100.1.1.2/24 | |
| POS2/2/0 | 10.2.1.2/24 | PE 2 | Loop0 | 4.4.4.9/32 | |
| POS2/2/1 | 10.2.2.1/24 | POS2/2/0 | 10.3.3.2/24 | ||
| CE 2 | GE1/0/1 | 100.2.1.2/24 | GE1/0/1 | 100.2.1.1/24 |
Procedure
1.Configure IP addresses for interfaces asshown in Table 1. (Details not shown.)
2.Create VE-L2VPN 1 and VE-L3VPN 1 on PE-agg:
# Create VE-L2VPN 1.
<PEagg> system-view
[PEagg] interface ve-l2vpn 1
[PEagg-VE-L2VPN1] quit
# Create VE-L3VPN 1.
[PEagg] interface ve-l3vpn 1
[PEagg-VE-L3VPN1] quit
3.Configure MPLS L2VPN:
a.Configure OSPF on PE 1, P, and PE-agg, andadvertise interface addresses:
# Configure PE 1.
<PE1> system-view
[PE1] ospf
[PE1-ospf-1] area 0
[PE1-ospf-1-area-0.0.0.0]network 1.1.1.9 0.0.0.0
[PE1-ospf-1-area-0.0.0.0]network 10.2.1.0 0.0.0.255
[PE1-ospf-1-area-0.0.0.0] quit
[PE1-ospf-1] quit
# Configure the P device.
<P> system-view
[P] ospf
[P-ospf-1] area 0
[P-ospf-1-area-0.0.0.0]network 2.2.2.9 0.0.0.0
[P-ospf-1-area-0.0.0.0]network 10.2.2.0 0.0.0.255
[P-ospf-1-area-0.0.0.0] network10.2.1.0 0.0.0.255
[P-ospf-1-area-0.0.0.0] quit
[P-ospf-1] quit
# Configure PE-agg.
[PEagg] ospf
[PEagg-ospf-1] area 0
[PEagg-ospf-1-area-0.0.0.0]network 3.3.3.9 0.0.0.0
[PEagg-ospf-1-area-0.0.0.0]network 10.2.2.0 0.0.0.255
[PEagg-ospf-1-area-0.0.0.0]quit
[PEagg-ospf-1] quit
b.Configure basic MPLS and MPLS LDP on PE 1,P, and PE-agg:
# Configure PE 1.
[PE1] mpls lsr-id 1.1.1.9
[PE1] mpls ldp
[PE1-ldp] lsp-trigger all
[PE1-ldp] quit
[PE1] interface pos 2/2/0
[PE1-Pos2/2/0] mpls enable
[PE1-Pos2/2/0] mpls ldp enable
[PE1-Pos2/2/0] quit
# Configure the P device.
[P] mpls lsr-id 2.2.2.9
[P] mpls ldp
[P-ldp] lsp-trigger all
[P-ldp] quit
[P] interface pos 2/2/0
[P-Pos2/2/0] mpls enable
[P-Pos2/2/0] mpls ldp enable
[P-Pos2/2/0] quit
[P] interface pos 2/2/1
[P-Pos2/2/1] mpls enable
[P-Pos2/2/1] mpls ldp enable
[P-Pos2/2/1] quit
# Configure PE-agg.
[PEagg] mpls lsr-id 3.3.3.9
[PEagg] mpls ldp
[PEagg-ldp] lsp-trigger all
[PEagg-ldp] quit
[PEagg] interface pos 2/2/0
[PEagg-Pos2/2/0] mpls enable
[PEagg-Pos2/2/0] mpls ldpenable
[PEagg-Pos2/2/0] quit
c.Enable L2VPN on PE 1 and PE-agg:
# Configure PE 1.
[PE1] l2vpn enable
# Configure PE-agg.
[PEagg] l2vpn enable
d.Configure the AC interfaces of PE 1 andPE-agg, create PWs that support interworking, and bind the interface to the PWs:
# On Serial 2/1/0 of PE 1, configure PPPto support IPCP negotiation without IP address.
[PE1] interface serial 2/1/0
[PE1-Serial2/1/0]link-protocol ppp
[PE1-Serial2/1/0] ppp ipcpignore local-ip
[PE1-Serial2/1/0] quit
# On PE 1, create a PW that supportsinterworking in the group, and bind Serial 2/1/0 to the PW.
[PE1] xconnect-group 1
[PE1-xcg-1] connection 1
[PE1-xcg-1-1] ac interfaceserial 2/1/0
[PE1-xcg-1-1] interworkingipv4
[PE1-xcg-1-1] peer 3.3.3.9pw-id 101
[PE1-xcg-1-1-3.3.3.9-101] quit
# On the L2VE interface of PE-agg,specify the default next hop as 100.1.1.2.
[PEagg] interface ve-l2vpn 1
[PEagg-VE-L2VPN1] default-nexthopip 100.1.1.2
[PEagg-VE-L2VPN1] quit
# On PE-agg, create a PW that supportsinterworking in the group, and bind VE-L2VPN 1 to the PW.
[PEagg] xconnect-group 1
[PEagg-xcg-1] connection 1
[PEagg-xcg-1-1] ac interface ve-l2vpn1
[PEagg-xcg-1-1] interworkingipv4
[PEagg-xcg-1-1] peer 1.1.1.9pw-id 101
[PEagg-xcg-1-1-1.1.1.9-101] quit
e.Configure the AC interface of CE 1 (Serial 2/1/0).
<CE1> system-view
[CE1] interface serial 2/1/0
[CE1-Serial2/1/0]link-protocol ppp
[CE1-Serial2/1/0] ip address100.1.1.1 24
4.Configure MPLS L3VPN:
a.Configure IS-IS on PE 2 and PE-agg, andadvertise interface addresses:
# Configure PE-agg.
[PEagg] isis 1
[PEagg-isis-1] network-entity 10.0000.0000.0001.00
[PEagg-isis-1] quit
[PEagg] interface pos 2/2/1
[PEagg-Pos2/2/1] isis enable 1
[PEagg-Pos2/2/1] quit
[PEagg] interface loopback 0
[PEagg-LoopBack0] isis enable1
[PEagg-LoopBack0] quit
# Configure PE 2.
[PE2] isis 1
[PE2-isis-1] network-entity10.0000.0000.0002.00
[PE2-isis-1] quit
[PE2] interface pos 2/2/0
[PE2-Pos2/2/0] isis enable 1
[PE2-Pos2/2/0] quit
[PE2] interface loopback 0
[PE2-LoopBack0] isis enable 1
[PE2-LoopBack0] quit
b.Configure basic MPLS and MPLS LDP on PE-aggand PE 2:
# Configure PE-agg.
[PEagg] interface pos 2/2/1
[PEagg-Pos2/2/1] mpls enable
[PEagg-Pos2/2/1] mpls ldpenable
[PEagg-Pos2/2/1] quit
# Configure PE 2.
[PE2] mpls lsr-id 4.4.4.9
[PE2] mpls ldp
[PE2-ldp] lsp-trigger all
[PE2-ldp] quit
[PE2] interface pos 2/2/0
[PE2-Pos2/2/0] mpls enable
[PE2-Pos2/2/0] mpls ldp enable
[PE2-Pos2/2/0] quit
c.On PE-agg and PE 2, create VPN instance VPN1, and bind the VPN instance to the interface connectedto the CE:
# Configure PE-agg.
[PEagg] ip vpn-instance VPN1
[PEagg-vpn-instance-VPN1] route-distinguisher200:1
[PEagg-vpn-instance-VPN1] vpn-target111:1 both
[PEagg-vpn-instance-VPN1] quit
[PEagg] interface ve-l3vpn 1
[PEagg-VE-L3VPN1] ip bindingvpn-instance VPN1
[PEagg-VE-L3VPN1] ip address100.1.1.2 24
# Configure PE 2.
[PE2] ip vpn-instance VPN1
[PE2-vpn-instance-VPN1] route-distinguisher200:1
[PE2-vpn-instance-VPN1] vpn-target111:1 both
[PE2-vpn-instance-VPN1] quit
[PE2] interface gigabitethernet 1/0/1
[PE2-GigabitEthernet1/0/1] ip bindingvpn-instance VPN1
[PE2-GigabitEthernet1/0/1] ip address 100.2.1.1 24
[PE2-GigabitEthernet1/0/1] quit
d.Establish EBGP peer relationships between CE1 and PE-agg, and between CE 2 and PE 2 to redistribute VPN routes:
# Configure CE 1 and specify PE-agg as thepeer.
<CE1> system-view
[CE1] bgp 65010
[CE1-bgp] peer 100.1.1.2as-number 100
[CE1-bgp] address-family ipv4
[CE1-bgp-ipv4] peer 100.1.1.2enable
[CE1-bgp-ipv4] import-routedirect
[CE1-bgp-ipv4] quit
[CE1-bgp] quit
# Configure PE-agg and specify CE 1 asthe peer.
[PEagg] bgp 100
[PEagg-bgp] ip vpn-instanceVPN1
[PEagg-bgp-VPN1] peer100.1.1.1 as-number 65010
[PEagg-bgp-VPN1]address-family ipv4
[PEagg-bgp-ipv4-VPN1] peer100.1.1.1 enable
[PEagg-bgp-ipv4-VPN1]import-route direct
[PEagg-bgp-ipv4-VPN1] quit
[PEagg-bgp-VPN1] quit
[PEagg-bgp] quit
# Configure CE 2 and specify PE 2 as thepeer.
[CE2] bgp 65020
[CE2-bgp] peer 100.2.1.1as-number 100
[CE2-bgp] address-family ipv4
[CE2-bgp-ipv4] peer 100.2.1.1enable
[CE2-bgp-ipv4] import-routedirect
[CE2-bgp-ipv4] quit
[CE2-bgp] quit
# Configure PE 2 and specify CE 2 as thepeer.
[PE2] bgp 100
[PE2-bgp] ip vpn-instance VPN1
[PE2-bgp-VPN1] peer 100.2.1.2as-number 65020
[PE2-bgp-VPN1] address-familyipv4
[PE2-bgp-ipv4-VPN1] peer 100.2.1.2enable
[PE2-bgp-ipv4-VPN1]import-route direct
[PE2-bgp-ipv4-VPN1] quit
[PE2-bgp-VPN1] quit
[PE2-bgp] quit
e.Establish an MP-IBGP peer relationshipbetween PE-agg and PE 2:
# Configure PE-agg.
[PEagg] bgp 100
[PEagg-bgp] peer 4.4.4.9as-number 100
[PEagg-bgp] peer 4.4.4.9connect-interface loopback 0
[PEagg-bgp] address-familyvpnv4
[PEagg-bgp-vpnv4] peer 4.4.4.9enable
[PEagg-bgp-vpnv4] quit
[PEagg-bgp] quit
# Configure PE 2.
[PE2] bgp 100
[PE2-bgp] peer 3.3.3.9as-number 100
[PE2-bgp] peer 3.3.3.9connect-interface loopback 0
[PE2-bgp] address-family vpnv4
[PE2-bgp-vpnv4] peer 3.3.3.9enable
[PE2-bgp-vpnv4] quit
[PE2-bgp] quit
5.The default MTU value varies by interfacetype. To avoid packet fragmentation, set the MTU value for each POS interfaceon each device to 1500 bytes. The following shows the MTU configuration on PE 1.
[PE1] interface pos 2/2/0
[PE1-Pos2/2/0] mtu 1500
[PE1-Pos2/2/0] shutdown
[PE1-Pos2/2/0] undo shutdown
Verifying theconfiguration
# Ping CE 2 from CE 1 to verify theirconnectivity.
<CE1> ping 100.2.1.2
Ping 100.2.1.2 (100.2.1.2): 56 databytes, press CTRL_C to break
56 bytes from 100.2.1.2: icmp_seq=0ttl=128 time=1.073 ms
56 bytes from 100.2.1.2: icmp_seq=1ttl=128 time=1.428 ms
56 bytes from 100.2.1.2: icmp_seq=2ttl=128 time=19.367 ms
56 bytes from 100.2.1.2: icmp_seq=3ttl=128 time=1.013 ms
56 bytes from 100.2.1.2: icmp_seq=4ttl=128 time=0.684 ms
--- Ping statistics for 100.2.1.2 ---
5 packet(s) transmitted, 5 packet(s)received, 0.0% packet loss
round-trip min/avg/max/std-dev =0.684/4.713/19.367/7.331 ms
Example: Configuring access to IPbackbone through an LDP VPLS
Network configuration
Create an LDP PW between PE 1 and PE-agg onthe VPLS access network, so that CE 1 can access the IP backbone through the PW.
Configure OSPF process 2 to advertiserouting information on the IP backbone.
Figure 4 Network diagram
Table 2 Interface and IP address assignment
| Device | Interface | IP address | Device | Interface | IP address |
| CE 1 | GE1/0/1 | 100.1.1.1/24 | PE-agg | Loop0 | 3.3.3.9/32 |
| PE 1 | Loop0 | 1.1.1.9/32 | POS2/2/0 | 10.2.2.2/24 | |
| POS2/2/0 | 10.2.1.1/24 | POS2/2/1 | 10.3.3.1/24 | ||
| P | Loop0 | 2.2.2.9/32 | VE-L3VPN1 | 100.1.1.2/24 | |
| POS2/2/0 | 10.2.1.2/24 | PE 2 | POS2/2/0 | 10.3.3.2/24 | |
| POS2/2/1 | 10.2.2.1/24 | GE1/0/1 | 100.2.1.1/24 | ||
| CE 2 | GE1/0/1 | 100.2.1.2/24 |
Procedure
1.Configure IP addresses for interfaces asshown in Table 2. (Details not shown.)
2.Create VE-L2VPN 1 and VE-L3VPN 1 on PE-agg:
# Create VE-L2VPN 1.
<PEagg> system-view
[PEagg] interface ve-l2vpn 1
[PEagg-VE-L2VPN1] quit
# Create VE-L3VPN 1, and configure an IPaddress for the interface.
[PEagg] interface ve-l3vpn 1
[PEagg-VE-L3VPN1] ip address100.1.1.2 24
[PEagg-VE-L3VPN1] quit
3.Configure MPLS L2VPN:
a.Configure OSPF on PE 1, P, and PE-agg, andadvertise interface addresses:
# Configure PE 1.
<PE1> system-view
[PE1] ospf
[PE1-ospf-1] area 0
[PE1-ospf-1-area-0.0.0.0]network 1.1.1.9 0.0.0.0
[PE1-ospf-1-area-0.0.0.0] network10.2.1.0 0.0.0.255
[PE1-ospf-1-area-0.0.0.0] quit
[PE1-ospf-1] quit
# Configure the P device.
<P> system-view
[P] ospf
[P-ospf-1] area 0
[P-ospf-1-area-0.0.0.0]network 2.2.2.9 0.0.0.0
[P-ospf-1-area-0.0.0.0]network 10.2.2.0 0.0.0.255
[P-ospf-1-area-0.0.0.0] network10.2.1.0 0.0.0.255
[P-ospf-1-area-0.0.0.0] quit
[P-ospf-1] quit
# Configure PE-agg.
[PEagg] ospf
[PEagg-ospf-1] area 0
[PEagg-ospf-1-area-0.0.0.0]network 3.3.3.9 0.0.0.0
[PEagg-ospf-1-area-0.0.0.0]network 10.2.2.0 0.0.0.255
[PEagg-ospf-1-area-0.0.0.0]quit
[PEagg-ospf-1] quit
b.Configure basic MPLS and MPLS LDP on PE 1,P, and PE-agg:
# Configure PE 1.
[PE1] mpls lsr-id 1.1.1.9
[PE1] mpls ldp
[PE1-ldp] lsp-trigger all
[PE1-ldp] quit
[PE1] interface pos 2/2/0
[PE1-Pos2/2/0] mpls enable
[PE1-Pos2/2/0] mpls ldp enable
[PE1-Pos2/2/0] quit
# Configure the P device.
[P] mpls lsr-id 2.2.2.9
[P] mpls ldp
[P-ldp] lsp-trigger all
[P-ldp] quit
[P] interface pos 2/2/0
[P-Pos2/2/0] mpls enable
[P-Pos2/2/0] mpls ldp enable
[P-Pos2/2/0] quit
[P] interface pos 2/2/1
[P-Pos2/2/1] mpls enable
[P-Pos2/2/1] mpls ldp enable
[P-Pos2/2/1] quit
# Configure PE-agg.
[PEagg] mpls lsr-id 3.3.3.9
[PEagg] mpls ldp
[PEagg-ldp] lsp-trigger all
[PEagg-ldp] quit
[PEagg] interface pos 2/2/0
[PEagg-Pos2/2/0] mpls enable
[PEagg-Pos2/2/0] mpls ldpenable
[PEagg-Pos2/2/0] quit
c.Enable L2VPN on PE 1 and PE-agg:
# Configure PE 1.
[PE1] l2vpn enable
# Configure PE-agg.
[PEagg] l2vpn enable
d.Create VSIs on PE 1 and PE-agg:
# On PE 1, create VSI vpna, andspecify the PW signaling protocol for the VSI as LDP.
[PE1] vsi vpna
[PE1-vsi-vpna] pwsignaling ldp
# On PE 1, create LDP PW 500 to the peerPE 3.3.3.9.
[PE1-vsi-vpna-ldp] peer 3.3.3.9pw-id 500
[PE1-vsi-vpna-ldp-3.3.3.9-500]quit
[PE1-vsi-vpna-ldp] quit
[PE1-vsi-vpna] quit
# On PE-agg, create VSI vpna, andspecify the PW signaling protocol for the VSI as LDP.
[PEagg] vsi vpna
[PEagg-vsi-vpna] pwsignaling ldp
# On PE-agg, create an LDP PW: specifythe peer PE address as 1.1.1.9, and set the PW ID to 500.
[PEagg-vsi-vpna-ldp] peer 1.1.1.9pw-id 500
[PEagg-vsi-vpna-ldp-1.1.1.9-500]quit
[PEagg-vsi-vpna-ldp] quit
[PEagg-vsi-vpna] quit
e.Bind the AC interface to the VSI on PE 1 andPE-agg:
# On PE 1, bind GigabitEthernet 1/0/1 to VSI vpna.
[PE1] interface gigabitethernet 1/0/1
[PE1-GigabitEthernet1/0/1] xconnect vsi vpna
[PE1-GigabitEthernet1/0/1] quit
# On PE-agg, bind VE-L2VPN 1 to VSI vpna.
[PEagg] interface ve-l2vpn 1
[PEagg-VE-L2VPN1] xconnect vsivpna
[PEagg-VE-L2VPN1] quit
4.Configure OSPF process 2 to advertiserouting information on the IP backbone:
# Configure CE 1.
[CE1] ospf 2
[CE1-ospf-2] area 0
[CE1-ospf-2-area-0.0.0.0]network 100.1.1.0 0.0.0.255
[CE1-ospf-2-area-0.0.0.0] quit
[CE1-ospf-2] quit
# Configure PE-agg.
[PEagg] ospf 2
[PEagg-ospf-2] area 0
[PEagg-ospf-2-area-0.0.0.0]network 100.1.1.0 0.0.0.255
[PEagg-ospf-2-area-0.0.0.0]network 10.3.3.0 0.0.0.255
[PEagg-ospf-2-area-0.0.0.0]quit
[PEagg-ospf-2] quit
# Configure PE 2.
<PE2> system-view
[PE2] ospf 2
[PE2-ospf-2] area 0
[PE2-ospf-2-area-0.0.0.0]network 100.2.1.0 0.0.0.255
[PE2-ospf-2-area-0.0.0.0]network 10.3.3.0 0.0.0.255
[PE2-ospf-2-area-0.0.0.0] quit
[PE2-ospf-2] quit
# Configure CE 2.
<CE2> system-view
[CE2] ospf 2
[CE2-ospf-2] area 0
[CE2-ospf-2-area-0.0.0.0]network 100.2.1.0 0.0.0.255
[CE2-ospf-2-area-0.0.0.0] quit
[CE2-ospf-2] quit
5.The default MTU value varies by interfacetype. To avoid packet fragmentation, set the MTU value for each POS interfaceon each device to 1500 bytes. The following shows the MTU configuration on PE1.
[PE1] int pos 2/2/0
[PE1-Pos2/2/0] mtu 1500
[PE1-Pos2/2/0] shutdown
[PE1-Pos2/2/0] undo shutdown
Verifying theconfiguration
# Ping CE 2 from CE 1 to verify theirconnectivity.
<CE1> ping 100.2.1.2
Ping 100.2.1.2 (100.2.1.2): 56 databytes, press CTRL_C to break
56 bytes from 100.2.1.2: icmp_seq=0ttl=128 time=1.073 ms
56 bytes from 100.2.1.2: icmp_seq=1ttl=128 time=1.428 ms
56 bytes from 100.2.1.2: icmp_seq=2ttl=128 time=19.367 ms
56 bytes from 100.2.1.2: icmp_seq=3ttl=128 time=1.013 ms
56 bytes from 100.2.1.2: icmp_seq=4ttl=128 time=0.684 ms
--- Ping statistics for 100.2.1.2 ---
5 packet(s) transmitted, 5 packet(s)received, 0.0% packet loss
round-trip min/avg/max/std-dev =0.684/4.713/19.367/7.331 ms
Example: Configuring LDP PW access to IP backbone through L2VEsubinterfaces
Network configuration
Create LDP PWs between PE 1 and PE-agg onthe L2VPN access network, so that CE 1 and CE 2 can access the IP backbonethrough the PWs.
Configure L2VPN access to the IP backbonethrough L2VE subinterfaces.
Configure OSPF process 2 to advertiserouting information on the IP backbone.
Figure 5 Network diagram
Table 3 Interface and IP address assignment
| Device | Interface | IP address | Device | Interface | IP address |
| CE 1 | GE1/0/1 | 100.1.1.1/24 | CE 2 | GE 1/0/1 | 100.1.1.2/24 |
| PE 1 | Loop0 | 1.1.1.9/32 | PE-agg | Loop0 | 3.3.3.9/32 |
| POS2/2/0 | 10.2.1.1/24 | POS2/2/0 | 10.2.2.2/24 | ||
| P | Loop0 | 2.2.2.9/32 | POS2/2/1 | 10.3.3.1/24 | |
| POS2/2/0 | 10.2.1.2/24 | VE-L3VPN1 | 100.1.1.3/24 | ||
| POS2/2/1 | 10.2.2.1/24 | PE 2 | POS2/2/0 | 10.3.3.2/24 | |
| CE 3 | GE1/0/1 | 100.2.1.2/24 | GE1/0/1 | 100.2.1.1/24 |
Procedure
1.Configure IP addresses for interfaces asshown in Table 3. (Details not shown.)
2.Create VE-L2VPN 1 and VE-L3VPN 1 on PE-agg:
# Create VE-L2VPN 1, VE-L2VPN 1.1, andVE-L2VPN 1.2.
<PEagg> system-view
[PEagg] interface ve-l2vpn 1
[PEagg-VE-L2VPN1] quit
[PEagg] interface ve-l2vpn 1.1
[PEagg-VE-L2VPN1.1] quit
[PEagg] interface ve-l2vpn 1.2
[PEagg-VE-L2VPN1.2] quit
# Create VE-L3VPN 1, and configure an IPaddress for the interface.
[PEagg] interface ve-l3vpn 1
[PEagg-VE-L3VPN1] ip address100.1.1.3 24
[PEagg-VE-L3VPN1] quit
3.Configure MPLS L2VPN:
a.Configure OSPF on PE 1, P, and PE-agg, andadvertise interface addresses:
# Configure PE 1.
<PE1> system-view
[PE1] ospf
[PE1-ospf-1] area 0
[PE1-ospf-1-area-0.0.0.0]network 1.1.1.9 0.0.0.0
[PE1-ospf-1-area-0.0.0.0]network 10.2.1.0 0.0.0.255
[PE1-ospf-1-area-0.0.0.0] quit
[PE1-ospf-1] quit
# Configure the P device.
<P> system-view
[P] ospf
[P-ospf-1] area 0
[P-ospf-1-area-0.0.0.0]network 2.2.2.9 0.0.0.0
[P-ospf-1-area-0.0.0.0]network 10.2.2.0 0.0.0.255
[P-ospf-1-area-0.0.0.0] network10.2.1.0 0.0.0.255
[P-ospf-1-area-0.0.0.0] quit
[P-ospf-1] quit
# Configure PE-agg.
[PEagg] ospf
[PEagg-ospf-1] area 0
[PEagg-ospf-1-area-0.0.0.0]network 3.3.3.9 0.0.0.0
[PEagg-ospf-1-area-0.0.0.0]network 10.2.2.0 0.0.0.255
[PEagg-ospf-1-area-0.0.0.0]quit
[PEagg-ospf-1] quit
b.Configure basic MPLS and MPLS LDP on PE 1,P, and PE-agg:
# Configure PE 1.
[PE1] mpls lsr-id 1.1.1.9
[PE1] mpls ldp
[PE1-ldp] lsp-trigger all
[PE1-ldp] quit
[PE1] interface pos 2/2/0
[PE1-Pos2/2/0] mpls enable
[PE1-Pos2/2/0] mpls ldp enable
[PE1-Pos2/2/0] quit
# Configure the P device.
[P] mpls lsr-id 2.2.2.9
[P] mpls ldp
[P-ldp] lsp-trigger all
[P-ldp] quit
[P] interface pos 2/2/0
[P-Pos2/2/0] mpls enable
[P-Pos2/2/0] mpls ldp enable
[P-Pos2/2/0] quit
[P] interface pos 2/2/1
[P-Pos2/2/1] mpls enable
[P-Pos2/2/1] mpls ldp enable
[P-Pos2/2/1] quit
# Configure PE-agg.
[PEagg] mpls lsr-id 3.3.3.9
[PEagg] mpls ldp
[PEagg-ldp] lsp-trigger all
[PEagg-ldp] quit
[PEagg] interface pos 2/2/0
[PEagg-Pos2/2/0] mpls enable
[PEagg-Pos2/2/0] mpls ldpenable
[PEagg-Pos2/2/0] quit
c.Enable L2VPN on PE 1 and PE-agg:
# Configure PE 1.
[PE1] l2vpn enable
# Configure PE-agg.
[PEagg] l2vpn enable
d.Create cross-connect groups on PE 1 andPE-agg:
# On PE-agg, create a cross-connect groupnamed vpna, create a cross-connect named ldp in the group, and bind VE-L2VPN 1.1to the cross-connect.
[PEagg] xconnect-group vpna
[PEagg-xcg-vpna] connection ldp
[PEagg-xcg-vpna-ldp] acinterface ve-l2vpn 1.1
# On PE-agg, create an LDP PW for thecross-connect to bind the AC to the PW.
[PEagg-xcg-vpna-ldp] peer 1.1.1.9pw-id 500
[PEagg-xcg-vpna-ldp-1.1.1.9-500]quit
[PEagg-xcg-vpna-ldp] quit
[PEagg-xcg-vpna] quit
# On PE-agg, create a cross-connect groupnamed vpnb, create a cross-connect named ldp in the group, and bind VE-L2VPN 1.2to the cross-connect.
[PEagg] xconnect-group vpnb
[PEagg-xcg-vpnb] connection ldp
[PEagg-xcg-vpnb-ldp] acinterface ve-l2vpn 1.2
# On PE-agg, create an LDP PW for thecross-connect to bind the AC to the PW.
[PEagg-xcg-vpnb-ldp] peer 1.1.1.9pw-id 501
[PEagg-xcg-vpnb-ldp-1.1.1.9-501]quit
[PEagg-xcg-vpnb-ldp] quit
[PEagg-xcg-vpnb] quit
# On PE 1, create a cross-connect groupnamed vpna, create a cross-connect named ldp in the group, and bind GigabitEthernet 1/0/1 to the cross-connect.
[PE1] xconnect-group vpna
[PE1-xcg-vpna] connection ldp
[PE1-xcg-vpna-ldp] acinterface gigabitethernet 1/0/1
# On PE 1, create an LDP PW for thecross-connect to bind the AC to the PW.
[PE1-xcg-vpna-ldp] peer3.3.3.9 pw-id 500
[PE1-xcg-vpna-ldp-3.3.3.9-500]quit
[PE1-xcg-vpna-ldp] quit
[PE1-xcg-vpna] quit
# On PE 1, create a cross-connect groupnamed vpnb, create a cross-connect named ldp in the group, and bind GigabitEthernet 1/0/2 to the cross-connect.
[PE1]xconnect-group vpnb
[PE1-xcg-vpnb]connection ldp
[PE1-xcg-vpnb-ldp] acinterface gigabitethernet 1/0/2
# On PE 1, create an LDP PW for thecross-connect to bind the AC to the PW.
[PE1-xcg-vpnb-ldp] peer 3.3.3.9pw-id 501
[PE1-xcg-vpnb-ldp-3.3.3.9-500]quit
[PE1-xcg-vpnb-ldp] quit
[PE1-xcg-vpnb] quit
4.Configure OSPF process 2 to advertiserouting information on the IP backbone:
# Configure CE 1.
[CE1] ospf 2
[CE1-ospf-2] area 0
[CE1-ospf-2-area-0.0.0.0] network100.1.1.0 0.0.0.255
[CE1-ospf-2-area-0.0.0.0] quit
[CE1-ospf-2] quit
# Configure PE-agg.
[PEagg] ospf 2
[PEagg-ospf-2] area 0
[PEagg-ospf-2-area-0.0.0.0]network 100.1.1.0 0.0.0.255
[PEagg-ospf-2-area-0.0.0.0]network 10.3.3.0 0.0.0.255
[PEagg-ospf-2-area-0.0.0.0]quit
[PEagg-ospf-2] quit
# Configure PE 2.
<PE2> system-view
[PE2] ospf 2
[PE2-ospf-2] area 0
[PE2-ospf-2-area-0.0.0.0]network 100.2.1.0 0.0.0.255
[PE2-ospf-2-area-0.0.0.0]network 10.3.3.0 0.0.0.255
[PE2-ospf-2-area-0.0.0.0] quit
[PE2-ospf-2] quit
# Configure CE 2.
<CE2> system-view
[CE2] ospf 2
[CE2-ospf-2] area 0
[CE2-ospf-2-area-0.0.0.0]network 100.2.1.0 0.0.0.255
[CE2-ospf-2-area-0.0.0.0] quit
[CE2-ospf-2] quit
5.The default MTU value varies by interfacetype. To avoid packet fragmentation, set the MTU value for each POS interfaceon each device to 1500 bytes. The following shows the MTU configuration on PE1.
[PE1] int pos 2/2/0
[PE1-Pos2/2/0] mtu 1500
[PE1-Pos2/2/0] shutdown
[PE1-Pos2/2/0] undo shutdown
Verifying theconfiguration
# Ping CE 3 from CE 1 and CE 2 to verify theconnectivity. This example uses CE 1.
<CE1> ping 100.2.1.2
Ping 100.2.1.2 (100.2.1.2): 56 databytes, press CTRL_C to break
56 bytes from 100.2.1.2: icmp_seq=0ttl=128 time=1.073 ms
56 bytes from 100.2.1.2: icmp_seq=1ttl=128 time=1.428 ms
56 bytes from 100.2.1.2: icmp_seq=2ttl=128 time=19.367 ms
56 bytes from 100.2.1.2: icmp_seq=3ttl=128 time=1.013 ms
56 bytes from 100.2.1.2: icmp_seq=4ttl=128 time=0.684 ms
--- Ping statistics for 100.2.1.2 ---
5 packet(s) transmitted, 5 packet(s)received, 0.0% packet loss
round-trip min/avg/max/std-dev =0.684/4.713/19.367/7.331 ms
