Operation Manual MPLS VLL. Table of Contents
|
|
- Coral Barnett
- 5 years ago
- Views:
Transcription
1 Table of Contents Table of Contents MPLS VLL Overview Concepts in MPLS VLL Introduction to MPLS VLL Packet Forwarding Implementation CCC MPLS VLL Configuration Configuring CCC MPLS VLL CCC MPLS VLL Configuration Example (1) CCC MPLS VLL Configuration Example (2) Martini MPLS VLL Configuration Configuring Martini MPLS VLL Martini MPLS VLL Configuration Example Martini MPLS VLL Primary/backup PW Configuration Example Kompella MPLS VLL Configuration Configuring Kompella MPLS VLL Kompella MPLS VLL Configuration Example (1) Kompella MPLS VLL Configuration Example (2) Displaying and Debugging MPLS VLL Troubleshooting MPLS VLL i
2 When configuring MPLS VLL, go to these sections for information you are interested in: MPLS VLL Overview CCC MPLS VLL Configuration Martini MPLS VLL Configuration Kompella MPLS VLL Configuration Displaying and Debugging MPLS VLL Troubleshooting MPLS VLL For MPLS VLL configuration examples, go to the following sections: CCC MPLS VLL Configuration Example (1) CCC MPLS VLL Configuration Example (2) Martini MPLS VLL Configuration Example Martini MPLS VLL Primary/backup PW Configuration Example Kompella MPLS VLL Configuration Example (1) Kompella MPLS VLL Configuration Example (2) Terms used in this document are listed below: Table 1-1 Terminology Term Full name AC CE FEC FR NPE PE PW PHP UPE VLL VPLS VSI LSP Attachment Circuit Customer Edge Forwarding Equivalence Class Frame Relay Network Facing PE Provider Edge Pseudowire Penultimate Hop Popping User Facing PE Virtual Leased Line Virtual Private LAN Service Virtual Switching Instance Label Switched Path 1-1
3 1.1 MPLS VLL Overview Concepts in MPLS VLL MPLS Virtual Leased Line (MPLS VLL) provides transparently transmission of Layer 2 data of users over an MPLS network. From the users perspective, this MPLS network is a Layer switched network through which Layer 2 connections can be set up between different sites. A VLL is a point-to-point virtual connection service provided in the public network. With the VLL, the two sites appear as if they were directly connected through a circuit. However a VLL cannot provide switching service among multiple points directly at the service provider Introduction to MPLS VLL MPLS VLL provides MPLS network-based Layer 2 VPN services. For users, an MPLS network is a Layer 2 switched network, through which Layer 2 connections can be established between network nodes. VPN A CE VC PE LSP PE VC CE VPN A VPN B CE P P PE CE VPN B Figure 1-2 Networking diagram of MPLS VLL MPLS VLL has the following advantages: Multiple network layer protocols supported, such as IP, IPv6, IPX, and SNA. Powerful extensibility. MPLS VLL 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 VLL to obtain and process the information, ensuring the privacy of user routes. Figure 1-3 illustrates the structure of an MPLS VLL packet. 1-2
4 Tunnel label VC label Label Stack L2 PDU Figure 1-3 Structure of an MPLS VLL packet The fields in an MPLS VLL packet are described as follows: Tunnel label (the outer label) is an MPLS label 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 VLLs implemented through circuit cross connect (CCC) do not contain this label. Data in MPLS VLL 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 Packet Forwarding In an MPLS VLL, CE, PE, and P operate in the same way as those in a BGP/MPLS VPN. That is, they also forward packets in an MPLS network transparently by using label stacks. To forward packets in an MPLS VLL, tunnels must be established first between PEs (this can be achieved by either manual configuration or signaling protocols). When the interfaces connecting PEs and CEs are up, PEs insert VC labels for packets sent by CE, and then mark them with tunnel labels. On receiving these packets, the remote PEs strip off the tunnel labels and send the packets to the corresponding CEs according to their VC labels. Figure 1-4 illustrates changes of the label stack of a packet during the forwarding. Figure 1-4 Label stack processing of MPLS VLL 1-3
5 1.1.4 Implementation At present, the official standard for MPLS VLL 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-mpls-09.txt draft-kompella-ppvpn-l2vpn-02.txt Martini draft defines the way to implement MPLS VLL 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 VLLs is known as Martini MPLS VLLs. Kompella draft defines how to establish MPLS VLLs in MPLS networks through end-to-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. Such MPLS VLLs are known as Kompella MPLS VLLs. Also, you can establish MPLS VLLs without signaling protocols. In this case, MPLS VLL services are provided through statically configured VC labels. An example of this is CCC, which implement MPLS VLLs through static configuration. Table 1-2 describes the features and implementation ways of the above three types of MPLS VLLs. Table 1-2 Features and implementation ways of the three types of MPLS VLLs VPN type Implementation Feature CCC Configures static LSPs to implement MPLS VLL. You must manually configure two LSPs (for sending and receiving packets respectively) for each CCC connection node by node (including PEs and Ps). The configured LSPs can only be used to transmit packets of the corresponding CCC connections. 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. 1-4
6 VPN type Implementation Feature Martini Kompella 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 CEs exchange VC labels through LDPs. They bind the corresponding CEs through VC-IDs. Similar to Layer 3 BGP/MPLS VPN defined in RFC2547. PEs discover Layer 2 VPN nodes automatically through IBGP sessions 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 to differentiate VPNs. Local switching like CCC is not available. An LSP can be shared by multiple VCs. 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 VLL is implemented by dividing the entire SP network into different VPNs and numbering these CEs in the VPNs. To establish a 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 for the connection by the local CE. Note: You also can configure LSPs without P devices. If a VLL-enabled port is bound with user-defined flow template, the flow template must contain a VLAN field. 1-5
7 Caution: MPLS VLL does not support NDP transparent transmission. It is not recommended to bind VLLs on the default VLAN interface. Martini VLL and Kompella VLL modes support multiport access mode, while CCC does not support this. 1.2 CCC MPLS VLL Configuration Configuring CCC MPLS VLL Follow these steps to configure CCC MPLS VLL: To do... Use the command... Remarks Enter system view system-view Configure LASR-ID mpls lsr-id ip-address Required Enable MPLS mpls Required Create the egress for the static LSP Create the ingress for the static LSP Create the transit for the static LSP static-lsp egress lsp-name l2vpn incoming-interface vlan-interface vlan-id in-label in-label static-lsp ingress lsp-name l2vpn nexthop next-hop-addr out-label out-label static-lsp transit lsp-name l2vpn incoming-interface vlan-interface vlan-id in-label in-label nexthop next-hop-addr out-label out-label 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. Quit MPLS view and enter system view quit Enable MPLS VLL mpls l2vpn Required 1-6
8 To do... Use the command... Remarks Establish local CCC connection Establish remote CCC connection ccc ccc-connection-name interface vlan-interface vlan-id out-interface vlan-interface vlan-id ccc ccc-connection-name interface vlan-interface vlan-id transmit-lsp transmit-lsp-name receive-lsp receive-lsp-name 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. Caution: In VLL, you can configure only one virtual circuit for each VLAN interface. VLL supports VLAN interfaces only. When you configure a VLL on a VLAN interface, data is encapsulated as Ethernet packets by default. You must use cards with the suffix CA (such as LSB2FT48CA) for the P devices and PE devices at the access sides of CCC public/private network. You can configure only one VLAN on the access side of each VPN private network. Each VLAN can contain only one interface, and IGMP and IGMP Snooping cannot be enabled in any of the VLANs configured on the interface. If IGMP and IGMP Snooping are enabled in some of the VLANs configured on the interface, IGMP packets cannot be transparently transmitted in the VPN. 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. CCC does not support multiport access of private network. 1-7
9 1.2.2 CCC MPLS VLL Configuration Example (1) I. Network requirements CEs and the corresponding PEs shown in Figure 1-5 are interconnected through their GigabitEthernet ports. Data is encapsulated as Ethernet packets at the data link layer. A local connection is required between CE-A and CE-B, and a remote connection between CE-A and CE-C. II. Network diagram CE B Local connection VLAN213 VLAN211 VLAN214 VLAN212 VLAN211 CE A VLAN212 PE A P PE B CE C Remote connection Figure 1-5 Network diagram for CCC MPLS VLL (1) III. Configuration procedure 1) Configure PE-A. # Enable MPLS globally. [H3C] mpls lsr-id [H3C] mpls # Enable MPLS VLL globally. [H3C] mpls l2vpn # Configure VLAN 211. [H3C] vlan 211 [H3C-vlan211] port gigabitethernet 2/1/1 [H3C-Vlan211] interface vlan-interface 211 [H3C-Vlan-interface211] quit # Configure VLAN 212. [H3C] vlan 212 [H3C-vlan212] port gigabitethernet 2/1/2 [H3C-vlan212] interface vlan-interface 212 [H3C-Vlan-interface212] quit # Configure VLAN 213. [H3C] vlan
10 [H3C-vlan213] port gigabitethernet 2/1/3 [H3C-vlan213] interface vlan-interface 213 [H3C-Vlan-interface213] quit # Enable MPLS on the interface of VLAN 214. [H3C] vlan 214 [H3C-vlan214] port gigabitethernet 2/1/4 [H3C-vlan214] quit [H3C] interface vlan-interface 214 [H3C-Vlan-interface214] ip address [H3C-Vlan-interface214] mpls [H3C-Vlan-interface214] quit # Configure the local connection. [H3C] ccc local-connection interface vlan-interface 211 out-interface vlan-interface 213 # Configure a static LSP, with the out-label of 100 and the egress interface being the interface of VLAN 214. [H3C] mpls [H3C-mpls] static-lsp ingress PEA-PEB l2vpn nexthop out-label 100 # Configure a static LSP, with the in-label of 211 and the ingress interface being the interface of VLAN 214. [H3C-mpls] static-lsp egress PEB-PEA l2vpn incoming-interface vlan-interface 214 in-label 211 # Configure the remote connection. [H3C] ccc remote-connection interface vlan-interface 212 transmit-lsp PEA-PEB receive-lsp PEB-PEA 2) Configure PE-B. # Enable MPLS globally. [H3C] mpls lsr-id [H3C] mpls # Enable MPLS VLL globally. [H3C] mpls l2vpn # Configure VLAN 211. [H3C] vlan 211 [H3C-vlan211] port gigabitethernet 2/1/1 [H3C] interface vlan-interface 211 [H3C-Vlan-interface211] quit # Enable MPLS on the interface of VLAN 212. [H3C] vlan
11 [H3C-vlan212] port gigabitethernet 2/1/2 [H3C-vlan212] quit [H3C] interface Vlan-interface 212 [H3C-Vlan-interface212] ip address [H3C-Vlan-interface212] mpls # Configure a static LSP, with the out-label of 200 and the egress interface being the interface of VLAN 212. [H3C-mpls] static-lsp ingress PEB-PEA l2vpn nexthop out-label 200 # Configure a static LSP, with the in-label of 101 and the ingress interface being the interface of VLAN 212. [H3C-mpls] static-lsp egress PEA-PEB l2vpn incoming-interface vlan-interface 212 in-label 101 # Configure the remote connection. [H3C] ccc remote-connection interface vlan-interface 211 transmit-lsp PEB-PEA receive-lsp PEA-PEB 3) Configure P. [H3C] mpls lsr-id [H3C] mpls [H3C] vlan 214 [H3C-vlan214] port gigabitethernet 2/1/1 [H3C-vlan214] quit [H3C] interface Vlan-interface 214 [H3C-Vlan-interface214] ip address [H3C-Vlan-interface214] mpls [H3C] vlan 212 [H3C-vlan212] port gigabitethernet 2/1/2 [H3C-vlan212] quit [H3C] interface Vlan-interface 212 [H3C-Vlan-interface212] ip address [H3C-Vlan-interface212] mpls # Configure a static LSP, with the in-label of 100, the ingress interface being the interface of VLAN 214, the out-label of 101, and the egress interface being the interface of VLAN 212. [H3C-mpls] static-lsp transit PEA-PEB l2vpn incoming-interface vlan-interface 214 in-label 100 nexthop out-label 101 # 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
12 [H3C-mpls] static-lsp transit PEB-PEA l2vpn incoming-interface vlan-interface 212 in-label 200 nexthop out-label 211 Caution: Following must be met to make a local CCC connection to go up: The interfaces of the two CE are physically up. The encapsulation types of the interfaces of the two CEs are the same and are supported by the MPLS VLL. For Layer 2 connections with the MPLS VLL 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 CCC MPLS VLL Configuration Example (2) I. Network requirements PE-A, PE-B, PE-C, and the P device constitute an MPLS domain. Configure a remote CCC connection between PE-A and PE-B so that CE-A1 and CE-B can communicate at Layer 2. Configure a CCC connection between PE-A and PE-C through the P device, so that CE-A2 and CE-C can communicate at Layer 2. II. Network diagram VLAN14 CE-A1 PE-A VLAN12 LSP PE-B GE3/1/1 AC VLAN14 VLAN12 VLAN 23 AC CE-B VLAN14 P LSP VLAN 23 AC CE-A2 VLAN34 VLAN34 PE-C CE-C Figure 1-6 Network diagram for CCC MPLS VLL (2) 1-11
13 III. Configuration procedure 1) Configure PE-A # Configure the LSR-ID. Enable MPLS and MPLS L2VPN. <PE-A> system-view [PE-A] mpls lsr-id [PE-A] mpls [PE-A] mpls l2vpn # Create public network VLAN 12, configure a VLAN interface, and then enable MPLS for the VLAN interface. [PE-A] vlan 12 [PE-A-vlan12] interface vlan-interface 12 [PE-A-Vlan-interface12] ip address [PE-A-Vlan-interface12] mpls [PE-A-Vlan-interface12] quit # Configure static LSPs in MPLS view. [PE-A] mpls [PE-A-mpls] static-lsp ingress A-ingress l2vpn nexthop out-label 821 [PE-A-mpls] static-lsp egress A-egress l2vpn incoming-interface Vlan-interface 12 in-label 812 [PE-A-mpls] quit # Create a private VLAN and a CCC connection. [PE-A] vlan 4012 [PE-A-vlan4012] interface vlan-interface 4012 [PE-A-Vlan-interface4012] quit [PE-A] ccc AB-connection interface Vlan-interface 4012 transmit-lsp A-ingress receive-lsp A-egress [PE-A] interface GigabitEthernet 3/1/1 [PE-A-GigabitEthernet3/1/1] port trunk permit vlan ) Configure other PE devices The configurations required on the other PE devices are similar to those on PE-A and are therefore omitted. 3) Configure the P device # Configure the LSR-ID and enable MPLS (configuration steps are omitted). # Create a public VLAN for each connected PE and assign an IP address for the VLAN interface. Then, enable MPLS and MPLS LDP on the interface. Configure a Loopback interface. Its IP address is used as the Router-ID (configuration steps are omitted). # Configure static LSP in MPLS view. 1-12
14 <P> system-view [P-mpls] static-lsp transit P l2vpn incoming-interface Vlan-interface34 in-label 843 nexthop out-label Martini MPLS VLL Configuration Configuring Martini MPLS VLL Follow these steps to configure Martini MPLS VLL: To do... Use the command... Remarks Enter system view system-view Configure the LSR-ID mpls lsr-id lsr-id Required Enable MPLS mpls Required Configure the LDP remote peer mpls ldp remote-peer index Required. Before configuring the connection, you need to enable LDP on each router and each port of the public network along the connection and configure the LDP remote peer on the peer PE. For details, refer to the LDP Configuration section in MPLS Configuration. Enable MPLS VLL mpls l2vpn Required Enter VLAN interface view or port view VLAN interface view GE/10GE port view interface vlan-interface vlan id interface GigabitEthernet interface-number 1-13
15 To do... Use the command... Remarks Required To configure a Martini MPLS VLL in VLAN interface view on a PE, you need to provide the IP address (lsr-id) of the peer PE, the VC ID, and the encapsulation type. The combination of the IP address and the VC ID must be unique on the PE. The default MTU is 1500 bytes. Create a Martini MPLS VLL virtual connection In VLAN interface view In GE/10GE port view mpls l2vc ip-address vc-id [ preferred-path peer tnl-address ] encapsulation { ethernet vlan } [ primary backup ] [ multi-port ] [ mtu mtu ] mpls l2vc ip-address vc-id [ preferred-path peer tnl-address ] vlan vlan-id encapsulation { ethernet vlan } [ mtu mtu ] To configure a Martini MPLS VLL in port view on a PE, you need to provide the IP address (lsr-id) of the peer PE, the VC ID, the PW encapsulation type, and a VLAN ID. The combination of the IP address and the VC ID must be unique on the PE, and the VLAN ID must be unique in the configuration on the same port. The default MTU is 1500 bytes. Return to system view quit Enter VLAN view Manually switch the Martini MPLS VLL virtual connection on the VLAN interface (primary or backup) interface vlan-interface vlan id mpls l2vc manual-switch [ primary backup ] Optional Return to system view quit In system view, restore the primary connections for all Martini MPLS VLL virtual connection configured In system view, enable the primary connection auto-restore function for Martini MPLS VLL virtual connections mpls l2vc manual-restore mpls l2vc auto-restore delay-time delay-time Optional Optional The auto-restore function is disabled by default. 1-14
16 To do... Use the command... Remarks Display the information about Martini MPLS VLL virtual connections display mpls l2vc [ interface { GigabitEthernet interface-number [ vlan vlan-id ] vlan-interface vlan-id } verbose ] display mpls l2vc protection [ interface vlan-interface vlan-id ] Optional Available in any view Note the following: During the Martini VLL configuration, if you specify the tunnel destination address, you must specify the 32-bit loopback address of the peer PE as the tunnel destination address; if you do not specify the tunnel destination address, the LSR-ID of the peer PE will be used as the tunnel destination address. You must use cards with the suffix CA (such as LSB2FT48CA) on the public network access sides when configuring Martini MPLS VLL; you can use cards with the suffix C or CA on the private network access side. VLL configured on a VLAN interface supports single-port or multi-port VLAN access private VLANs. If the encapsulation type is Ethernet access, the port link type for the private VLAN is Access; if the encapsulation type is VLAN access, the port link type for the private VLAN is Trunk. It is not recommended to use Hybrid as the port link type for the private VLAN. The user access mode across the PW connection must be the same. For single-port access Martini VLL configuration, there can be only one VLAN at the access side of each VPN, each VLAN can comprise only one interface, and IGMP or IGMP Snooping must not be enabled in any VLAN on this interface; if IGMP or IGMP Snooping is enabled in any VLAN on this interface, IGMP messages cannot be transparently transmitted in this VPN. Multiport access Martini VLL does not support VLANs that contain hybrid inserted cards or aggregated ports. On the same VLAN interface, the access mode of the primary and backup virtual connection must be the same, both single-port access or both multi-port access. For a multi-port access private network VLAN, the encapsulation type of all the ports in the VLAN must be the same. Currently only GE/10GE cards suffixed with CA support Martini VLL configuration in port view (XP4CA cards and WAN cards, such as ATM, E1/T1 and CPOS, do not support this configuration). Only one port is allowed at the access side of each VPN, no duplicate VLAN ID configuration is allowed on the port, and this port must belong to the VLAN in configuration. Make sure the STP is disabled on the port. The Martini VLL configuration cannot be made on a port in hybrid insertion 1-15
17 configuration or an aggregation port. Other configurations, such other VLL connections, IGMP, and IGMP snooping, cannot be made on the specified VLAN interface; otherwise these configurations will not work normally. To allow normal operation of other services configured on the VLAN interface, you need to remove the Martini VLL configuration made on the port. Currently only Martini VLLs configured on a VLAN interface support the primary/backup VC mode, while port-based Martini VLLs do not support this. LSB1XP4CA0 cards do not support the multi-port VLL feature. Interface cards configured for ACL redirection in port groups (such as XP4B) cannot be used as non-mpls intermixing cards. The MTU value set in Martini VLL configuration does not affect the actual MTU of the link. If you use the mpls l2vc manual-restore command to manually restore primary connections for the MPLS VLL virtual connections on the device, the device will automatically disable the primary connection auto-restore function. With the primary connection auto-restore function enabled on the device, you can still use the mpls l2vc manual-restore command to manually switch the MPLS VLL virtual connection on the specified VLAN interface. In this case, if the primary L2VC flapping occurs, after the primary virtual connection resumes normal, the MPLS VLL virtual connection will switch to the primary L2VC automatically Martini MPLS VLL Configuration Example I. Network requirements CEs shown in Figure 1-7 are in the same VLAN as the corresponding PEs resides in. A remote connection is required between CE-A and CE-B. II. Network diagram VLAN212 VLAN21 VLAN22 VLAN212 CE A PE A P PE B CE B Figure 1-7 Network diagram for Martini MPLS VLL III. Configuration procedure 1) Configure PE-A. # Configure the LSR-ID. Enable MPLS, LDP, and MPLS VLL. [H3C-A] mpls lsr-id [H3C-A] mpls [H3C-A-mpls] quit [H3C-A] mpls ldp [H3C-A] mpls l2vpn 1-16
18 # Configure VLAN 212. [H3C-A] vlan 212 [H3C-A-vlan212] port gigabitethernet 2/1/2 [H3C-A-vlan212]interface vlan-interface 212 [H3C-A-Vlan-interface212] quit # Configure VLAN 21. [H3C-A] vlan 21 [H3C-A-vlan21] port gigabitethernet 2/1/1 [H3C-A-vlan21] quit [H3C-A] interface Vlan-interface 21 [H3C-A-Vlan-interface21] ip address [H3C-A-Vlan-interface21] mpls [H3C-A-Vlan-interface21] mpls ldp enable # Configure an IP address for the Loopback interface, which is used as the Router ID. [H3C-A] interface loopback 0 [H3C-A-LoopBack0] ip address # Enable OSPF. [H3C-A] ospf 1 [H3C-A-ospf-1] area [H3C-A-ospf-1-area ] network [H3C-A-ospf-1-area ] network # Configure the LDP Remote Peer. [H3C-A] mpls ldp remote-peer 1 [H3C-A-remote-peer-1] remote-ip # Configure a Martini MPLS VLL connection. [H3C-A] interface vlan-interface 212 [H3C-A-Vlan-interface212] mpls l2vc encapsulation ethernet 2) Configure PE-B. # Configure the LSR-ID. Enable MPLS, MPLS LDP, and MPLS VLL. [H3C-B] mpls lsr-id [H3C-B] mpls [H3C-B-mpls] quit [H3C-B] mpls ldp [H3C-B] mpls l2vpn # Configure VLAN 22. [H3C-B] vlan 22 [H3C-B-vlan22] port gigabitethernet 2/1/1 [H3C-B-vlan22] interface Vlan-interface 22 [H3C-B-Vlan-interface22] ip address
19 [H3C-B-Vlan-interface22] mpls [H3C-B-Vlan-interface22] mpls ldp enable # Configure VLAN 212. [H3C-B] vlan 212 [H3C-B-vlan212] port gigabitethernet 2/1/2 [H3C-B-vlan212] interface vlan-interface 212 [H3C-B-Vlan-interface212] quit # Configure an IP address for the Loopback interface, which is used as the LSR-ID. [H3C-B] interface loopback 0 [H3C-B-LoopBack0] ip address # Enable OSPF. [H3C-B] ospf 1 [H3C-B-ospf-1] area [H3C-B-ospf-1-area ] network [H3C-B-ospf-1-area ] network # Configure the LDP Remote Peer. [H3C-B] mpls ldp remote-peer 1 [H3C-B-mpls-remote1] remote-ip # Configure a Martini MPLS VLL connection. [H3C-B] interface vlan-interface 212 [H3C-B-Vlan-interface212] mpls l2vc encapsulation ethernet 3) Configure P. # Configure the LSR-ID. Enable MPLS, and LDP. [H3C-P] mpls lsr-id [H3C-P] mpls [H3C-P-mpls] quit [H3C-P] mpls ldp # Configure an IP address for the Loopback interface and use it as the LSR-ID. [H3C-P] interface loopback 0 [H3C-P-LoopBack0] ip address [H3C-P-LoopBack0] quit # Configure the VLAN interface. [H3C-P] vlan 21 [H3C-P-vlan21] port gigabitethernet 2/1/1 [H3C-P-vlan21] quit [H3C-P] interface Vlan-interface 21 [H3C-P-Vlan-interface21] mpls [H3C-P-Vlan-interface21] mpls ldp enable 1-18
20 [H3C-P-Vlan-interface21] ip address [H3C-P-Vlan-interface21] quit [H3C-P] vlan 22 [H3C-P-vlan22 port gigabitethernet 2/1/2 [H3C-P-vlan22] quit [H3C-P] interface Vlan-interface 22 [H3C-P-Vlan-interface22] mpls [H3C-P-Vlan-interface22] mpls ldp enable [H3C-P-Vlan-interface22] ip address # Enable OSPF. [H3C-P] ospf 1 [H3C-P-ospf-1] area [H3C-P-ospf-1-area ] network [H3C-P-ospf-1-area ] network [H3C-P-ospf-1-area ] network Caution: Following must be met to make an LDP Layer 2 VPN to go up: The interfaces of the two CEs are physically up. Two LSP tunnels, which are opposite in direction, exist between two PEs. The encapsulation types of interfaces of the two CEs are the same and are supported by the MPLS VLL. It is recommended that the VLANs on PE A and PE B which are connected to the CEs be consistent. 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 interior gateway protocol (IGP) on each router along the path, such as OSPF Martini MPLS VLL Primary/backup PW Configuration Example I. Network requirements The CEs are connected through VLAN. A remote connection is established between PE2 and PE1, PE2 and PE3, respectively. On VLAN101, the virtual interface of PE2, configure a primary virtual connection to PE1 and a backup virtual connection to PE3. Enable manual primary/backup switchover on VLAN101. In system view, restore the connection mode to primary. 1-19
21 In system view, enable the primary connection auto-restore function. II. Network diagram CE1 G5/2/1 PE G5/1/2 VLAN30 G5/1/3 PE G5/1/13 CE3 G5/1/ G5/1/ VLAN10 VLAN70 PE2 G4/1/ VLAN50 P G5/1/2 G4/1/17 G5/1/ G5/2/ CE2 Figure 1-8 Network diagram for configuring Martini MPLS VLL primary/backup PW III. Configuration procedure 1) Configure PE1 # Configure LSR ID and enable MPLS, LDP and MPLS VLL globally. [PE1] mpls lsr-id [PE1] mpls [PE1-mpls] quit [PE1] mpls ldp [PE1] mpls l2vpn # Configure the Loopback interface address to serve as the Router ID. [PE1]interface LoopBack 0 [PE1-LoopBack0]ip address # Configure public VLAN10 and enable MPLS. [PE1] vlan 10 [PE1-vlan10] interface vlan 10 [PE1-Vlan-interface10] ip address [PE1-Vlan-interface10] mpls [PE1-Vlan-interface10] int g5/1/1 [PE1-GigabitEthernet5/1/1] port access vlan 10 # Create a static LSP from PE1 and PE2. [PE1] mpls [PE1-mpls] static-lsp ingress 1to2 destination nexthop out-label
22 [PE1-mpls] static-lsp egress 2to1 incoming-interface Vlan-interface10 in-label 3 # Configure the peer relationship with PE2 so that the LDP remote session can be established between them. [PE1] mpls ldp remote-peer 1 [PE1-mpls-remote1] remote-ip # Configure Martini MPLS VLL connection. [PE1] int g5/2/1 [PE1-GigabitEthernet5/2/1] port link-type trunk [PE1-GigabitEthernet5/2/1] port trunk permit vlan 101 [PE1-GigabitEthernet5/2/1] vlan 101 [PE1-vlan101] interface Vlan-interface 101 [PE1-Vlan-interface101] mpls l2vc encapsulation ethernet primary [PE1-Vlan-interface101] quit [PE1] 2) Configure PE2 # Configure LSR ID and enable MPLS, LDP and MPLS VLL globally. [PE2] mpls lsr-id [PE2] mpls [PE2-mpls] quit [PE2] mpls ldp [PE2] mpls l2vpn # Configure the Loopback interface address to serve as the Router ID. [PE2] interface LoopBack 0 [PE2-LoopBack0] ip address # Configure public network VLAN 10 and VLAN 50, and enable MPLS. [PE2]vlan 10 [PE2-vlan10] interface vlan 10 [PE2-Vlan-interface10] ip address [PE2-Vlan-interface10] mpls [PE2-Vlan-interface10] interface g5/1/1 [PE2-GigabitEthernet5/1/1]port access vlan 10 [PE2-GigabitEthernet5/1/1]vlan 50 [PE2-vlan50]interface vlan 50 [PE2-Vlan-interface50] ip address [PE2-Vlan-interface50] mpls [PE2-Vlan-interface50] quit [PE2] # Create a static LSP from PE2 to PE1, PE2 to PE3, respectively. 1-21
23 [PE2] mpls [PE2-mpls]static-lsp ingress pe2-pe3 destination nexthop out-label 50 [PE2-mpls]static-lsp egress pe3-pe2 incoming-interface Vlan-interface50 in-label 180 [PE2-mpls]static-lsp ingress 2to1 destination nexthop out-label 3 [PE2-mpls]static-lsp egress 1to2 incoming-interface Vlan-interface10 in-label 3 # Configure the peer relationship with PE1 and PE3 so that the LDP remote session can be established between them. [PE2] mpls ldp remote-peer 0 [PE2-mpls-remote0]remote-ip [PE2-mpls-remote0]mpls ldp remote-peer 1 [PE2-mpls-remote1]remote-ip # Configure Martini MPLS VLL connection. [PE2]interface g5/2/1 [PE2-GigabitEthernet5/2/1] port link-type trunk [PE2-GigabitEthernet5/2/1] port trunk permit vlan 101 [PE2-GigabitEthernet5/2/1] vlan 101 [PE2-vlan101]interface Vlan-interface 101 [PE2-Vlan-interface101]mpls l2vc encapsulation ethernet primary [PE2-Vlan-interface101]mpls l2vc encapsulation ethernet backup [PE2-Vlan-interface101]quit [PE2] 3) Configure PE3 # Configure LSR ID and enable MPLS, LDP and MPLS VLL globally. [PE3] mpls lsr-id [PE3] mpls [PE3-mpls] quit [PE3] mpls ldp [PE3] mpls l2vpn # Configure the Loopback interface address to serve as the Router ID. [PE3]interface LoopBack 0 [PE3-LoopBack0] ip address # Configure VLAN 70 and enable MPLS. [PE3] vlan 70 [PE3-vlan70] interface vlan 70 [PE3-Vlan-interface70] ip address [PE3-Vlan-interface70] mpls 1-22
24 [PE3-Vlan-interface70] interface g5/1/1 [PE3-GigabitEthernet5/1/1] port link-type trunk [PE3-GigabitEthernet5/1/1] port trunk permit vlan 70 # Create a static LSP from PE3 to PE2. [PE3]mpls [PE3-mpls]static-lsp egress pe2-pe3 incoming-interface Vlan-interface70 in-label 3 [PE3-mpls]static-lsp ingress pe3-pe2 destination nexthop out-label 170 # Configure the peer relationship with PE2 so that the LDP remote session can be established between them. [PE3]mpls ldp remote-peer 1 [PE3-mpls-remote1]remote-ip # Configure Martini MPLS VLL connection. [PE3]interface g5/1/13 [PE3-GigabitEthernet5/1/13] port link-type trunk [PE3-GigabitEthernet5/1/13] port trunk permit vlan 101 [PE3-GigabitEthernet5/1/13] vlan 101 [PE3-vlan101]interface Vlan-interface 101 [PE3-Vlan-interface101] mpls l2vc encapsulation ethernet [PE3-Vlan-interface101]q [PE3] 4) Configure the P device # Configure LSR ID and enable MPLS and LDP globally. [P] mpls lsr-id [P] mpls [P-mpls] quit [P] mpls ldp # Configure the Loopback interface address to serve as the Router ID. [P] interface LoopBack0 [P-LoopBack0] ip address # Configure VLAN 70 and enable MPLS. [P]vlan 70 [P-vlan70] interface vlan 70 [P-Vlan-interface70] ip address [P-Vlan-interface70] mpls [P-Vlan-interface70] interface g4/1/18 [P-GigabitEthernet 4/1/18] port link-type trunk [P-GigabitEthernet 4/1/18] port trunk permit vlan
25 [P-GigabitEthernet 4/1/18]q [P]vlan 50 [P-vlan50] interface vlan 50 [P-Vlan-interface50] ip address [P-Vlan-interface50] mpls [P-Vlan-interface50] interface g4/1/17 [P-GigabitEthernet 4/1/17] port link-type trunk [P-GigabitEthernet 4/1/17] port trunk permit vlan 50 # Configure a transit LSP from PE2 to PE3 and a transit LSP from PE3 to PE2 on the P device. [P] mpls [P-mpls] static-lsp transit pe2-pe3 incoming-interface Vlan-interface50 in-label 50 nexthop out-label 3 [P-mpls] static-lsp transit pe3-pe2 incoming-interface Vlan-interface70 in-label 170 nexthop out-label 180 5) Manually switch the primary/backup virtual connection on VLAN 101, the virtual interface of PE2. # Display the information about Martini MPLS VLL virtual connection. [PE2] display mpls l2vc interface Vlan-interface 101 Interface: Vlan-interface101 State: up, Service: VLL VC-ID: 1101, VC State: (p)up, Peer Ip Address: primary Encapsulation: vlan Group ID: Local 0, Remote 0, VC Label: Local 32768, Remote 33015, MTU:Local 1500, Remote 0 Tunnel Type: LSP, Tunnel Destination: , Tunnel Index: 31746, AC: up, LDP Session: up VC-ID: 101, VC State: (b)up, Peer Ip Address: backup Encapsulation: vlan Group ID: Local 0, Remote 0, VC Label: Local 32769, Remote 33015, MTU:Local 1500, Remote 0 Tunnel Type: LSP, Tunnel Destination: , Tunnel Index: 31744, AC: up, LDP Session: up # Switch the Martini MPLS VLL virtual connection to backup. [PE2] interface Vlan-interface 101 [PE2-Vlan-interface101] mpls l2vc manual-switch backup 1-24
26 [PE2-Vlan-interface101] quit # Restore the Martini MPLS VLL virtual connection to primary globally. [PE2] mpls l2vc manual-restore # In system view, enable the primary connection auto-restore function for Martini MPLS VLL virtual connections. [PE2] mpls l2vc auto-restore delay-time Kompella MPLS VLL Configuration Configuring Kompella MPLS VLL Follow these steps to configure Kompella MPLS VLL: To do... Use the command... Remarks Enter system view system-view Configure the LSR-ID mpls lsr-id lsr-id Required Enable MPLS mpls Required Enable MPLS VLL globally Perform BGP (border gateway protocol) related configuration. Make sure BGP operates properly and routers can discover routes to other routers. Enter VLL address family view. mpls l2vpn Refer to BGP Configuration in the IP Routing Volume. l2vpn-family Required Required In a Kompella MPLS VLL, the extended BGP is used as the signaling protocol to distribute VC labels. So, you also need to configure BGP parameters on PEs. As for the MPLS VLL itself, it has no special requirements on the BGP configuration. Note that after the reflection function is enabled in BGP view, the function is enabled on the related VLL peers. To enabled the reflection function for a VLL peer only, you can execute the undo reflect between-clients command in BGP view, through which the unicast routes received from a client are not reflected to other clients. Required 1-25
27 To do... Use the command... Remarks Activate the peer or peer group. Create a VPN and specify the encapsulation type. Configure the RD (route distinguisher) of the MPLS VLL Configure the VPN-target of the MPLS VLL Configure the Layer 2 MTU (maximum transmission unit) of the VPN peer { group-name peer-address } enable mpls l2vpn vpn-name [ encapsulation { ethernet vlan } ] route-distinguisher route-distinguisher vpn-target vpn-target-ext-comm unity [ import-extcommu nity export-extcommuni ty both ] mtu mtu 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. Required The default encapsulation type is Ethernet. In the Kompella mode, the encapsulation type of the access side of the private network can be Ethernet access and VLAN access. If you configure the encapsulation type as Ethernet access, the port link type in a private network VLAN is Access type; if you configure the encapsulation type as VLAN access, the port link type in a private network VLAN is Trunk type. It is not recommended to use Hybrid type as the port link type in a private network VLAN. The user access modes of the instance in all the peer PEs must be consistent. Required For an MPLS VLL, 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 VLL and create another one. As for VLL, it is recommended that you assign a unique RD for each VPN. Required Optional The same MTU value must be configured for all PEs in the same VPN. 1-26
28 To do... Use the command... Remarks Create a CE or modify the CE Range of an existing CE Enter an existing CE Create connections between CEs ce name [ id id [ range range ] [ default-offset offset ] ] ce name connection [ ce-offset offset ] { interface vlan-interface vlan-id [ multi-port ] } 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-27
29 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 suffix CA (such as LSB2FT48CA) on the public/private network access side when configuring Kompella MPLS VLL. VLL supports single port or multiport access private VLANs, while the Kompella VLL local connection does not support multiport access. Multiport access enabled Kompella VLL does not support VLANs with intermixing ports or aggregated ports. Only one VLAN is allowed on the access side of each VPN private network. Each VLAN can contain only one interface. IGMP and IGMP Snooping cannot be enabled in any of the VLANs configured on the interface. If IGMP and IGMP Snooping are enabled on some of the VLANs configured on the interface, IGMP packets cannot be transparently transmitted in the VPN. In Kompella MPLS VLL, the encapsulation type on the access side of each private network can be Ethernet access and VLAN access. Ethernet access is the default type. If you configure the encapsulation type as Ethernet access, the port link type in a private network VLAN is Access type; if you configure the encapsulation type as VLAN access, the port link type in a private network VLAN is Trunk type. It is not recommended to use Hybrid type as the port link type in a private network VLAN. The user access modes of the instance in all peer PEs must be consistent. In Kompella mode, VPNs are established in the entire SP network. In each VPN, a CE is assigned a CE ID, which must be unique in the VPN. In a VPN, connections cannot be established between CEs with the same CE IDs. In this case, You need to remove the configurations of the CEs with the same CE IDs and configure CE IDs for these CEs again to establish the connections. The MTU configured here has no effect on the actual MTU on the link Kompella MPLS VLL Configuration Example (1) I. Network requirements CEs shown in Figure 1-9 are in the same VLAN as the corresponding PEs resides in. A remote connection is required between CE-A and CE-B. 1-28
30 II. Network diagram VLAN212 VLAN21 VLAN22 VLAN212 CE A PE A P PE B CE B Figure 1-9 Network diagram for Kompella MPLS VLL (1) III. Configuration procedure 1) Configure PE-A. # Enable MPLS globally. [H3C] mpls lsr-id [H3C] mpls [H3C-mpls] quit [H3C] mpls ldp # Configure an IP address for the Loopback interface. [H3C] interface loopback 0 [H3C-LoopBack0] ip address # Enable MPLS VLL globally. [H3C] mpls l2vpn # Configure VLAN 212. [H3C] vlan 212 [H3C-vlan212] port gigabitethernet 2/1/2 [H3C-vlan212] interface vlan-interface 212 [H3C-Vlan-interface212] quit # Enable MPLS on the interface of VLAN 21. [H3C] vlan 21 [H3C-vlan21] port gigabitethernet 2/1/4 [H3C-vlan21] quit [H3C] interface vlan-interface 21 [H3C-Vlan-interface21] ip address [H3C-Vlan-interface21] mpls [H3C-Vlan-interface21] mpls ldp enable [H3C-Vlan-interface21] mpls ldp transport-ip interface [H3C-Vlan-interface21] quit # Configure BGP. [H3C] bgp 100 [H3C-bgp] group 100 internal [H3C-bgp] peer 100 connect-interface loopback0 [H3C-bgp] peer group
31 [H3C-bgp] l2vpn-family [H3C-bgp-af-l2vpn] peer 100 enable # Create and configure the VPN. [H3C] mpls l2vpn vpn1 encapsulation ethernet [H3C-mpls-l2vpn-vpn1] route-distinguisher 100:1 [H3C-mpls-l2vpn-vpn1] vpn-target 100:1 # Create CE1 and configure the corresponding connection. [H3C-mpls-l2vpn-vpn1] ce ce1 id 1 range 200 [H3C-mpls-l2vpn-vpn1-ce1] connection ce-offset 2 interface vlan-interface 212 [H3C-mpls-l2vpn-vpn1-ce1] quit # Enable OSPF. [H3C] ospf 1 router-id [H3C-ospf-1] area [H3C-ospf-1-area ] network [H3C-ospf-1-area ] network ) Configure PE-B. # Enable MPLS globally. [H3C] mpls lsr-id [H3C] mpls [H3C-mpls] quit [H3C] mpls ldp # Configure an IP address for the Loopback interface. [H3C] interface loopback 0 [H3C-LoopBack0] ip address # Enable MPLS VLL globally. [H3C] mpls l2vpn # Configure VLAN 212. [H3C] vlan 212 [H3C-vlan212] port gigabitethernet 2/1/2 [H3C-vlan212] interface vlan-interface 212 [H3C-Vlan-interface 212] quit # Enable MPLS on the interface of VLAN 22. [H3C] vlan 22 [H3C-vlan22] port gigabitethernet 2/1/4 [H3C-vlan22] quit [H3C] interface vlan-interface 22 [H3C-Vlan-interface22] ip address [H3C-Vlan-interface22] mpls 1-30
32 [H3C-Vlan-interface22] mpls ldp enable [H3C-Vlan-interface22] mpls ldp transport-ip interface [H3C-Vlan-interface22] quit # Configure BGP. [H3C] bgp 100 [H3C-bgp] group 100 internal [H3C-bgp] peer 100 connect-interface loopback0 [H3C-bgp] peer group 100 [H3C-bgp] l2vpn-family [H3C-bgp-af-l2vpn] peer 100 enable # Create and configure VPN1. [H3C] mpls l2vpn vpn1 encapsulation ethernet [H3C-mpls-l2vpn-vpn1] route-distinguisher 100:1 [H3C-mpls-l2vpn-vpn1] vpn-target 100:1 # Create CE2 and configure the corresponding connection. [H3C-mpls-l2vpn-vpn1] ce ce2 id 2 range 200 [H3C-mpls-l2vpn-vpn1-ce2] connection ce-offset 1 interface vlan-interface 212 [H3C-mpls-l2vpn-vpn1-ce2] quit # Enable OSPF. [H3C] ospf 1 router-id [H3C -ospf-1] area [H3C -ospf-1-area ] network [H3C -ospf-1-area ] network ) Configure the P device. The configuration of P device is the same as that of standard MPLS configuration. Refer to the P Router Configuration section of BGP/MPLS VPN. Note that the VLANs on PE A and PE B which are connected to the CEs must be consistent Kompella MPLS VLL Configuration Example (2) I. Network requirements PE-A, PE-B, PE-C, and the P device constitute an MPLS domain. Configure Kompella MPLS L2VPNs on PE-A, PE-B, and PE-C, and specify the CE range to 10. Set up Kompella MPLS VLL connections between PE-A and PE-B and between PE-A and PE-C. Configure CE-A1 and CE-B to communicate at Layer 2, and CE-A2 and CE-C to communicate at Layer
33 II. Network diagram Figure 1-10 Network diagram for Kompella MPLS VLL (2) III. Configuration procedure 1) Configure PE-A. # Configure LSR ID and enable MPLS and LDP. <PE-A> system-view [PE-A] mpls lsr-id [PE-A] mpls [PE-A] mpls ldp # Create public network VLAN 12, configure a VLAN interface, and then enable MPLS and MPLS LDP for the VLAN interface. [PE-A] vlan 12 [PE-A-vlan12] interface vlan-interface 12 [PE-A-Vlan-interface12] ip address [PE-A-Vlan-interface12] mpls [PE-A-Vlan-interface12] mpls ldp enable [PE-A-Vlan-interface12] quit # Configure a Loopback interface. Its IP address is used as the Router-ID and LSR-ID. [PE-A] interface LoopBack 0 [PE-A-LoopBack0] ip address [PE-A-LoopBack0] quit # Enable OSPF and advertise the routes of the interfaces. [PE-A] ospf [PE-A-ospf-1] area 0 [PE-A-ospf-1-area ] network [PE-A-ospf-1-area ] network [PE-A-ospf-1-area ] network
34 [PE-A-ospf-1-area ] quit # Enable BGP and configure the BGP peer relationship with PE-B and PE-C, using the loopback interface as the source interface. [PE-A] bgp 100 [PE-A-bgp] group ibgp internal [PE-A-bgp] peer group ibgp [PE-A-bgp] peer connect-interface LoopBack0 [PE-A-bgp] peer group ibgp [PE-A-bgp] peer connect-interface LoopBack0 # Enable the peer group to exchange BGP routing information. [PE-A-bgp] l2vpn-family [PE-A-bgp-af-l2vpn] peer ibgp enable [PE-A-bgp-af-l2vpn] quit # Enable MPLS L2VPN. [PE-A] mpls l2vpn # Configure a private VLAN, and enter its VLAN interface view. [PE-A] vlan-vpn [PE-A] vlan 4000 [PE-A-vlan4000] interface vlan-interface 4000 [PE-A-Vlan-interface4000] quit # Create a Kompella MPLS L2VPN, specifying the encapsulation type as VLAN. Then specify the RD and RT. [PE-A] mpls l2vpn k4000 encapsulation vlan [PE-A-mpls-l2vpn-k4000] route-distinguisher 100:4000 [PE-A-mpls-l2vpn-k4000] vpn-target 100:4000 # Create a CE and configure the corresponding connection. [PE-A-mpls-l2vpn-k4000] ce PE-A id 1 range 10 [PE-A-mpls-l2vpn-ce-k4000-PE-A] connection ce-offset 1 interface Vlan-interface ) Configure the other PE devices. The configurations required on the other PE devices are similar to those on PE-A and are therefore omitted. 3) Configure the P device. The following gives only the configurations required on the P device. The detailed configuration steps are omitted. Configure the LSR-ID, and enable MPLS and MPLS LDP. Create a public VLAN and assign an IP address for the VLAN interface. Then, enable MPLS and MPLS LDP on the interface. 1-33
35 Configure a Loopback interface. Its IP address is used as the Router-ID. Enable OSPF and advertise the routes of the interfaces. 1.5 Displaying and Debugging MPLS VLL To do... Use the command... Remarks Display information about a CCC MPLS VLL connection Display information about a Martini MPLS VLL connection Display information about a Kompella MPLS VLL connection Enable debugging for MPLS VLL display ccc [ ccc-name type [ local remote ] ] display mpls l2vc [ interface { GigabitEthernet interface-number [ vlan vlan-id ] vlan-interface vlan-id } verbose] display mpls l2vc protection [ interface vlan-interface vlan-id ] display mpls l2vpn [ vsi-name [ local-ce remote-ce ] connection [ vsi-name [ down remote-ce up verbose ] brief interface vlan-interface vlan-id ] forwarding-info { vc-label interface vlan-interface vlan-id } ] display bgp l2vpn { all peer route-distinguisher ASN } debugging mpls l2vpn { advertisement all connections [ interface vlan-interface vlan-id ] error event loadshare switchover } Available in any view Available in user view 1.6 Troubleshooting MPLS VLL Symptom 1: Fail to configure Layer 2 VPN on the VLAN interface. Solution: 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 VLL connection. The VC is down and the Remote value is invalid. Solution: 1-34
Configuring MPLS L2VPN
Contents Configuring MPLS L2VPN 1 MPLS L2VPN overview 1 Basic concepts of MPLS L2VPN 2 Implementation of MPLS L2VPN 2 MPLS L2VPN configuration task list 4 Configuring MPLS L2VPN 5 Configuring CCC MPLS
More informationConfiguring MPLS L2VPN
Contents Configuring MPLS L2VPN 1 MPLS L2VPN overview 1 About MPLS L2VPN 1 Comparison with traditional VPN 2 Comparison with MPLS L3VPN 2 Basic concepts 2 MPLS L2VPN implementation 3 MPLS L2VPN configuration
More informationConfiguring MPLS L2VPN
Contents Configuring MPLS L2VPN 1 Overview 1 Comparison with traditional VPN 1 Comparison with MPLS L3VPN 2 Basic concepts 2 MPLS L2VPN implementation 3 MPLS L2VPN configuration task list 4 Configuring
More informationConfiguring VPLS. VPLS overview. Operation of VPLS. Basic VPLS concepts
Contents Configuring VPLS 1 VPLS overview 1 Operation of VPLS 1 VPLS packet encapsulation 4 H-VPLS implementation 5 Hub-spoke VPLS implementation 7 Multi-hop PW 8 VPLS configuration task list 9 Enabling
More informationTable of Contents Chapter 1 MPLS L3VPN Configuration
Table of Contents Table of Contents... 1-1 1.1 MPLS L3VPN Overview... 1-1 1.1.1 MPLS L3VPN Model... 1-2 1.1.2 MPLS L3VPN Implementation... 1-5 1.1.3 Nested MPLS L3VPN Implementation... 1-7 1.1.4 Hierarchical
More informationHP A5820X & A5800 Switch Series MPLS. Configuration Guide. Abstract
HP A5820X & A5800 Switch Series MPLS Configuration Guide Abstract This document describes the software features for the HP 5820X & 5800 Series products and guides you through the software configuration
More informationLARGE SCALE IP ROUTING LECTURE BY SEBASTIAN GRAF
LARGE SCALE IP ROUTING LECTURE BY SEBASTIAN GRAF MODULE 07 - MPLS BASED LAYER 2 SERVICES 1 by Xantaro MPLS BASED LAYER 2 VPNS USING MPLS FOR POINT-TO-POINT LAYER 2 SERVICES 2 by Xantaro Why are Layer-2
More informationOperation Manual MCE H3C S3610&S5510 Series Ethernet Switches. Table of Contents
Table of Contents Table of Contents Chapter 1 MCE Overview... 1-1 1.1 MCE Overview... 1-1 1.1.1 Introduction to BGP/MPLS VPN... 1-1 1.1.2 BGP/MPLS VPN Concepts... 1-2 1.1.3 Introduction to MCE... 1-5 1.1.4
More informationTable of Contents 1 Multicast VPN Configuration 1-1
Table of Contents 1 Multicast VPN Configuration 1-1 Multicast VPN Overview 1-1 Introduction to MPLS L3VPN 1-1 Introduction to Multicast VPN 1-2 Introduction to MD-VPN 1-4 Protocols and Standards 1-7 How
More informationQuidway S5700 Series Ethernet Switches V100R006C01. Configuration Guide - VPN. Issue 01 Date HUAWEI TECHNOLOGIES CO., LTD.
V100R006C01 Issue 01 Date 2011-11-21 HUAWEI TECHNOLOGIES CO., LTD. 2011. All rights reserved. No part of this document may be reproduced or transmitted in any form or by any means without prior written
More informationHP 5920 & 5900 Switch Series
HP 5920 & 5900 Switch Series MCE Configuration Guide Part number: 5998-2896 Software version: Release2207 Document version: 6W100-20121130 Legal and notice information Copyright 2012 Hewlett-Packard Development
More informationVPLS configuration commands
Contents VPLS configuration commands 1 bandwidth 1 broadcast-restrain 1 description 2 display bgp vpls 3 display l2vpn fast-switch-group 8 display mac-address vsi 9 display mpls l2vpn fib ac vpls 10 display
More informationConfiguring multicast VPN
Contents Configuring multicast VPN 1 Multicast VPN overview 1 Multicast VPN overview 1 MD-VPN overview 3 Protocols and standards 6 How MD-VPN works 6 Share-MDT establishment 6 Share-MDT-based delivery
More informationContents. EVPN overview 1
Contents EVPN overview 1 EVPN network model 1 MP-BGP extension for EVPN 2 Configuration automation 3 Assignment of traffic to VXLANs 3 Traffic from the local site to a remote site 3 Traffic from a remote
More informationVPLS configuration commands
Contents VPLS configuration commands 1 car 1 description 1 display bgp vpls 2 display l2vpn fast-switch-group 7 display mac-address vsi 8 display mpls l2vpn fib ac vpls 10 display mpls l2vpn fib pw vpls
More informationVPLS configuration commands
Contents VPLS configuration commands 1 car 1 description 1 display bgp vpls 2 display l2vpn fast-switch-group 7 display mac-address vsi 8 display mpls l2vpn fib ac vpls 9 display mpls l2vpn fib pw vpls
More informationHP FlexFabric 7900 Switch Series
HP FlexFabric 7900 Switch Series MCE Configuration Guide Part number: 5998-6188 Software version: Release 2117 and Release 2118 Document version: 6W100-20140805 Legal and notice information Copyright 2014
More informationL2 MPLS VPN (VPLS) Technology White Paper
S9500 L2 MPLS VPN (VPLS) Technology White Paper L2 MPLS VPN (VPLS) Technology White Paper Keywords: MPLS, VPLS Abstract: MPLS technologies make it very easy to provide VPN services based on IP technologies
More informationHP FlexFabric 5930 Switch Series
HP FlexFabric 5930 Switch Series MCE Configuration Guide Part number: 5998-4625 Software version: Release 2406 & Release 2407P01 Document version: 6W101-20140404 Legal and notice information Copyright
More informationH3C S10500 Switch Series
H3C S10500 Switch Series MPLS Configuration Guide Hangzhou H3C Technologies Co., Ltd. http://www.h3c.com Software version: Release 1126 and Later Document version: 20111130-C-1.01 Copyright 2011, Hangzhou
More informationMPLS VPN Carrier Supporting Carrier Using LDP and an IGP
MPLS VPN Carrier Supporting Carrier Using LDP and an IGP Multiprotocol Label Switching (MPLS) Virtual Private Network (VPN) Carrier Supporting Carrier (CSC) enables one MPLS VPN-based service provider
More informationMPLS VPN Carrier Supporting Carrier Using LDP and an IGP
MPLS VPN Carrier Supporting Carrier Using LDP and an IGP Last Updated: December 14, 2011 Multiprotocol Label Switching (MPLS) Virtual Private Network (VPN) Carrier Supporting Carrier (CSC) enables one
More informationConfiguring MPLS L3VPN
Contents Configuring MPLS L3VPN 1 MPLS L3VPN overview 1 MPLS L3VPN concepts 2 MPLS L3VPN packet forwarding 4 MPLS L3VPN networking schemes 5 MPLS L3VPN routing information advertisement 8 Inter-AS VPN
More informationMPLS design. Massimiliano Sbaraglia
MPLS design Massimiliano Sbaraglia - MPLS layer 2 VPN diagram flowchart - MPLS layer 2 VPN pseudowire VPWS diagram - MPLS layer 2 VPN VPLS diagram - MPLS layer 2 EVPN diagram - MPLS layer 3 VPN diagram
More informationNetwork Configuration Example
Network Configuration Example Interconnecting a Layer 2 Circuit with a Layer 3 VPN Modified: 2017-01-19 Juniper Networks, Inc. 1133 Innovation Way Sunnyvale, California 94089 USA 408-745-2000 www.juniper.net
More informationHP Routing Switch Series
HP 12500 Routing Switch Series MPLS Configuration Guide Part number: 5998-3414 Software version: 12500-CMW710-R7128 Document version: 6W710-20121130 Legal and notice information Copyright 2012 Hewlett-Packard
More informationHP A-MSR Router Series MPLS. Configuration Guide. Abstract
HP A-MSR Router Series MPLS Configuration Guide Abstract This document describes the software features for the HP A Series products and guides you through the software configuration procedures. These configuration
More informationConfiguring Virtual Private LAN Services
Virtual Private LAN Services (VPLS) enables enterprises to link together their Ethernet-based LANs from multiple sites via the infrastructure provided by their service provider. This module explains VPLS
More informationDeploy VPLS. APNIC Technical Workshop October 23 to 25, Selangor, Malaysia Hosted by:
Deploy VPLS APNIC Technical Workshop October 23 to 25, 2017. Selangor, Malaysia Hosted by: Issue Date: [201609] Revision: [01] Acknowledgement Cisco Systems 2 VPLS Overview 3 Virtual Private LAN Service
More informationModule 11a MPLS VPWS Configuration Lab (LDP)
APNIC MPLS Workshop Lab Module 11a MPLS VPWS Configuration Lab (LDP) Objective: All the routers are pre-configured with basic interface, OSPF, BGP, MPLS Label Distribution Protocol (LDP) configuration
More informationConfiguring Virtual Private LAN Service (VPLS) and VPLS BGP-Based Autodiscovery
Configuring Virtual Private LAN Service (VPLS) and VPLS BGP-Based Autodiscovery Finding Feature Information, page 1 Configuring VPLS, page 1 Configuring VPLS BGP-based Autodiscovery, page 17 Finding Feature
More informationTable of Contents Chapter 1 Tunneling Configuration
Table of Contents Table of Contents... 1-1 1.1 Introduction to Tunneling... 1-1 1.1.1 IPv6 over IPv4 Tunnel... 1-2 1.1.2 IPv4 over IPv4 Tunnel... 1-7 1.2 Tunneling Configuration Task List... 1-8 1.3 Configuring
More informationConfiguring MPLS and EoMPLS
37 CHAPTER This chapter describes how to configure multiprotocol label switching (MPLS) and Ethernet over MPLS (EoMPLS) on the Catalyst 3750 Metro switch. MPLS is a packet-switching technology that integrates
More informationHP MSR Router Series. MPLS Configuration Guide(V5) Part number: Software version: CMW520-R2513 Document version: 6PW
HP MSR Router Series MPLS Configuration Guide(V5) Part number: 5998-8188 Software version: CMW520-R2513 Document version: 6PW106-20150808 Legal and notice information Copyright 2015 Hewlett-Packard Development
More informationMPLS VPN Carrier Supporting Carrier IPv4 BGP Label Distribution
MPLS VPN Carrier Supporting Carrier IPv4 BGP Label Distribution This feature lets you configure your carrier supporting carrier network to enable Border Gateway Protocol (BGP) to transport routes and Multiprotocol
More informationMPLS VPN. 5 ian 2010
MPLS VPN 5 ian 2010 What this lecture is about: IP CEF MPLS architecture What is MPLS? MPLS labels Packet forwarding in MPLS MPLS VPNs 3 IP CEF & MPLS Overview How does a router forward packets? Process
More informationConfiguring MPLS L3VPN
Contents Configuring MPLS L3VPN 1 MPLS L3VPN overview 1 Introduction to MPLS L3VPN 1 MPLS L3VPN concepts 2 MPLS L3VPN packet forwarding 5 MPLS L3VPN networking schemes 5 MPLS L3VPN routing information
More informationModule 11b MPLS VPLS Configuration Lab (LDP Manual)
APNIC MPLS Workshop Lab Module 11b MPLS VPLS Configuration Lab (LDP Manual) Objective: All the routers are pre-configured with basic interface, OSPF, BGP, MPLS Label Distribution Protocol (LDP) configuration
More informationComputer Network Architectures and Multimedia. Guy Leduc. Chapter 2 MPLS networks. Chapter 2: MPLS
Computer Network Architectures and Multimedia Guy Leduc Chapter 2 MPLS networks Chapter based on Section 5.5 of Computer Networking: A Top Down Approach, 6 th edition. Jim Kurose, Keith Ross Addison-Wesley,
More informationHP 5920 & 5900 Switch Series
HP 5920 & 5900 Switch Series MPLS Configuration Guide Part number: 5998-4676a Software version: Release 23xx Document version: 6W101-20150320 Legal and notice information Copyright 2015 Hewlett-Packard
More informationMPLS VPN over mgre. Finding Feature Information. Last Updated: November 1, 2012
MPLS VPN over mgre Last Updated: November 1, 2012 The MPLS VPN over mgre feature overcomes the requirement that a carrier support multiprotocol label switching (MPLS) by allowing you to provide MPLS connectivity
More informationConfigure L2VPN Autodiscovery and Signaling
This chapter describes the L2VPN Autodiscovery and Signaling feature which enables the discovery of remote Provider Edge (PE) routers and the associated signaling in order to provision the pseudowires.
More informationMPLS VPN Carrier Supporting Carrier IPv4 BGP Label Distribution
MPLS VPN Carrier Supporting Carrier IPv4 BGP Label Distribution This feature enables you to configure your carrier supporting carrier network to enable Border Gateway Protocol (BGP) to transport routes
More informationMPLS VPN--Inter-AS Option AB
The feature combines the best functionality of an Inter-AS Option (10) A and Inter-AS Option (10) B network to allow a Multiprotocol Label Switching (MPLS) Virtual Private Network (VPN) service provider
More informationTopexam. 一番権威的な IT 認定試験ウェブサイト 最も新たな国際 IT 認定試験問題集
Topexam 一番権威的な IT 認定試験ウェブサイト http://www.topexam.jp 最も新たな国際 IT 認定試験問題集 Exam : HP0-Y36 Title : Deploying HP Enterprise Networks Vendors : HP Version : DEMO Get Latest & Valid HP0-Y36 Exam's Question and
More informationVPLS Autodiscovery: BGP Based
First Published: February 19, 2007 Last Updated: February 19, 2007 VPLS Autodiscovery enables each Virtual Private LAN Service (VPLS) provider edge (PE) router to discover which other PE routers are part
More informationPractice exam questions for the Nokia NRS II Composite Exam
Practice exam questions for the Nokia NRS II Composite Exam The following questions will test your knowledge and prepare you for the Nokia NRS II Composite Exam. Compare your responses with the Answer
More informationSecurizarea Calculatoarelor și a Rețelelor 32. Tehnologia MPLS VPN
Platformă de e-learning și curriculă e-content pentru învățământul superior tehnic Securizarea Calculatoarelor și a Rețelelor 32. Tehnologia MPLS VPN MPLS VPN 5-ian-2010 What this lecture is about: IP
More informationTable of Contents Chapter 1 MPLS Basics Configuration
Table of Contents Table of Contents... 1-1 1.1 MPLS Overview... 1-1 1.1.1 Basic Concepts of MPLS... 1-2 1.1.2 Architecture of MPLS... 1-5 1.1.3 MPLS and Routing Protocols... 1-7 1.1.4 Applications of MPLS...
More informationIPv6 Switching: Provider Edge Router over MPLS
Multiprotocol Label Switching (MPLS) is deployed by many service providers in their IPv4 networks. Service providers want to introduce IPv6 services to their customers, but changes to their existing IPv4
More informationMPLS VPN Inter-AS Option AB
First Published: December 17, 2007 Last Updated: September 21, 2011 The feature combines the best functionality of an Inter-AS Option (10) A and Inter-AS Option (10) B network to allow a Multiprotocol
More informationLARGE SCALE IP ROUTING LECTURE BY SEBASTIAN GRAF
LARGE SCALE IP ROUTING LECTURE BY SEBASTIAN GRAF MODULE 05 MULTIPROTOCOL LABEL SWITCHING (MPLS) AND LABEL DISTRIBUTION PROTOCOL (LDP) 1 by Xantaro IP Routing In IP networks, each router makes an independent
More informationMPLS VPN Multipath Support for Inter-AS VPNs
The feature supports Virtual Private Network (VPN)v4 multipath for Autonomous System Boundary Routers (ASBRs) in the interautonomous system (Inter-AS) Multiprotocol Label Switching (MPLS) VPN environment.
More informationHP FlexFabric Switch Series
HP FlexFabric 12900 Switch Series MPLS Command Reference Part number: 5998-7274 Software version: R103x Document version: 6W100-20150116 Legal and notice information Copyright 2015 Hewlett-Packard Development
More informationImplementing Virtual Private LAN Services
Implementing Virtual Private LAN Services This module provides the conceptual and configuration infmation f Virtual Private LAN Services (VPLS) on Cisco IOS XR software. VPLS suppts Layer 2 VPN technology
More informationIPv6 Switching: Provider Edge Router over MPLS
Multiprotocol Label Switching (MPLS) is deployed by many service providers in their IPv4 networks. Service providers want to introduce IPv6 services to their customers, but changes to their existing IPv4
More informationH3C S10500 Switch Series
H3C S10500 Switch Series MPLS Configuration Guide Hangzhou H3C Technologies Co., Ltd. http://www.h3c.com Software version: Release 1201 and Later Document version: 6W101-20120903 Copyright 2012, Hangzhou
More informationDeploy MPLS L3 VPN. APNIC Technical Workshop October 23 to 25, Selangor, Malaysia Hosted by:
Deploy MPLS L3 VPN APNIC Technical Workshop October 23 to 25, 2017. Selangor, Malaysia Hosted by: Issue Date: [201609] Revision: [01] Acknowledgement Cisco Systems Course Outline MPLS L3 VPN Models L3
More informationLab 1: Static MPLS LSP-RTX4-RTX1 LSP-RTX1-RTX4 LSP-RTX3-RTX2 LSP-RTX2-RTX3
Lab 1: Static MPLS First lab gives a basic understanding of MPLS label swapping No signaling manually assign labels like static routing Understand configuration, forwarding tables, and debugging of MPLS
More informationH3C SR6600 Routers. MPLS Configuration Guide. Hangzhou H3C Technologies Co., Ltd.
H3C SR6600 Routers MPLS Configuration Guide Hangzhou H3C Technologies Co., Ltd. http://www.h3c.com Document Version: 20100930-C-1.08 Product Version: SR6600-CMW520-R2420 Copyright 2007-2010, Hangzhou H3C
More informationConfigure Multipoint Layer 2 Services
This module provides the conceptual and configuration information for Multipoint Layer 2 Bridging Services, also called Virtual Private LAN Services (VPLS). Note VPLS supports Layer 2 VPN technology and
More informationAlcatel-Lucent 4A Alcatel-Lucent Services Architecture.
Alcatel-Lucent 4A0-104 Alcatel-Lucent Services Architecture http://killexams.com/exam-detail/4a0-104 A. Service tunnels are unidirectional. B. Transport tunnels are unidirectional. C. A service will use
More informationDeploying MPLS L2VPN
Deploying MPLS L2VPN Nurul Islam Roman (nurul@apnic.net) 1 Abstract This session covers the fundamental and advanced topics associated with the deployment of Layer 2 VPNs over an MPLS network. The material
More informationПрименение MPLS в сетях связи. (Часть 2)
Применение MPLS в сетях связи. (Часть 2) Дополнительные главы Компьютерных сетей и телекоммуникаций. Васин В.В. CCIE, ECE, CCSI MPLS VPN Technology Introducing VPNs Traditional Router-Based Networks Traditional
More informationMulti Protocol Label Switching (an introduction) Karst Koymans. Thursday, March 12, 2015
.. MPLS Multi Protocol Label Switching (an introduction) Karst Koymans Informatics Institute University of Amsterdam (version 4.3, 2015/03/09 13:07:57) Thursday, March 12, 2015 Karst Koymans (UvA) MPLS
More informationMulti-VRF Support. Finding Feature Information. Prerequisites for Multi-VRF Support
The feature allows you to configure and maintain more than one instance of a routing and forwarding table within the same customer edge (CE) device. Finding Feature Information, page 1 Prerequisites for,
More informationCisco. Maintaining Cisco Service Provider VPNs and MPLS Networks (MSPVM)
Cisco 642-780 Maintaining Cisco Service Provider VPNs and MPLS Networks (MSPVM) Download Full Version : http://killexams.com/pass4sure/exam-detail/642-780 QUESTION: 56 Which command should be used to verify
More informationVendor: HP. Exam Code: HP0-Y36. Exam Name: Deploying HP Enterprise Networks. Version: Demo
Vendor: HP Exam Code: HP0-Y36 Exam Name: Deploying HP Enterprise Networks Version: Demo QUESTION NO: 1 A provider of MPLS services configures MPLS Layer-3 VPN services for two customers. Each customer
More informationBasic MPLS commands. display mpls forwarding ilm. Syntax. Views. Predefined user roles. Parameters. Usage guidelines. Examples
Contents Basic MPLS commands 1 display mpls forwarding ilm 1 display mpls forwarding nhlfe 2 display mpls interface 4 display mpls label 5 display mpls lsp 6 display mpls lsp statistics 10 display mpls
More informationNetwork Configuration Example
Network Configuration Example Configuring BGP Autodiscovery for LDP VPLS Release NCE0035 Modified: 2017-01-24 Juniper Networks, Inc. 1133 Innovation Way Sunnyvale, California 94089 USA 408-745-2000 www.juniper.net
More informationInternet Engineering Task Force (IETF) Request for Comments: Alcatel-Lucent W. Luo January 2011
Internet Engineering Task Force (IETF) Request for Comments: 6074 Category: Standards Track ISSN: 2070-1721 E. Rosen B. Davie Cisco Systems, Inc. V. Radoaca Alcatel-Lucent W. Luo January 2011 Provisioning,
More informationMPLS VPN C H A P T E R S U P P L E M E N T. BGP Advertising IPv4 Prefixes with a Label
7 C H A P T E R S U P P L E M E N T This online supplement of Chapter 7 focuses on two important developments. The first one is Inter-Autonomous. Inter-Autonomous is a concept whereby two service provider
More informationCCIE R&S Techtorial MPLS
CCIE R&S Techtorial MPLS Ing. Tomáš Kelemen Partner Systems Engineer CCIE #24395 Ing. Peter Mesjar Systems Engineer CCIE #17428 2011 Cisco Systems, Inc. All rights reserved. 1 Agenda Introduction to MPLS
More informationConfiguring MPLS, MPLS VPN, MPLS OAM, and EoMPLS
CHAPTER 43 Configuring MPLS, MPLS VPN, MPLS OAM, and EoMPLS This chapter describes how to configure multiprotocol label switching (MPLS) and Ethernet over MPLS (EoMPLS) on the Cisco ME 3800X and ME 3600X
More informationL2 VPNs. Javed Asghar Muhammad Waris Sagheer 2005, Cisco Systems, Inc. All rights reserved.
L2 VPNs Javed Asghar jasghar@cisco.com Muhammad Waris Sagheer waris@cisco.com 2005, Cisco Systems, Inc. All rights reserved. 1 Agenda! Topics:! L2VPN Introduction! L2VPN Models! Quality of Service! L2VPN
More informationHPE FlexFabric 5940 Switch Series
HPE FlexFabric 5940 Switch Series EVPN Configuration Guide Part number: 5200-2002b Software version: Release 25xx Document version: 6W102-20170830 Copyright 2017 Hewlett Packard Enterprise Development
More informationOperation Manual MPLS. Table of Contents
Table of Contents Table of Contents Chapter 1 MPLS Architecture... 1-1 1.1 MPLS Overview... 1-1 1.2 MPLS Basic Concepts... 1-1 1.2.1 FEC... 1-1 1.2.2 Label... 1-1 1.2.3 LDP... 1-3 1.3 MPLS Architecture...
More informationEVPN Virtual Private Wire Service (VPWS) Single Homed
EVPN Virtual Private Wire Service (VPWS) Single Homed Effective Release Cisco IOS XE 3.18, this feature is now supported on Cisco ASR 920 Series Aggregation Services Router, EVPN-VPWS single homed is a
More informationConfiguring basic MBGP
Contents Configuring MBGP 1 MBGP overview 1 Protocols and standards 1 MBGP configuration task list 1 Configuring basic MBGP 2 Controlling route advertisement and reception 2 Configuration prerequisites
More informationNetwork Configuration Example
Network Configuration Example Layer 2 Circuits Modified: 2017-01-19 Juniper Networks, Inc. 1133 Innovation Way Sunnyvale, California 94089 USA 408-745-2000 www.juniper.net All rights reserved. Juniper
More informationEVPN Virtual Private Wire Service (VPWS) Single Homed
EVPN Virtual Private Wire Service (VPWS) Single Homed EVPN-VPWS single homed is a BGP control plane solution for point-to-point services. It has the ability to forward traffic from or to one network to
More informationWAN Edge MPLSoL2 Service
4 CHAPTER While Layer 3 VPN services are becoming increasing popular as a primary connection for the WAN, there are a much larger percentage of customers still using Layer 2 services such Frame-Relay (FR).
More informationMultiprotocol Label Switching Virtual Private Network
Anas Al-Selwi Multiprotocol Label Switching Virtual Private Network Helsinki Metropolia University of Applied Sciences Bachelor of Engineering Information Technology Thesis 08 May 2013 Abstract Author(s)
More informationHP MSR Router Series. MPLS Configuration Guide(V7) Part number: Software version: CMW710-R0106 Document version: 6PW
HP MSR Router Series MPLS Configuration Guide(V7) Part number: 5998-5680 Software version: CMW710-R0106 Document version: 6PW100-20140607 Legal and notice information Copyright 2014 Hewlett-Packard Development
More informationIntroduction to Multi-Protocol Label
Introduction to Multi-Protocol Label Switching (MPLS) Matthew Bocci, Alcatel-Lucent IP Division Agenda History of MPLS Standardisation MPLS Architecture Control Plane QoS and Traffic Engineering Protection
More informationJuniper JN0-661 Exam Questions and Answers (PDF) Juniper JN0-661 Exam Questions JN0-661 BrainDumps
Juniper JN0-661 Dumps with Valid JN0-661 Exam Questions PDF [2018] The Juniper JN0-661 Juniper Service Provider Routing and Switching Exam exam is an ultimate source for professionals to retain their credentials
More informationBGP Best External. Finding Feature Information
The feature provides the network with a backup external route to avoid loss of connectivity of the primary external route. The feature advertises the most preferred route among those received from external
More informationHPE FlexFabric 5940 Switch Series
HPE FlexFabric 5940 Switch Series MCE Configuration Guide Part number: 5200-1024b Software version: Release 25xx Document version: 6W102-20170830 Copyright 2017 Hewlett Packard Enterprise Development LP
More informationBGP MPLS VPNs. Introduction
This chapter describes services that are supported for Border Gateway Protocol (BGP) Multi-Protocol Label Switching (MPLS) Virtual Private Networks (VPNs). MPLS is a licensed Cisco feature that requires
More informationCisco Training - HD Telepresence MPLS: Implementing Cisco MPLS V3.0. Upcoming Dates. Course Description. Course Outline
Cisco Training - HD Telepresence MPLS: Implementing Cisco MPLS V3.0 From the technology basics to advanced VPN configuration. $3,995.00 5 Days Upcoming Dates Dec 10 - Dec 14 Mar 25 - Mar 29 Course Description
More informationInterAS Option B. Information About InterAS. InterAS and ASBR
This chapter explains the different InterAS option B configuration options. The available options are InterAS option B, InterAS option B (with RFC 3107), and InterAS option B lite. The InterAS option B
More informationH3C S7500E-XS Switch Series
H3C S7500E-XS Switch Series Comware 7 MPLS Configuration Guide New H3C Technologies Co., Ltd. http://www.h3c.com.hk Software version: S7500EXS-CMW710-R7536P05 Document version: 6W100-20170630 Copyright
More informationTELCO GROUP NETWORK. Rafał Jan Szarecki 23/10/2011
TELCO GROUP NETWORK Rafał Jan Szarecki 23/10/2011 GOALS G-NET Regional (MEA) TELCO has 12 national s OpCo. Build international network infrastructure, to allow all OpCo offer VPNs with sites in multiple
More informationMPLS VPN Explicit Null Label Support with BGP. BGP IPv4 Label Session
MPLS VPN Explicit Null Label Support with BGP IPv4 Label Session The MPLS VPN Explicit Null Label Support with BGP IPv4 Label Session feature provides a method to advertise explicit null in a Border Gateway
More informationBGP Support for the L2VPN Address Family
BGP support for the Layer 2 Virtual Private Network (L2VPN) address family introduces a BGP-based autodiscovery mechanism to distribute L2VPN endpoint provisioning information. BGP uses a separate L2VPN
More informationBGP-MVPN SAFI 129 IPv6
Subsequent Address Family Identifier (SAFI) 129, known as VPN Multicast SAFI, provides the capability to support multicast routing in the service provider's core IPv6 network. Border Gateway Protocol (BGP)
More informationHP Routing Switch Series
HP 12500 Routing Switch Series EVI Configuration Guide Part number: 5998-3419 Software version: 12500-CMW710-R7128 Document version: 6W710-20121130 Legal and notice information Copyright 2012 Hewlett-Packard
More informationConfiguring BGP: RT Constrained Route Distribution
Configuring BGP: RT Constrained Route Distribution BGP: RT Constrained Route Distribution is a feature that can be used by service providers in Multiprotocol Label Switching (MPLS) Layer 3 VPNs to reduce
More informationMPLS LDP. Agenda. LDP Overview LDP Protocol Details LDP Configuration and Monitoring 9/27/16. Nurul Islam Roman
MPLS LDP Nurul Islam Roman (nurul@apnic.net) 1 Agenda LDP Overview LDP Protocol Details LDP Configuration and Monitoring 1 Label Distribution Protocol Overview MPLS nodes need to exchange label information
More informationWhat You Will Learn By the end of this appendix, you should know and be able to explain the following:
What You Will Learn By the end of this appendix, you should know and be able to explain the following: What static MPLS labels are and how they can be used The difference between static MPLS bindings and
More information