104 - ODR002106 NE Series Routers MPLS L2VPN Practice Guide Based On ISSUE 1.00
104 - ODR002106 NE Series Routers MPLS L2VPN Practice Guide Based On ISSUE 1.00
104 - ODR002106 NE Series Routers MPLS L2VPN Practice Guide Based On ISSUE 1.00
Guide
NE Series Routers MPLS L2VPN Practice Guide
Contents
Typical Usage Scenarios of MPLS L2VPN ....................................................................... 1
Experiment Description..................................................................................................... 3
Environment Introduction .................................................................................................................. 3
Objectives ......................................................................................................................................... 3
References ....................................................................................................................................... 3
Topology ........................................................................................................................................... 3
Tasks ................................................................................................................................................ 4
Configuration Preparation ................................................................................................................. 4
Configuration Flowchart .................................................................................................................... 5
FAQ ................................................................................................................................... 19
Answers ............................................................................................................................ 20
As shown in the preceding figure, the enterprises have a small number of branches, and therefore
only point-to-point (P2P) L2VPN services are required. Carriers can provide simple P2P VLL
connections over an MPLS MAN to implement Layer 2 leased line interconnections between the
branches.
As shown in the preceding figure, HSI users access the BRAS using Layer 2 PPPoE. When HSI
users are scattered, they access the BRAS over an MAN. VLL can be deployed between the PEs
on the MAN to transparently transmit Layer 2 PPPoE dial-up packets.
VLL is used for Layer 2 leased line interconnections for enterprise VPNs in a country. Transparent transmission for HSI
user packets applies when dial-up users abroad are scattered.
Experiment Description
Environment Introduction
This guide describes basic configuration methods of and configuration procedures for MPLS
L2VPN. This guide also covers main technologies related to MPLS L2VPN. Router Visio 1.6.7 is
used to build an experiment environment.
Objectives
Configure MPLS L2VPN.
Troubleshoot MPLS L2VPN faults.
References
NE40E&NE80E Command Reference 04
Topology
In the topology, the three CEs on VPNA are connected using VLL. The CEs' Loopback1 addresses
are used to simulate network segment routes. For details about interfaces, IP addresses, IGP and
MPLS, see the topology.
Tasks
Task Description
1 Run OSPF to implement interworking between the devices in the MPLS domain.
2 Configure sub-interface VLAN IDs and VPN IP network segments, use local CCC to
connect CE1 and CE2 over E0/0/1.1, and ensure that the simulated network IP
addresses of CE1 and CE2 are reachable.
3 Configure sub-interface VLAN IDs and VPN IP network segments, use remote CCC to
connect CE2 and CE3 over E0/0/1.2, and ensure that the sub-interface network
segment IP addresses are reachable.
4 Configure sub-interface VLAN IDs and VPN IP network segments, use Martini to
connect CE2 and CE3 over E0/0/1.3, and ensure that the simulated network IP
addresses of CE2 and CE3 are reachable.
5 Configure sub-interface VLAN IDs and VPN IP network segments, use SVC to connect
CE2 and CE3 over E0/0/1.4, and ensure that the sub-interface network segment IP
addresses are reachable.
6 Configure sub-interface VLAN IDs and VPN IP network segments, use VLL at one end
and VPLS at the other end to connect CE2 and CE3 over E0/0/1.5, and ensure that the
sub-interface network segment IP addresses are reachable.
Configuration Preparation
Before you configure MPLS L2VPN, complete the following operations:
Connect and power on devices.
Configure interface IP addresses and loopback interface addresses.
Configuration Flowchart
Configuration description
Operation View Command
Configure an IP [Quidway-Ethernet0/0/0] ip address ip-address mask | mask-length
address.
Configure CE1
<Quidway>system-view
[Quidway]sysname CE1
[CE1]interface LoopBack 1
[CE1-LoopBack1]ip address 11.11.11.11 32
Configure CE2
<Quidway>system-view
[Quidway]sysname CE2
[CE2]interface LoopBack 1
[CE2-LoopBack1]ip address 21.21.21.21 32
Configure CE3
<Quidway>system-view
[Quidway]sysname CE3
[CE3]interface LoopBack 1
[CE3-LoopBack1]ip address 31.31.31.31 32
Configure PEA
<Quidway>system-view
[Quidway]sysname PEA
[PEA]interface Ethernet 0/0/2
[PEA-Ethernet0/0/2]ip address 10.1.1.1 30
[PEA-Ethernet0/0/2]undo shutdown
[PEA-Ethernet0/0/2]quit
[PEA]interface LoopBack 0
[PEA-LoopBack0]ip address 1.1.1.1 32
Configure PEB
<Quidway>system-view
[Quidway]sysname PEB
[PEB]interface Ethernet 0/0/2
[PEB-Ethernet0/0/2]ip address 10.1.1.2 30
[PEB-Ethernet0/0/2]undo shutdown
[PEB-Ethernet0/0/2]quit
[PEB]interface LoopBack 0
[PEB-LoopBack0]ip address 2.2.2.2 32
Configuration description
Operation View Command
Configure a router ID. [Quidway] router id router-id
Configure PEA
[PEA]router id 1.1.1.1
[PEA]ospf 1
[PEA-ospf-1]area 0
[PEA-ospf-1-area-0.0.0.0]network 10.1.1.0 0.0.0.3
[PEA-ospf-1-area-0.0.0.0]network 1.1.1.1 0.0.0.0
Configure PEB
[PEB]router id 2.2.2.2
[PEB]ospf 1
[PEB-ospf-1]area 0
[PEB-ospf-1-area-0.0.0.0]network 10.1.1.0 0.0.0.3
[PEB-ospf-1-area-0.0.0.0]network 2.2.2.2 0.0.0.0
Configuration description
According to experiment requirements, plan sub-interface VLAN IDs and VPN IP network segments. The PEs and CEs
use sub-interfaces, for example, E0/0/1.1. The VLAN ID is 10, and the VPN IP network segment is 172.168.1.0/24. The
IP address of CE1's sub-interface is 172.168.1.1/24, and the IP address of CE2's sub-interface is 172.168.1.2/24. To
ensure that the simulated network IP addresses of CE1 and CE2 are reachable, configure static routes on the CEs.
Configure PEA
[PEA]mpls lsr-id 1.1.1.1
[PEA]mpls
[PEA-mpls]quit
[PEA]mpls l2vpn
[PEA-l2vpn]quit
Configure CE1
[CE1]interface Ethernet 0/0/1.1
[CE1-Ethernet0/0/1.1]vlan-type dot1q 10
[CE1-Ethernet0/0/1.1]ip address 172.168.1.1 24
[CE1-Ethernet0/0/1.1]quit
[CE1]interface Ethernet 0/0/1
[CE1-Ethernet0/0/1]undo shutdown
[CE1]ip route-static 21.21.21.21 32 172.168.1.2
Configure CE2
[CE2]interface Ethernet 0/0/0.1
[CE2-Ethernet0/0/0.1]vlan-type dot1q 10
[CE2-Ethernet0/0/0.1]ip address 172.168.1.2 24
[CE2-Ethernet0/0/0.1]quit
[CE2]interface Ethernet 0/0/0
[CE2-Ethernet0/0/0]undo shutdown
[CE2]ip route-static 11.11.11.11 32 172.168.1.1
Configuration description
According to experiment requirements, plan sub-interface VLAN IDs and VPN IP network segments. The PEs and CEs
use sub-interfaces, for example, E0/0/1.2. The VLAN ID is 20, and the VPN IP network segment is 172.168.2.0/24. The
IP address of CE2's sub-interface is 172.168.2.2/24, and the IP address of CE3's sub-interface is 172.168.2.3/24.
Configure PEA
[PEA]mpls lsr-id 1.1.1.1
[PEA]mpls
[PEA-mpls]quit
[PEA]interface Ethernet 0/0/2
[PEA-Ethernet0/0/2]mpls
[PEA-Ethernet0/0/2]quit
[PEA]interface Ethernet0/0/0.2
[PEA-Ethernet0/0/0.2]vlan-type dot1q 20
[PEA-Ethernet0/0/0.2]quit
[PEA]mpls l2vpn
When you create a static LSP, the local incoming and outgoing labels must correspond to the remote outgoing and
incoming labels, respectively.
Configure PEB
[PEB]mpls lsr-id 2.2.2.2
[PEB]mpls
[PEB-mpls]quit
[PEB]interface Ethernet 0/0/2
[PEB-Ethernet0/0/2]mpls
[PEB-Ethernet0/0/2]quit
[PEB]interface Ethernet 0/0/1.2
[PEB-Ethernet0/0/1.2]vlan-type dot1q 20
[PEB-Ethernet0/0/1.2]quit
[PEB]interface ethernet 0/0/1
[PEB-Ethernet0/0/1]undo shutdown
[PEB]mpls l2vpn
[PEB-l2vpn]quit
[PEB]ccc CE3-CE2 interface Ethernet0/0/1.2 in-label 400 out-label 300 nexthop 10.1.1.1
Configure CE2
[CE2]interface Ethernet 0/0/0.2
[CE2-Ethernet0/0/0.2]vlan-type dot1q 20
[CE2-Ethernet0/0/0.2]ip address 172.168.2.2 24
[CE2-Ethernet0/0/0.2]quit
Configure CE3
[CE3]interface Ethernet 0/0/1.2
[CE3-Ethernet0/0/1.2]vlan-type dot1q 20
[CE3-Ethernet0/0/1.2]ip address 172.168.2.3 24
[CE3-Ethernet0/0/1.2]quit
[CE3]interface Ethernet 0/0/1
[CE3-Ethernet0/0/1]undo shutdown
Configuration description
According to experiment requirements, plan sub-interface VLAN IDs and VPN IP network segments. The PEs and CEs
use sub-interfaces, for example, E0/0/1.3. The VLAN ID is 30, and the VPN IP network segment is 172.168.3.0/24. The
IP address of CE2's sub-interface is 172.168.3.2/24, and the IP address of CE3's sub-interface is 172.168.3.3/24. To
ensure that the simulated network IP addresses of CE2 and CE3 are reachable, configure static routes on the CEs.
Configure PEA
[PEA]mpls lsr-id 1.1.1.1
[PEA]mpls
[PEA-mpls]quit
[PEA]interface Ethernet 0/0/2
[PEA-Ethernet0/0/2]mpls
[PEA-Ethernet0/0/2]quit
\\Create a remote MPLS LDP peer and enter the remote MPLS LDP peer view.
[PEA-mpls-ldp-remote-abc]remote-ip 2.2.2.2
[PEA-mpls-ldp-remote-abc]quit
Configure PEB
[PEB]mpls lsr-id 2.2.2.2
[PEB]mpls
[PEB-mpls]quit
[PEB]interface Ethernet 0/0/2
[PEB-Ethernet0/0/2]mpls
[PEB-Ethernet0/0/2]quit
Configure CE2
[CE2]interface ethernet0/0/0.3
[CE2-Ethernet0/0/0.3]vlan-type dot1q 30
[CE2-Ethernet0/0/0.3]ip address 172.168.3.2 24
[CE2]ip route-static 31.31.31.31 32 172.168.3.3
Configure CE3
[CE3]interface Ethernet 0/0/1.3
[CE3-Ethernet0/0/0.3]vlan-type dot1q 30
[CE3-Ethernet0/0/0.3]ip address 172.168.3.3 24
[CE3]ip route-static 21.21.21.21 32 172.168.3.2
Configuration description
According to experiment requirements, plan sub-interface VLAN IDs and VPN IP network segments. The PEs and CEs
use sub-interfaces, for example, E0/0/1.4. The VLAN ID is 40, and the VPN IP network segment is 172.168.4.0/24. The
IP address of CE2's sub-interface is 172.168.4.2/24, and the IP address of CE3's sub-interface is 172.168.4.3/24.
Configure PEA
[PEA]mpls lsr-id 1.1.1.1
[PEA]mpls
[PEA-mpls]quit
[PEA]interface Ethernet 0/0/2
[PEA-Ethernet0/0/2]mpls
[PEA-Ethernet0/0/2]quit
[PEA]mpls ldp
[PEA-mpls-ldp]quit
[PEA]interface Ethernet 0/0/2
[PEA-Ethernet0/0/2]mpls ldp
[PEA-Ethernet0/0/2]quit
Configure PEB
[PEB]mpls lsr-id 2.2.2.2
[PEB]mpls
[PEB-mpls]quit
[PEB]interface Ethernet 0/0/2
[PEB-Ethernet0/0/2]mpls
[PEB-Ethernet0/0/2]quit
[PEB]mpls ldp
[PEB-mpls-ldp]quit
[PEB]interface Ethernet 0/0/2
[PEB-Ethernet0/0/2]mpls ldp
[PEB-Ethernet0/0/2]quit
\\Ensure that the transmit and receive labels on PEA correspond to the receive and transmit labels
on PEB, respectively.
Configure CE2
[CE2]interface Ethernet 0/0/0.4
[CE2-Ethernet0/0/0.4]vlan-type dot1q 40
[CE2-Ethernet0/0/0.4]ip address 172.168.4.2 24
Configure CE3
[CE3]interface Ethernet 0/0/1.4
[CE3-Ethernet0/0/1.4]vlan-type dot1q 40
[CE3-Ethernet0/0/1.4]ip address 172.168.4.3 24
The command output shows that one static L2 VC has been established.
2. Run the ping command to check link connectivity. For example, run the ping command on
CE2 to ping CE3's sub-interface IP address.
[CE2]ping 172.168.4.3
PING 172.168.4.3: 56 data bytes, press CTRL_C to break
Reply from 172.168.4.3: bytes=56 Sequence=1 ttl=255 time=110 ms
Reply from 172.168.4.3: bytes=56 Sequence=2 ttl=255 time=60 ms
Reply from 172.168.4.3: bytes=56 Sequence=3 ttl=255 time=90 ms
Reply from 172.168.4.3: bytes=56 Sequence=4 ttl=255 time=50 ms
Reply from 172.168.4.3: bytes=56 Sequence=5 ttl=255 time=90 ms
--- 172.168.4.3 ping statistics ---
5 packet(s) transmitted
5 packet(s) received
0.00% packet loss
round-trip min/avg/max = 50/80/110 ms
FAQ
1. Which of the following commands can I use to view brief information about all LDP Layer 2
VCs? ( )
Answers
1. C
2. The inner label used in Martini mode is a VC label. To enable two CEs to communicate,
configure the same VC ID for the two CEs. However, the VC ID on a PE is unique. Therefore,
local connections are not supported. SVC is a static Martini connection.