Escolar Documentos
Profissional Documentos
Cultura Documentos
Table of Contents
Table of Contents
1.1 MPLS L2VPN Overview ....................................................................................................1 1.1.1 Introduction to MPLS L2VPN...................................................................................1 1.1.2 Packet Forwarding...................................................................................................2 1.1.3 Implementation........................................................................................................3 1.2 CCC MPLS L2VPN Configuration......................................................................................5 1.2.1 Configuring CCC MPLS L2VPN...............................................................................5 1.2.2 CCC MPLS L2VPN Configuration Example.............................................................7 1.3 Martini MPLS L2VPN Configuration..................................................................................11 1.3.1 Configuring Martini MPLS L2VPN..........................................................................11 1.3.2 Martini MPLS L2VPN Configuration Example........................................................12 1.4 Kompella MPLS L2VPN Configuration.............................................................................16 1.4.1 Configuring Kompella MPLS L2VPN......................................................................16 1.4.2 Kompella MPLS L2VPN Configuration Example....................................................18 1.5 Displaying and Debugging MPLS L2VPN.........................................................................22 1.6 Troubleshooting MPLS L2VPN.........................................................................................23
1.1
MPLS L2VPN
MPLS L2VPN
Note: L2VPN mentioned in the following section refers to the L2VPN implemented through virtual leased line (VLL).
Figure 1.1 MPLS L2VPN MPLS L2VPN has the following advantages:
Multiple network layer protocols supported, such as IP, IPv6, IPX, and SNA. Powerfulextensibility. MPLS L2VPN only establishes Layer 2 connections, rather than imports and manages the routing information. This eases work load of PE (provider edge) devices and the entire SP (service provider) network remarkably and thus enables SPs to provide more VPNs and accommodate more users.
Reliability and privacy of user routes. As no user routing information is imported, there is no need for MPLS L2VPN to obtain and process the information, ensuring the privacy of user routes.
Error: Reference source not found illustrates the structure of an MPLS L2VPN packet.
1.1
MPLS L2VPN
VC label label
L2 PDU PDU
Figure 1.2 Structure of an MPLS L2VPN packet The fields in an MPLS L2VPN packet are described as follows: Tunnel label (the outer label) is an MPLS lable or a GRE label. It is used to transmit a packet from one PE to anther. VC label (the inner label) is a lower layer label used to identify the links between PEs and CEs. Packets of MPLS L2VPNs implemented through circuit cross connect (CCC) do not contain this label. Data in MPLS L2VPN can be encapsulated as Ethernet or VLAN packets at the data link layer. At present, data of different nodes in a VPN must be encapsulated as the same type of packets.
1.1
MPLS L2VPN
CE1
PE1
PE2
CE2
L2 PDU
T V L2 PDU
V L2 PDU
L2 PDU
1.1.3 Implementation
At present, the official standard for MPLS L2VPN has not been established yet. However, the PPVPN (Provider-provisioned Virtual Private Network) group of IETF (Internet Engineering Task Force) defines multiple framework drafts, two of which are commonly used. They are known as Martini draft and Kompella draft. Till May, 2005, they are depicted in the following documents respectively: draft-martini-l2circuit-trans-m pls-09.txt draft-kompella-ppvpn-l2vpn-02.txt Martini draft defines the way to implement MPLS L2VPN by establishing point-to-point links. Here, LDP (label distribution protocol) is used as the signaling protocol to exchange VC labels. This kind of MPLS L2VPNs is known as Martini MPLS L2VPNs. Kompella draft defines how to establish MPLS L2VPNs in MPLS networks through endto-end (CE-to-CE) connections. At present, BGP (border gateway protocol) is used as the signaling protocol to propagate the information about Layer 2 reachability and VC labels. This kind of MPLS L2VPNs is known as Kompella MPLS L2VPN. Also, you can establish MPLS L2VPNs without signaling protocols. In this case, MPLS L2VPN services are provided through statically configured VC labels. An example of this is CCC, which implement MPLS L2VPNs through static configuration. Error: Reference source not found describes the features and implementation ways of the above three types of MPLS L2VPNs.
1.1
MPLS L2VPN
3.1 Features and implementation ways of the three types of MPLS L2VPNs VPN type CCC Implementation Configures static LSPs to implement MPLS L2VPN. You sending packets must and manually receiving for configure two LSPs (for respectively) Feature Data is transmitted through packets with single-layer labels. LSPs are used exclusively. No signaling is needed to transmit the Layer 2 VPN information. Only MPLS forwarding is required. In this way, CEs of different SPs can be interconnected easily.
each CCC connection node by node (including PEs and Ps). The configured LSPs can only be used of to the CCC transmit packets
Uses extended LDP as the signaling to transmit the VC information. Uses VC-TYPE and VC-ID to identify VCs. VC-TYPE indicates the encapsulation type of data link layer, and VC-ID uniquely identifies a VC. PEs connecting VC CEs labels CEs exchange the
Local switching like CCC is not available. An LSP can be shared by multiple VCs.
1.1
MPLS L2VPN
Implementation Similar to Layer 3 BGP/MPLS VPN defined in RFC2547. PEs discover Layer 2 VPN nodes through automatically IBGP sessions
Feature Users can assign extra labels to VPNs for future use. This eases the configuration work loads of VPN deployment and capacity expansion. Vpn-target is used to identify VPNs. This brings great flexibility for VPN networking. Connections between CEs are not concerned. This type of MPLS L2VPN is implemented by dividing the entrie SP network into different VPNs and numbering these CEs in the VPNs. To establish a to connection between two CEs, you need to set the local CE ID and the remote CE ID on the PE, and specify the Circuit ID assigned CE. for the connection by the local
established between them. They also propagate the VPN information. Labels are distributed in the form of label blocks, which enables multiple connections being assigned tags simultaneously. The size of a tag block is determined by CE range (user-configurable). Vpn-target is used differentiate VPNs.
Note:
1.1
MPLS L2VPN
Configuration step Enable MPLS Create the egress for the static LSP mpls
Command
Description Required Required. Before configuring a CCC connection, you need to configure two static LSPs between the two PEs and all P routers in between for bidirectional packets. Refer to corresponding sections in the command manual for more information about these commands and corresponding undo commands.
static-lsp egress lsp-name l2vpn incoming-interface vlan-interface vlan-id inlabel in-label static-lsp ingress lsp-name l2vpn nexthop next-hopaddr out-label out-label static-lsp transit lsp-name l2vpn incoming-interface vlan-interface vlan-id inlabel in-label { nexthop next-hop-addr | outgoinginterface vlan-interface vlan-id } out-label out-label quit
Create the ingress for the static LSP Create the transit for the static LSP
Quit MPLS view and enter system view Enable L2VPN MPLS
mpls l2vpn ccc ccc-connection-name interface vlan-interface vlan-id out-interface ccc ccc-connection-name interface vlan-interface vlan-id transmit-lsp transmit-lsp-name receivelsp receive-lsp-name
Required Required. Two types of CCC connections exist: local CCC connection and remote CCC connection. A local CCC connection is established between two local CEs. It can be switched directly by the PE without being configured a static LSP. A remote CCC connection is established between the local CE and a remote CE. The two CEs are attached to different PEs. In this case, you need to configure two static LSPs for bidirectional packets transmitted between the two PEs.
1.1
MPLS L2VPN
Caution:
In L2VPN, you can configure only one virtual circuit for each VLAN interface. L2VPN supports VLAN interfaces only. When you configure an L2VPN on a VLAN interface, data is encapsulated as Ethernet packets by default. You must use cards with the silk screen of CA (such as LSB2FT48CA) for CCC MPLS L2VPN. You can configure only one VLAN on the access side of each VPN private network. Each VLAN can have only one interface, and all the VLANs connecting to the interface must have IGMP disabled.
You must configure two static LSPs for each remote CCC connection. Two CCC connections cannot share one static LSP. A static LSP used by a remote CCC connection cannot be used for other purposes (such as carrying IP packets and BGP/MPLS VPN packets). When you configure a static LSP for a CCC connection, the next hop must be the IP address from which the ARP packets are learnt.
Remote connection
1.1
MPLS L2VPN
# Configure a static LSP, with the out-label of 100 and the egress interface being the interface of VLAN 214.
[Quidway] mpls [Quidway-mpls] static-lsp ingress PEA-PEB l2vpn nexthop 5.5.5.2 out-label
1.1
MPLS L2VPN
# Configure a static LSP, with the in-label of 211 and the ingress interface being the interface of VLAN 214.
[Quidway-mpls] static-lsp egress PEB-PEA l2vpn incoming-interface vlaninterface 214 in-label 211
# Configure a static LSP, with the out-label of 200 and the egress interface being the interface of VLAN 212.
[Quidway-mpls] static-lsp ingress nexthop 6.6.6.2 out-label 200
# Configure a static LSP, with the in-label of 101 and the ingress interface being the interface of VLAN 212.
[Quidway-mpls] static-lsp egress PEA-PEB l2vpn incoming-interface vlaninterface 212 in-label 101
Configure P.
1.1
MPLS L2VPN
# Configure a static LSP, with the in-label of 100, the ingress interface being the interface of VLAN 211, the out-label of 101, and the egress interface being the interface of VLAN 212.
[Quidway-mpls] static-lsp transit PEA-PEB l2vpn incoming-intergace vlaninterface 211 in-label 100 nexthop 6.6.6.1 out1going-interface vlan-
# Configure a static LSP, with the in-label of 200, the ingress interface being the interface of VLAN 212, the out-label of 211, and the egress interface being the interface of VLAN 211.
[Quidway-mpls] static-lsp transit PEB-PEA l2vpn incoming-interface vlaninterface 212 in-label 200 nexthop 5.5.5.1 out-label 211
The interfaces of the two CE are physically up. The encapsulattion types of the interfaces of the two CEs are the same and are supported by the MPLS L2VPN.
For Layer 2 connections with the MPLS L2VPN being VLAN encapsulation, the VLAN IDs of the interfaces of the two CEs can either be the same or different. However, if a trunk is configured between the CEs and the PEs on both sides, the VLAN IDs of the interfaces of the two CEs must be the same.
1.1
MPLS L2VPN
Quit to system view Enter VLAN interface view Create a Martini MPLS L2VPN virtual connection in VLAN interface view
1.1
MPLS L2VPN
Caution:
You must use cards with the silk screen of CA (such as LSB2FT48CA) on the public network access side when configuring Martini MPLS L2VPN. You can configure only one VLAN on the access side of each VPN private network. Each VLAN can have only one interface. And all the VLANs connecting to the interface must have IGMP disabled.
L2VPN supports VLAN interfaces only. When you configure an L2VPN on a VLAN interface, data is encapsulated as Ethernet packets by default.
VLAN212 PE B
CE B
# Configure the LSR ID. Enable MPLS, LDP, and MPLS L2VPN.
[Quidway-A] mpls lsr-id 2.2.2.2 [Quidway-A] mpls [Quidway-A-mpls] quit [Quidway-A] mpls ldp [Quidway-A] mpls l2vpn
1.1
MPLS L2VPN
# Configure an IP address for the loopback interface, which is used as the router ID.
[Quidway-A] interface loopback 0 [Quidway-A-LoopBack0] ip address 192.1.1.1 255.255.255.255
# Enable OSPF.
[Quidway-A] ospf 1 [Quidway-A-ospf-1] area 0.0.0.0 [Quidway-A-ospf-1-area-0.0.0.0] network 192.1.1.1 0.0.0.0 [Quidway-A-ospf-1-area-0.0.0.0] network 168.1.1.1 0.0.255.255 [Quidway-A-ospf-1-area-0.0.0.0] network 192.2.1.0 0.0.0.255
2)
Configure PE-B.
# Configure the LSR ID. Enable MPLS, LDP, and MPLS L2VPN.
[Quidway-B] mpls lsr-id 192.1.1.2 [Quidway-B] mpls [Quidway-B-mpls] quit [Quidway-B] mpls ldp [Quidway-B] mpls l2vpn
1.1
MPLS L2VPN
# Configure an IP address for the loopback interface, which is used as the LSR ID.
[Quidway-B] interface loopback 0 [Quidway-B-LoopBack0] ip address 192.1.1.2 255.255.255.255
# Enable OSPF.
[Quidway-B] ospf 1 [Quidway-B-ospf-1] area 0.0.0.0 [Quidway-B-ospf-1-area-0.0.0.0] network 192.1.1.2 0.0.0.0 [Quidway-B-ospf-1-area-0.0.0.0] network 169.1.0.0 0.0.255.255 [Quidway-B-ospf-1-area-0.0.0.0] network 192.2.0.0 0.0.0.255
3)
Configure P.
# Configure the LSR ID. Enable MPLS, LDP, and MPLS L2VPN.
[Quidway-P] mpls lsr-id 192.1.1.3
1.1
MPLS L2VPN
# Configure an IP address for the loopback interface, which is used as the LSR ID.
[Quidway-P] interface loopback 0 [Quidway-P-LoopBack0] ip address 192.1.1.3 255.255.255.255 [Quidway-P-LoopBack0] quit
# Enable OSPF.
[Quidway-P] ospf 1 [Quidway-P-ospf-1] area 0.0.0.0 [Quidway-P-ospf-1-area-0.0.0.0] network 168.1.0.0 0.0.255.255 [Quidway-P-ospf-1-area-0.0.0.0] network 169.1.0.0 0.0.255.255 [Quidway-P-ospf-1-area-0.0.0.0] network 192.1.1.3 0.0.0.0
1.1
MPLS L2VPN
The interfaces of the two CE are physically up. Two LSP tunnels, which are opposite in direction, exist between two PEs. The encapsulattion types of interfaces of the two CEs are the same and are supported by the MPLS L2VPN.
LDP remote sessions exist between PEs and are in Operational state.
To establish a tunnel, routes to the peer PE are necessary. So you need to configure IGP (interior gateway protocol) on each router along the path, such as OSPF.
l2vpn-family
Required. By default, only the peers of BGP IPv4 unicast address families are active. The peer groups of other types are deactivated and thus cannot exchange the routing information.
quit
1.1
MPLS L2VPN
Configuration step Create a VPN and specify the encapsulation type. Configure the RD (route distinguisher) of the MPLS L2VPN
Description Required. The default encapsulation type is Ethernet. Required. For an MPLS L2VPN, you must configure the RD before performing other configurations. An RD cannot be modified once it is configured. The only way to modify a configured RD is to remove the corresponding MPLS L2VPN and create another one. As for L2VPN, it is recommended that you assign a unique RD for each VPN. Required
Configure the VPNtarget of the MPLS L2VPN Configure the Layer 2 MTU (maximum transmission unit) of the VPN
Optional. You can configure the Layer 2 MTU for the VPN. For the entire network, only one valid VPN MTU exists. If two interconnected PEs are configured with different MTUs, the smaller one is adopted. Required. Each CE created on a PE needs to uniquely correspond to one actual CE device connected to the PE. You need to specify a unique ID for these CEs. You can also specify the CE range. It is desired that the CE ID begins with 1 and increases in step of 1. Required. When planning a VPN, you can specify CE IDs for CEs beginning with 1 and increasing in step of 1, and then establish connections by CE IDs. You can establish connections with CE offset not provided for simplifying the configuration. In this case, the default CE offset is used.
1.1
MPLS L2VPN
Caution:
You can only change the CE range to a number larger than the existing one. For example, you can change a CE range from 10 to 20, rather than from 10 to 5. The only way to change a CE range to a smaller number is to remove the CE and create a new one.
You must use cards with the silk screen of CA (such as LSB2FT48CA) on the public network access side when configuring Kompella MPLS L2VPN. You can configure only one VLAN on the access side of each VPN private network. Each VLAN can have only one interface. And all the VLANs connecting to the interface must have IGMP disabled.
In Kompella MPLS L2VPN, the encapsulation type on the access side of each private network must be Ethernet.
VLAN212 PE B
CE B
1.1
MPLS L2VPN
# Configure BGP.
[Quidway] bgp 100 [Quidway-bgp] group 100 internal [Quidway-bgp] peer 100 connect-interface loopback0 [Quidway-bgp] peer 3.3.3.3 group 100 [Quidway-bgp] l2vpn-family [Quidway-bgp-af-l2vpn] peer 100 enable
1.1
MPLS L2VPN
# Enable OSPF.
[Quidway] ospf 1 router-id 1.1.1.1 [Quidway-ospf-1] area 0.0.0.0 [Quidway-ospf-1-area-0.0.0.0] network 1.1.1.1 0.0.0.0 [Quidway-ospf-1-area-0.0.0.0] network 5.5.5.0 0.0.0.255
2)
Configure PE-B.
1.1
MPLS L2VPN
# Configure BGP.
[Quidway] bgp 100 [Quidway-bgp] group 100 internal [Quidway-bgp] peer 100 connect-interface loopback0 [Quidway-bgp] peer 1.1.1.1 group 100 [Quidway-bgp] l2vpn-family [Quidway-bgp-af-l2vpn] peer 100 enable
1.1
MPLS L2VPN
# Enable OSPF.
[Quidway] ospf 1 router-id 3.3.3.3 [Quidway -ospf-1] area 0.0.0.0 [Quidway -ospf-1-area-0.0.0.0] network 3.3.3.3 0.0.0.0 [Quidway -ospf-1-area-0.0.0.0] network 6.6.6.0 0.0.0.255
3)
The configuration of P device is the same as that of standard MPLS configuration. Refer to the P router Configuration of BGP/MPLS VPN in Basic MPLS Operation Manual.
Display information about the system or about Kompella MPLS L2VPNs Enable debugging for MPLS L2VPN
debugging mpls l2vpn { all | advertisement | error | event | connections [ interface vlan-interface vlan-id ] }
1.1
MPLS L2VPN
Check to see if MPLS/BGP VPN, multicast, or VLL is enabled on the VLAN interface. Because you cannot perform Layer 2 VPN configuration on a VLAN interface if MPLS/BGP VPN, multicasting, or VLL is enabled on it.
Check to see if the VLAN is a Super-Vlan or a Sub-Vlan. You can perform the Layer 2 VPN configuration only on common VLAN interfaces.
Symptom 2: Fail to ping the peer from one end of a Martini MPLS L2VPN connection. The VC is down and the Remote value is invalid. Solution:
VC state being down indicates the encapsulation types or VC IDs of the two ends are not the same. Make sure the interface types (Access or Trunk) of the two PE interfaces and the VC IDs of the two ends are consistent.
As for the invalid Remote value, make sure you have configured the Remote parameters and the peer addresses correctly.
Symptom 3: Fail to ping the peer of a Kompella MPLS L2VPN connection. The Connection is down and the VPN value is null. Solution:
VPN value being null indicates the VPN is configured incorrectly. Make sure the VPN configurations (such as RD, RT) of the both ends are consistent, and the connection configurations of the two CEs on both ends are correct.
Connection being down indicates configurations concerning encapsulation of the two ends are not the same. Make sure the encapsulation types and MTUs configured for the local and remote PE devices are consistent. A connection fails if the encapsulation types configured on the two ends are not the same.
Symptom 4: Fail to ping the peer end of a CCC MPLS L2VPN connection. The sending and receiving channels are up, so does the linkconnection. Solution:
Make sure the in-label and out-label configured on the both ends correspond to each other. If a P device exists, make sure its forwarding connection configuration is correct, and the next hop configured statically is configured.