Any Transport over MPLS

Transcript

1 Any Transport MPLS over describes how to configure over MPLS (AToM) transports data link layer (Layer This module Any Transport Label Switching providers backbone. AToM enables service over a Multiprotocol to 2) packets (MPLS) sites with existing Layer 2 networks by using a single, integrated, packet-based network connect customer Cisco MPLS network. Instead of using separate networks with network infrastructure--a management environments, providers can deliver Layer 2 connections over an MPLS backbone. AToM provides service framework and transport supported Layer 2 traffic types over an MPLS network a common to encapsulate core. the following transport AToM supports types: like-to-like • ATM Adaptation over MPLS Layer Type-5 (AAL5) • ATM Cell Relay over MPLS • Ethernet over MPLS (port modes) • Circuit Emulation (CEM) Note For information see Configuring Pseudowire . on ATM Cell relay and Circuit Emulation(CEM), Feature , on page 2 • Finding Information • Prerequisites for Any Transport over MPLS, on page 2 Restrictions , on page 2 • General , on page 3 • ATM AAL5 over MPLS Restrictions • Ethernet over MPLS (EoMPLS) Restrictions , on page 3 • Tunnel Selection Restrictions , on page 3 • Remote Ethernet Port Shutdown Restrictions , on page 3 • Restrictions for PPP and Multilink PPP, on page 3 About Any Transport over MPLS, on page 4 • Information • How to Configure over MPLS, on page 14 Any Transport • Configuration Examples for Any Transport over MPLS, on page 42 • Additional References for Any Transport over MPLS, on page 64 • Feature Information for Any Transport over MPLS, on page 64 Any Transport over MPLS 1

2 MPLS over Transport Any Information Feature Finding Finding Information Feature and in this module. documented all the features may not support release Your software For the latest caveats To release. and software notes for your platform Tool and the release feature see Bug Search information, in which each find information about the features in this module, and to see a list of the releases documented see the feature table. information feature is supported, and Cisco software image support. about platform to find information Navigator Use Cisco Feature support . An account on Cisco.com is not required. To access Cisco Feature Navigator , go to www.cisco.com/go/cfn MPLS over for Any Prerequisites Transport edge (PE) routers can reach each other via • IP routing must be configured in the core so that the provider IP. • MPLS must be configured in the core so that a label-switched path (LSP) exists between the PE routers. Layer 2 traffic. Ensure that the for originating • A loopback interface must be configured and terminating PErouters canaccesstheotherrouter’sloopback interface. Notethattheloopback interface isnotneeded in all cases. For example, does not need a loopback interface tunnel selection when AToM is directly (TE) tunnel. to a traffic engineering mapped Restrictions General format--Configure the Label Distribution Protocol (LDP) router ID on all PE routers to be a • Address might not function loopback address with a /32 mask. Otherwise, some configurations properly . with explicit Null MPLS encapsulation, when a Transparent Clock (TC) is • For PTPoIP configuration field. the correction and a PTP slave, the TC does not update a PTP master placed between on the BGP gateway • TE-FRR because with BGP labels for layer 2 and layer 3 VPNs must terminate of the four-label limitation. MPLS labels using IPv4 Border • If an AToM tunnel spans different service providers that exchange Gateway MPLS label stack is Protocol (BGP) (RFC 3107), you add a label to the stack. The maximum four (FRR label, TE label, LDP label, VC label). . For pseudowire (HSPW) convergence without pseudowire grouping increments • Hot standby linearly forathousand virtualcircuits, itrequires about54seconds ofconvergencetime.Thisisapplicable example, only for the Cisco RSP3 Module. the convergence numbers. Clear interface is not the recommended way to measure on L2VPN • With two ECMP paths, load sharing traffic occurs based on odd or even MPLS VC labels. evenMPLSVClabels,loadsharing ButifL2VPN IfL2VPN circuits haveeitherodd or isnotperformed. evenMPLSVClabels,thentheoddMPLSVClabelscircuits circuits and ofbothodd haveacombination link. will select one link whereas the even MPLS VC labels circuits will select another MPLS over Any Transport 2

3 MPLS over Transport Any Restrictions MPLS over ATM AAL5 MPLS Restrictions ATM AAL5 over only in SDU mode. • AAL5 over MPLS is supported Restrictions (EoMPLS) MPLS over Ethernet over MPLS must be in the between Ethernet the CE and PE routers • The subinterfaces that are running same subnet. as the PE router. CE router must be on the same VLAN on the adjoining • The subinterface that conform The 802.1Q over MPLS supports • Ethernet to the IEEE 802.1Q VLAN packets standard. membership into Ethernet information VLAN for inserting method a standard establishes specification the PE and CE routers. The Inter-Switch is not supported frames. between Link (ISL) protocol , if the peer PE does not support a control word, the • The AToM control word is supported. However word is disabled. control • Ethernet packets with hardware-level cyclic redundancy check (CRC) errors, and runt errors, framing are discarded packets on input. Restrictions Selection Tunnel be an LSP destined path should • The selected to the peer PE router. • The selected tunnel must be an MPLS TE tunnel. of the loopback • If you specify an IP address, that address must be the IP address interface on the remote must have a /32 mask. There must be an LSP destined address. PE router. The address to that selected The LSP need not be a TE tunnel. Restrictions Shutdown Port Ethernet Remote if the remote PE router is running image or is on another This feature is not symmetrical an older version andthelocalPEisrunning feature portshutdown Ethernet remote theEoMPLS thatdoesnotsupport platform this feature. an image which supports Port Shutdown is supported only on EFP with encapsulation default. Remote Ethernet Restrictions for PPP and Multilink PPP module. links in a Multilink • All member PPP bundle must be on the same interface • All member links in a Multilink must be of the same bandwidth. PPP bundle links per bundle is supported. of 16 member • A maximum MPLS Transport Any over 3

4 MPLS over Transport Any MPLS over Transport Any About Information of the Multilink PPP bundle to change the bundle fragmentation • Perform or no shutdown a shutdown and disabled. enabled mode between PPP fragmentation , Multilink However (LFI) is not supported. and Interleaving • Link Fragmentation is supported fragmentation, see Disabling PPP Multilink Fragmentation section. by default. To disable PPP is not supported. Multilink • Multicast is not supported. • PPP compression for this feature. • IPv6 is not supported is not supported. • PPP half bridging (ACFC) or Protocol-Field-Compression (PFC) • To enable an Address-and-Control-Field-Compression configuration, perform a shutdown or no shutdown on the serial interface. PPP bundle. timeslots cannot be used as memberlink in a Multilink • Fractional are not supported. • Frame Relay (FR) and Multilink Frame Relay (MFR) • Compressing IP or UDP or RTP headers are not supported. serial interfaces, • PPP and Multilink PPP are supported on synchronous serial interfaces. Asynchronous (HSSI), and ISDN interfaces High-Speed are not supported. Serial Interfaces with different MTU values, PPP connection on each end of an Multilink interfaces • When you configure of the same MTU is recommended. the link drops traffic at high traffic rates. The configuration over MPLS Information About Any Transport To configure AToM, you must understand the following concepts: How AToM Transports Layer 2 Packets at the ingress AToM encapsulates PE at the other end Layer 2 frames PE and sends them to a corresponding theencapsulation TheegressPEremoves thetwoPErouters. between whichisaconnection ofapseudowire, and sends out the Layer 2 frame. between transmission of the PE PE routers The successful of the Layer 2 frames is due to the configuration You specify routers. the following the routers. between called a pseudowire, You set up the connection, on each PE router: information across the pseudowire, Frame Relay, • The type of Layer 2 data that will be transported such as Ethernet, or ATM the PE routers to • The IP address of the loopback interface of the peer PE router, which enables communicate the pseudowire • A unique combination of peer PE IP address and VC ID that identifies of Layer The following example shows the basic configuration steps on a PE router that enable the transport Each transport 2 packets. different steps. type has slightly or subinterface on the PE router: the interface Step 1 defines over Transport Any MPLS 4

5 Any MPLS over Transport Associated Commands Using Protocol-Based Layer AToM Transports How Feature L2VPN with 2 Packets Router# interface interface-type interface-number configuration instance andentersservice onaninterface mode: service anethernet Step2configures instance ethernet service WORD Router(config-if)# instance number Router(config-if)# service instance 393 ethernet ethernet1 such as dot1q: type for the interface, the encapsulation Step 3 specifies Router(config-if-srv)# encapsulation encapsulation-type Step 4 does the following: the LDP router ID of the peer PE router. a connection • Makes to the peer PE router by specifying , called the VC ID, which is shared between the two PE routers. a 32-bit unique • Specifies identifier The combination use on the router. Two circuits of the peer router ID and the VC ID must be unique cannot the same combination of peer router ID and VC ID. the tunneling • Specifies AToM uses MPLS as the data in the pseudowire. used to encapsulate method method. tunneling Router(config-if-srv)# xconnect peer-router-id vcid encapsulation mpls thetunneling Asanalternative, youcansetupapseudowire classtospecify andothercharacteristics. method see the Configuring For more information, Class, on page 15. the Pseudowire 2 Packets How AToM Transports with Associated Commands Using Layer L2VPN Protocol-Based Feature Layer 2 frames at the ingress PE and sends them to a corresponding PE at the other end AToM encapsulates ofapseudowire, whichisaconnection between thetwoPErouters. TheegressPEremoves theencapsulation and sends out the Layer 2 frame. of the PE between is due to the configuration The successful transmission of the Layer 2 frames PE routers called a pseudowire, the following You specify the routers. between routers. You set up the connection, on each PE router: information Frame Relay, such as Ethernet, across the pseudowire, • The type of Layer 2 data that will be transported or ATM of the peer PE router, which enables of the loopback the PE routers interface to • The IP address communicate • A unique of peer PE IP address and VC ID that identifies the pseudowire combination The following example shows the basic configuration steps on a PE router that enable the transport of Layer 2 packets. Each transport type has slightly different steps. the interface on the PE router: or subinterface Step 1 defines MPLS Any Transport over 5

6 MPLS over Transport Any of AToM Benefits Router# interface interface-number interface-type gi 0/1/0 interface Router(config)# configuration mode: anethernet service onaninterface andentersservice instance Step2configures instance WORD ethernet number instance service Router(config-if)# instance service ethernet1 Router(config-if)# 393 ethernet Step 3 specifies the encapsulation type for the interface, such as dot1q: Router(config-if)# encapsulation encapsulation-type encapsulation dot1q Router(config-if-srv)# 393 Step 3 does the following: the LDP router ID of the peer PE router. to the peer PE router by specifying a connection • Makes identifier , called the VC ID, which is shared between the two PE routers. • Specifies a 32-bit unique The combination of the peer router ID and the VC ID must be unique on the router. Two circuits cannot use the same combination of peer router ID and VC ID. method used to encapsulate data in the pseudowire. AToM uses MPLS as the • Specifies the tunneling tunneling method. Router(config)# interface pseudowire 100 encapsulation mpls Router(config-if)# 123 10.0.0.1 neighbor Router(config-if)# exit Router(config-if)# ! l2vpn xconnect context A Router(config)# 100 Router(config-xconnect)# member pseudowire 393 member service instance Router (config-xconnect)# gigabitethernet0/1/0 exit Router(config-xconnect)# method youcansetupapseudowire Asanalternative, andothercharacteristics. classtospecify thetunneling see the Configuring For more information, Class, on page 15. the Pseudowire of AToM Benefits of enabling Layer 2 packets to be sent in the MPLS network: list explains some of the benefits The following many types of Layer 2 packets, including • The AToM product and Frame set accommodates Ethernet all types of Relay, across multiple Cisco router platforms. This enables the service provider to transport traffic over the backbone and accommodate all types of customers. for transporting developed over MPLS. This benefits • AToM adheres to the standards Layer 2 packets Other in the network. the service provider that wants to incorporate industry-standard methodologies are proprietary , which can limit the service provider Layer 2 solutions ’s ability to expand the network to use only one vendor’s equipment. provider and can force the service MPLS over Transport Any 6

7 MPLS over Transport Any Reroute Fast Engineering Traffic MPLS to the customer . Because the service provider network is separate • Upgrading to AToM is transparent of service disruption to AToM without can upgrade provider the service network, from the customer to that they are using a traditional . The customers Layer 2 backbone. the customer assume Reroute Fast Engineering Traffic MPLS (FRR) support. with fast reroute (TE) tunnels AToM can use MPLS traffic engineering AToM VCs can be rerouted around a failed link or node at the same time as MPLS and IP prefixes. commands; fast reroute you can use standard any special on AToM does not require fast reroute Enabling commands. whenitisroutedtoanFRR-protected Attheingress PE,anAToMtunnelisprotected byfastreroute TE tunnel. Both link and node protection are supported for AToM VCs at the ingress PE. Packet Maximum Transmission Unit Guidelines for Estimating Size the size of the packets through the core network. traveling helps you determine calculation The following of the P and PE routers interfaces on the core-facing unit (MTU) transmission You set the maximum to than or equal to the total bytes of the items in accommodate packets of this size. The MTU should be greater the following equation: label label header * MPLS Core MTU >= (Edge MTU + Transport + AToM header + (MPLS stack size)) used in the equation. the variables describe sections The following MTU Edge interfaces. The edge MTU is the MTU for the customer-facing Header Transport sizes of the headers. The Transport header type. The table below lists the specific on the transport depends of Packets Size 1: Header Table Type Transport Packet Size AAL5 0-32 bytes 18 bytes Ethernet VLAN Port 14 bytes Ethernet FrameRelayDLCI Task Force (IETF) 2 bytes for Cisco encapsulation, 8 bytes for Internet Engineering encapsulation HDLC 4 bytes PPP 4 bytes over Transport Any MPLS 7

8 MPLS over Transport Any Example Size Packet Estimating AToM Header and cell PPP, HDLC, for Ethernet, word is optional word). The control is 4 bytes (control The AToM header types. The control relay transport types. word is required for Frame Relay and ATM AAL5 transport Stack Label MPLS of the core MPLS network: on the configuration The MPLS label stack size depends MPLSlabel theAToMVCs(VClabel).Therefore, • AToMusesoneMPLSlabeltoidentify theminimum connected AToM PEs, which are PE routers that do not have a P router between stack is one for directly them. • If LDP is used in the MPLS network, the label stack size is two (the LDP label and the VC label). PE routers of LDP is used between • If a TE tunnel instead in the MPLS network, the label stack size is two (the TE label and the VC label). • If a TE tunnel and LDP are used in the MPLS network (for example, a TE tunnel between P routers or with LDP on the tunnel), P and PE routers, between the label stack is three (TE label, LDP label, VC label). • If you use MPLS fast reroute in the MPLS network, you add a label to the stack. The maximum MPLS label stack in this case is four (FRR label, TE label, LDP label, VC label). environment, • If AToM is used by the customer carrier in an MPLS VPN Carrier Supporting Carrier you add a label to the stack. The maximum is four (FRR carrier network MPLS label stack in the provider label, TE label, LDP label, VC label). • If an AToM tunnel spans different service that exchange providers MPLS labels using IPv4 Border MPLS label stack is Gateway (BGP) (RFC 3107), you add a label to the stack. The maximum Protocol four (FRR label, TE label, LDP label, VC label) because of • TE-FRR with BGP labels for layer 2 and layer 3 VPNs must terminate on the BGP gateway the four-label limitation. Othercircumstances canincrease theMPLSlabelstacksize.Therefore, analyze thecomplete datapathbetween Then the AToM tunnel endpoints the maximum MPLS label stack size for your network. and determine the label stack size by the size of the MPLS label. multiply Example Size Packet Estimating example The estimated is 1526 bytes, based on the following packet size in the following assumptions: • The edge MTU is 1500 bytes. 18 bytes for the transport • The transport header. which designates VLAN, type is Ethernet • The AToM header the control is 0, because word is not used. LDP is used. The MPLS label is 4 bytes. • The MPLS label stack is 2, because * MPLS Edge = Core MTU MTU + Transport header + AToM header + (MPLS label stack label) 1500 + 18 + 0 + (2 * 4 ) = 1526 the P and PE routers in the core to accept packets of 1526 bytes. You must configure MPLS over Transport Any 8

9 MPLS over Transport Any AToM with Supported Features QoS QoS Supported with AToM Features The tables below list the QoS features supported by AToM. over Ethernet MPLS Table 2: QoS Features Supported with Ethernet QoS Feature over MPLS policy to: Service Can be applied (input and output) • Interface Supports the following Classification commands: cos match • (on interfaces) (on interfaces) experimental mpls match • (oninterfaces) (output policy) • match qos-gr oup commands: the following Supports Marking policy) (output cos set • discard-class (input policy) • set experimental • set mpls (input policy) (on interfaces) oup qos-gr • set (input policy) Policing the following: Supports • Color-aware policing • Multiple-action policing • Single-rate policing policing • Two-rate Supports the following: Queueing andshaping • Byte-based WRED (LLQ) • Low Latency Queueing (WRED) Early Detection Random • Weighted Transport MPLS over Any 9

10 MPLS over Transport Any AToM with Supported Features QoS Table Features Supported with Frame Relay over MPLS 3: QoS over Relay Frame MPLS QoS Feature Can be applied to: Service policy • Interface (input and output) • PVC (input and output) Supports the following commands: Classification and VCs) (on interfaces fr-de match • fr-dlci • match (on interfaces) oup qos-gr • match the following commands: Marking Supports management congestion elay frame-r • (output) set discard-class • • set fr-de (output policy) fr-fecn-becn • set (output) set experimental • mpls • set qos-gr oup ecn (output) threshold • Supports the following: Policing • Color-aware policing policing • Multiple-action • Single-rate policing policing • Two-rate MPLS Transport Any over 10

11 MPLS over Transport Any AToM with Supported Features QoS QoS Feature Frame over MPLS Relay Queueing andshaping the following: Supports WRED • Byte-based • Class-based weighted fair queueing (CBWFQ) • LLQ • random-detect discard-class-based command • Traffic shaping • WRED Supported Features 4: QoS Table over and AAL5 with MPLS Relay ATM Cell MPLS Feature ATM Cell Relay QoS and AAL5 over Can be applied policy Service to: • Interface (input and output) • PVC (input and output) • Subinterface (input and output) commands: Classification Supports the following experimental • match mpls (on VCs) • match qos-gr oup (output) Supports the following commands: Marking discard-class-based • random-detect (input) and VCs) clp (on interfaces, • set (output) subinterfaces, • (input) discard-class set set • subinterfaces, (on interfaces, (input) mpls and experimental VCs) (input) oup qos-gr set • the following: Policing Supports • Color-aware policing • Multiple-action policing policing • Single-rate • Two-rate policing over Any MPLS Transport 11

12 Any MPLS over Transport (AToM) MPLS Port Transport Any Shutdown Ethernet Remote over ATM Cell and AAL5 over MPLS QoS Feature Relay Queueing Supports andshaping the following: WRED • Byte-based • CBWFQ on ATM PVCs support shaping • Class-based • LLQ command • discard-class-based random-detect • WRED Any Port Ethernet Remote Shutdown (AToM) MPLS over Transport over allows a service This Cisco IOS XE feature provider edge (PE) router on the local end of an Ethernet pseudowire MPLS (EoMPLS) link failure and cause the shutdown of the Ethernet port on to detect a remote port on the local CE router is shut down, the router the Ethernet edge (CE) router. Because the local customer does not lose data by continuously if the link is sending traffic to the failed remote link. This is beneficial configured as a static IP route. a CE The figure below illustrates a condition in an EoMPLS WAN, with a down Layer 2 tunnel link between router (Customer Edge 1) and the PE router (Provider Edge 1). A CE router on the far side of the Layer 2 to forward tunnel (Customer Edge 2), continues the L2 tunnel. Edge 1 through traffic to Customer 1: Remote WAN in EoMPLS Outage Link Figure Previous link. Traffic forwarded Edge 2 router could not detect a failed remote the Provider to this feature, Edge 2 to Customer Edge 1 would be lost until routing or spanning tree protocols detected from Customer would be even link. If the link was configured with static routing, the remote link outage the down remote more difficult to detect. Withthisfeature, theProvider Edge2routerdetects theremote linkfailureandcausesashutdown ofthelocal L2tunnellinkisrestored, thelocalinterface isautomatically Customer port.Whentheremote Edge2Ethernet as well. The possibility restored of data loss is thus diminished. isgenerally sequence asfollows: Ethernet tothefigureabove,theRemote described Withreference Shutdown Edge 1 fails. Edge 1 and Provider Customer link between The remote 1. laser on the line card interface the transmit link failure and disables the remote Edge 2 detects Provider 2. to Customer Edge 2. connected 3. An RX_LOS error alarm is received by Customer Edge 2 causing Edge 2 to bring down the Customer interface. 4. Edge 2 in an up state. with Customer its interface Edge 2 maintains Provider Any MPLS over Transport 12

13 Any MPLS over Transport Associated Commands Using Shutdown Port Ethernet Protocol-Based (AToM) MPLS over Transport Any Feature L2VPN with Remote Edge2routerenables thetransmit 5. linkandEoMPLS connection isrestored, theProvider Whentheremote laser. interface. Edge 2 router brings up its downed The Customer 6. by default by This feature is enabled You can also enable this feature over MPLS (EoMPLS). for Ethernet modeasshowninthefollowing remote usingthe inxconnect command e notification failur link configuration example: eompls pseudowire-class encapsulation mpls ! interface GigabitEthernet1/0/0 eompls xconnect 10.13.13.13 1 pw-class remote failure notification link ! inxconnect failur configuration no remote e notification usingthe canbedisabled Thisfeature link command to display EXEC command privileged L2 brief ip interface show the status of all remote mode. Use the privileged EXEC command to show the status of the L2 tunnel on a tunnel links. Use the show interface specific interface. Note failur to clients for remote will not give notification e notification command link no remote The attachment circuit status down. Note is supported only on EFP with encapsulation default. Remote Ethernet Port Shutdown Port Transport over MPLS (AToM) Remote Ethernet Any Shutdown Using Commands Associated with L2VPN Protocol-Based Feature over This Cisco IOS XE feature allows a service provider edge (PE) router on the local end of an Ethernet MPLS (EoMPLS) pseudowire to detect a remote link failure and cause the shutdown of the Ethernet port on the Ethernet the local customer edge (CE) router. Because port on the local CE router is shut down, the router sending traffic to the failed remote if the link is link. This is beneficial does not lose data by continuously as a static IP route. configured a CE in an EoMPLS a condition The figure below illustrates WAN, with a down Layer 2 tunnel link between router (Customer Edge 1). A CE router on the far side of the Layer 2 Edge 1) and the PE router (Provider to forward traffic to Customer Edge 1 through the L2 tunnel. tunnel (Customer Edge 2), continues in EoMPLS WAN Outage Link 2: Remote Figure Transport Any MPLS over 13

14 MPLS over Transport Any MPLS over Transport Any to Configure How the Provider Edge 2 router could not detect a failed remote link. Traffic forwarded Previous to this feature, detected tree protocols or spanning Edge 1 would be lost until routing Edge 2 to Customer from Customer link outage with static routing, link. If the link was configured the down remote would be even the remote more difficult to detect. ofthelocal linkfailureandcausesashutdown theremote Edge2routerdetects theProvider Withthisfeature, thelocalinterface Customer L2tunnellinkisrestored, isautomatically port.Whentheremote Edge2Ethernet as well. The possibility of data loss is thus diminished. restored described asfollows: Withreference isgenerally sequence Shutdown Ethernet tothefigureabove,theRemote link between Edge 1 fails. Customer The remote Edge 1 and Provider 1. the transmit laser on the line card interface 2. Provider Edge 2 detects the remote link failure and disables Edge 2. connected to Customer Edge 2 causing Customer Edge 2 to bring down the 3. An RX_LOS error alarm is received by Customer interface. 4. Provider Edge 2 maintains its interface with Customer Edge 2 in an up state. isrestored, Edge2routerenables thetransmit 5. Whentheremote linkandEoMPLS theProvider connection laser. interface. Edge 2 router brings up its downed The Customer 6. This feature You can also enable this feature by for Ethernet by default is enabled over MPLS (EoMPLS). link failur e notification command inxconnect usingthe modeasshowninthefollowing remote configuration example: l2vpn xconnect context con1 member GigabitEthernet1/0/0 service-instance 300 100 member Pseudowire notification failure link remote e notification canbedisabled Thisfeature link configuration no remote usingthe command failur inxconnect the status of all remote mode. Use the show L2 ip interface to display EXEC command privileged brief privileged show tunnel links. Use the to show the status of the L2 tunnel on a interface EXEC command interface. specific Note link failur e notification command will not give notification to clients for remote attachment The no remote circuit status down. How to Configure Any Transport over MPLS a basic AToM configuration the following and includes explains This section procedures: how to perform MPLS over Transport Any 14

15 MPLS over Transport Any Class the Pseudowire Configuring Configuring Class the Pseudowire Note class if you specify a pseudowire You need not specify this task is optional. configurations, In simple the method xconnect command. tunneling as part of the class or as part of the as part of the pseudowire command mpls encapsulation the • You must specify for the AToM VCs to work properly mpls command command . If you omit the encapsulation xconnect error: the following you receive command, xconnect as part of the command. % Incomplete SUMMAR Y STEPS 1. enable e terminal 2. configur name 3. pseudowir e-class 4. mpls encapsulation STEPS DETAILED Command Purpose or Action enable Enables privileged EXEC mode. Step 1 • Enter your password if prompted. Example: Router> enable Enters global configuration configur e terminal mode. 2 Step Example: terminal configure Router# apseudowire classwithanamethatyouspecify Establishes name e-class pseudowir Step 3 and enters pseudowire mode. class configuration Example: pseudowire-class atom Router(config)# mpls Specifies the tunneling encapsulation. encapsulation 4 Step Example: Router(config-pw)# mpls encapsulation MPLS over Transport Any 15

16 Any MPLS over Transport Associated Commands Using Protocol-Based the Pseudowire Configuring Feature L2VPN with Class L2VPN Configuring Class Using Commands Associated with the Pseudowire Feature Protocol-Based Note a pseudowire You need not specify the configurations, In simple this task is optional. class if you specify context l2vpn as part of the method command. xconnect tunneling • You must specify class or as part of the as part of the pseudowire command mpls encapsulation the l2vpn encapsulation . If you omit the for the AToM VCs to work properly command context xconnect as part of the mpls xconnect context command, you receive the following error: l2vpn command % Incomplete command. SUMMAR Y STEPS 1. enable 2. configur e terminal 3. interface pseudowir e name mpls encapsulation 4. neighbor 5. vcid-value ess peer-addr DETAILED STEPS Command or Action Purpose EXEC mode. enable Enables privileged 1 Step • Enter your password if prompted. Example: enable Router> e terminal Enters global configuration mode. configur Step 2 Example: terminal Router# configure Establishes with a name that you pseudowire an interface name e pseudowir interface 3 Step and enters pseudowire mode. class configuration specify Example: interface Router(config)# atom pseudowire encapsulation mpls encapsulation. the tunneling Specifies 4 Step Example: mpls Router(config-pw-class)# encapsulation Specifies the peer IP address and virtual circuit (VC) ID vcid-value ess neighbor peer-addr Step 5 pseudowire. value of a Layer 2 VPN (L2VPN) Example: MPLS Any Transport over 16

17 MPLS over Transport Any a Pseudowire Type and Removing the Encapsulation Changing or Action Purpose Command 1 33.33.33.33 neighbor Router(config-pw-class)# Type and Removing the Encapsulation Changing a Pseudowire Onceyou specify mpls command, the you cannotremove itusingthe no encapsulation mpls encapsulation command. error message: result in the following Those methods on an existing are not allowed changes Encapsulation pw-class. Toremove mpls command, youmustdeletethepseudowire withthe encapsulation no pseudowir e-class the command. and command e-class using the the pseudowire remove the type of encapsulation, To change no pseudowir type. reconfigure the pseudowire to specify the new encapsulation Changing the Encapsulation Type and Removing a Pseudowire Using Protocol-Based with Commands Associated the L2VPN Feature no encapsulation Onceyou specify mpls the encapsulation mpls command, you cannotremove itusingthe command. Those methods result in the following error message: pseudowire on existing encapsulation remove % Cannot To remove the encapsulation mpls command, you must delete the pseudowire with the no interface pseudowir e command. no template command Tochange pseudowir e thetypeofencapsulation, remove thepseudowire usingthe type type. the new encapsulation to specify the pseudowire and reconfigure MPLS Configuring ATM AAL5 over over ATM AAL5 MPLS Configuring on PVCs Y STEPS SUMMAR 1. enable e terminal configur 2. 3. subinterface ] interface type slot / subslot / port [ . l2transport pvc [ name ] vpi / 4. vci 5. encapsulation aal5 mpls vcid 6. xconnect peer-r outer-id encapsulation 7. end mpls vc l2transport show 8. MPLS Any over Transport 17

18 MPLS over Transport Any on PVCs MPLS over ATM AAL5 Configuring DETAILED STEPS Purpose or Action Command EXEC mode. privileged enable Enables 1 Step • Enter your password if prompted. Example: enable Router> e terminal configur mode. Enters global configuration 2 Step Example: configure terminal Router# Specifies the interface type and enters interface subslot ] . port interface / [ / slot type subinterface 3 Step mode. configuration Example: interface atm1/0/0 Router(config)# or assigns Creates a name to an ATM PVC and enters vpi [ name vci l2transport / ] pvc 4 Step mode. PVC configuration L2transport Example: indicates keyword l2transport • The that the PVC is a l2transport Router(config-if)# pvc 1/200 of a terminated PVC instead switched PVC. for the PVC. Make encapsulation aal5 Specifies ATM AAL5 encapsulation Step 5 typeonthePEand sureyouspecify thesameencapsulation Example: customer edge (CE) routers. encapsulation Router(config-if-atm-l2trans-pvc)# aal5 VC. circuit to a pseudowire Binds the attachment mpls peer-r xconnect vcid outer-id encapsulation 6 Step Example: xconnect Router(config-if-atm-l2trans-pvc)# mpls 100 encapsulation 10.13.13.13 end EXEC mode. Exits to privileged Step 7 Example: Router(config-if-atm-l2trans-pvc)# end l2transport show Displays output that shows ATM AAL5 over MPLS is mpls vc Step 8 on a PVC. configured Example: l2transport mpls Router# vc show Any MPLS Transport over 18

19 Any MPLS over Transport with associated the commands using CLIs MPLS over ATM AAL5 Configuring feature Protocol-Based the L2VPN on PVCs Examples that shows that ATM The following is sample output from the show mpls l2transport vc command AAL5 over MPLS is configured on a PVC: vc Router# show mpls l2transport intf Local Dest Local address VC ID Status circuit --------- ------------ ------ ----- ------------- UP 1/100 10.4.4.4 100 ATM1/0 ATM AAL5 with the commands ATM AAL5 Configuring the L2VPN associated on PVCs MPLS over using Protocol-Based CLIs feature Y STEPS SUMMAR 1. enable configur 2. e terminal / port [ . subinterface ] 3. interface type slot / subslot vci 4. pvc [ name ] vpi / l2transport encapsulation aal5 5. 6. end 7. interface pseudowir e number 8. mpls encapsulation peer-addr ess vcid-value 9. neighbor exit 10. context 11. l2vpn xconnect context-name member 12. pseudowir e interface-number vci vpi 13. member atm interface-number pvc / 14. end atom l2vpn show 15. vc STEPS DETAILED Command Purpose or Action Enables enable EXEC mode. privileged 1 Step if prompted. • Enter your password Example: Device> enable configur Enters global configuration e terminal mode. 2 Step Example: configure terminal Device# type and enters interface Specifies the interface . [ interface type slot / subslot / ] subinterface port Step 3 mode. configuration Example: over Any MPLS Transport 19

20 Any MPLS over Transport with associated the commands using CLIs MPLS over ATM AAL5 Configuring feature Protocol-Based the L2VPN on PVCs Purpose or Action Command atm1/0/0 Device(config)# interface a name to an ATM PVC and enters or assigns Creates vci vpi ] name [ pvc l2transport / Step 4 L2transport mode. PVC configuration Example: • The indicates keyword l2transport that the PVC is Device(config-if)# l2transport pvc 1/200 PVC instead a switched PVC. of a terminated aal5 Specifies encapsulation ATM AAL5 encapsulation for the PVC. Make 5 Step the same encapsulation type on the PE sure you specify Example: and customer edge (CE) routers. Device(config-if-atm-l2trans-pvc)# encapsulation aal5 end EXEC mode. Exits to privileged Step 6 Example: Device(config-if-atm-l2trans-pvc)# end interface and enters interface Specifies the pseudowire interface pseudowir e number 7 Step configuration mode. Example: interface Device(config)# 100 pseudowire (MPLS) Specifies that Multiprotocol Label Switching mpls encapsulation is Step 8 method. used as the data encapsulation Example: mpls Device(config-if)# encapsulation Specifies the peer IP address and virtual circuit (VC) ID peer-addr neighbor ess vcid-value 9 Step pseudowire. value of the Layer 2 VPN (L2VPN) Example: Device(config-if)# neighbor 10.13.13.13 100 exit mode. configuration Exits interface Step 10 Example: Device(config-if)# exit a Layer 2 VPN (L2VPN) context cross connect Creates context-name l2vpn xconnect context 11 Step mode. configuration and enters xconnect Example: xconnect context Device(config)# con1 l2vpn a member pseudowire to form a Layer 2 VPN Specifies member pseudowir e interface-number 12 Step (L2VPN) cross connect. Example: Device(config-xconnect)# member pseudowire 100 MPLS Any Transport over 20

21 Any MPLS over Transport over Configuration Configuring Mode in VC Class MPLS ATM AAL5 Purpose or Action Command interface. of the ATM member the location Specifies atm member vpi vci / pvc interface-number Step 13 Example: Device(config-xconnect)# member atm 100 pvc 1/200 end Exits to privileged EXEC mode. Step 14 Example: Device(config-xconnect)# end output that shows ATM AAL5 over MPLS is show l2vpn atom Displays vc Step 15 configured on a PVC. Example: show vc Device# l2vpn atom Examples show l2vpn atom vc command thatshowsthatATMAAL5 Thefollowing issample outputfromthe over MPLS is configured on a PVC: vc Device# show l2vpn atom address Status Local intf Local circuit VC ID Dest ------ ----- ------------ ------------- --------- 10.4.4.4 100 1/100 ATM AAL5 ATM1/0 UP in VC Class Configuration Mode Configuring ATM AAL5 over MPLS Y STEPS SUMMAR enable 1. 2. configur e terminal 3. vc-class atm vc-class-name 4. layer-type encapsulation exit 5. . subslot / slot subinterface type interface 6. port / [ ] vc-class-name class-int 7. pvc name [ / 8. vci vpi ] l2transport vcid encapsulation mpls 9. xconnect peer-r outer-id 10. end class-links 11. show atm DETAILED STEPS or Action Purpose Command privileged Enables EXEC mode. enable 1 Step Transport over MPLS Any 21

22 Any MPLS over Transport over Configuration Configuring Mode in VC Class MPLS ATM AAL5 Purpose or Action Command • Enter your password if prompted. Example: enable Router> e terminal Enters global configuration mode. configur Step 2 Example: configure terminal Router# a VC class and enters VC class configuration Creates vc-class-name atm vc-class Step 3 mode. Example: Router(config)# vc-class atm aal5class the AAL and encapsulation type. Configures layer-type encapsulation 4 Step Example: aal5 Router(config-vc-class)# encapsulation exit Exits VC class configuration mode. 5 Step Example: exit Router(config-vc-class)# Specifies the interface type enters interface configuration subinterface slot interface type / subslot / port [ ] . Step 6 mode. Example: atm1/0/0 interface Router(config)# or a VC class to the ATM main interface Applies class-int vc-class-name Step 7 subinterface. Example: Note You can also apply a VC class to a PVC. class-int Router(config-if)# aal5class a name to an ATM PVC and enters Creates or assigns [ l2transport / vpi ] name vci pvc Step 8 mode. PVC configuration L2transport Example: • The l2transport that the PVC is indicates keyword l2transport pvc 1/200 Router(config-if)# a switched PVC. of a terminated PVC instead circuit to a pseudowire VC. Binds the attachment mpls xconnect peer-r outer-id vcid encapsulation Step 9 Example: Router(config-if-atm-l2trans-pvc)# xconnect 10.13.13.13 100 encapsulation mpls end EXEC mode. Exits to privileged Step 10 Example: MPLS over Transport Any 22

23 Any MPLS over Transport with associated the commands using Mode CLIs in VC Class MPLS over ATM AAL5 Configuring feature Protocol-Based the L2VPN Configuration Purpose or Action Command Router(config-if-atm-l2trans-pvc)# end atm Displays the type of encapsulation and that the VC class show class-links Step 11 to an interface. was applied Example: Router# show atm class-links Examples the command class-links command verifies In the following atm output from the example, show output shows the as part of a VC class. The command that ATM AAL5 over MPLS is configured type of encapsulation and that the VC class was applied to an interface. 1/100 show Router# atm class-links vc 1/100: Displaying vc-class inheritance for ATM1/0/0.0, - using default no broadcast - Not configured configured aal5 on main interface - VC-class encapsulation Mode Configuration using MPLS over ATM AAL5 Configuring the commands associated in VC Class with the L2VPN Protocol-Based CLIs feature SUMMAR Y STEPS 1. enable e terminal configur 2. 3. vc-class vc-class-name atm 4. encapsulation layer-type 5. exit [ . subinterface 6. interface type slot / subslot / port ] class-int vc-class-name 7. 8. pvc [ name ] vpi / vci l2transport 9. exit number 10. interface pseudowir e mpls 11. encapsulation vcid-value 12. neighbor peer-addr ess 13. exit context-name 14. l2vpn xconnect context pseudowir e interface-number member 15. 16. member atm interface-number 17. end class-links 18. show atm Any Transport over MPLS 23

24 Any MPLS over Transport with associated the commands using Mode CLIs in VC Class MPLS over ATM AAL5 Configuring feature Protocol-Based the L2VPN Configuration DETAILED STEPS Purpose Command or Action Enables privileged EXEC mode. enable 1 Step • Enter your password if prompted. Example: Router> enable configur Enters global configuration mode. e terminal 2 Step Example: terminal configure Router# Creates a VC class and enters VC class configuration atm vc-class vc-class-name Step 3 mode. Example: Router(config)# vc-class atm aal5class Configures the AAL and encapsulation type. layer-type encapsulation 4 Step Example: aal5 Router(config-vc-class)# encapsulation Exits VC class configuration exit mode. Step 5 Example: exit Router(config-vc-class)# Specifies the interface type enters interface configuration / [ interface ] subinterface . port type subslot / slot Step 6 mode. Example: interface atm1/0/0 Router(config)# Applies or a VC class to the ATM main interface vc-class-name class-int 7 Step subinterface. Example: Note You can also apply a VC class to a PVC. Router(config-if)# class-int aal5class a name to an ATM PVC and enters Creates or assigns name ] pvc [ l2transport vci / vpi Step 8 L2transport mode. PVC configuration Example: • The l2transport keyword indicates that the PVC is l2transport Router(config-if)# pvc 1/200 PVC. of a terminated a switched PVC instead Exits interface configuration exit mode. 9 Step Example: Router(config-if)# exit MPLS over Transport Any 24

25 Any MPLS over Transport with associated the commands using Mode CLIs in VC Class MPLS over ATM AAL5 Configuring feature Protocol-Based the L2VPN Configuration Purpose or Action Command Specifies the pseudowire interface and enters interface e interface pseudowir number Step 10 mode. configuration Example: 100 Router(config)# interface pseudowire Label Switching encapsulation mpls (MPLS) Specifies that Multiprotocol is 11 Step used as the data encapsulation method. Example: mpls Router(config-if)# encapsulation the peer IP address Specifies and virtual circuit (VC) ID ess vcid-value neighbor peer-addr Step 12 value of the Layer 2 VPN (L2VPN) pseudowire. Example: 10.0.0.1 neighbor 123 Router(config-if)# mode. exit configuration Exits interface Step 13 Example: Router(config-if)# exit Creates a Layer 2 VPN (L2VPN) cross connect context context-name context xconnect l2vpn 14 Step and enters xconnect mode. configuration Example: con1 Router(config)# l2vpn xconnect context a member pseudowire to form a Layer 2 VPN Specifies pseudowir e interface-number member Step 15 cross connect. (L2VPN) Example: Router(config-xconnect)# member pseudowire 100 of the ATM member Specifies the location interface. member interface-number atm Step 16 Example: Device(config-xconnect)# member atm 100 Exits to privileged EXEC mode. end Step 17 Example: Router(config-if-atm-l2trans-pvc)# end Displays the type of encapsulation show atm class-links and that the VC class Step 18 to an interface. was applied Example: show Router# atm class-links Transport Any over MPLS 25

26 MPLS over Transport Any MPLS over Ethernet Configuring Examples verifies command class-links atm show output from the the command example, In the following that ATM AAL5 over MPLS is configured output shows the as part of a VC class. The command to an interface. and that the VC class was applied type of encapsulation 1/100 Router# atm class-links show vc 1/100: Displaying for ATM1/0/0.0, inheritance vc-class no broadcast - Not configured default - using interface on main configured - VC-class encapsulation aal5 over MPLS Configuring Ethernet Mode in Port over Ethernet Configuring MPLS Y STEPS SUMMAR 1. enable 2. configur e terminal / port / 3. interface gigabitethernet slot subslot ess no ip addr 4. negotiation auto 5. service 6. id ethernet instance peer-r outer-id vcid encapsulation 7. xconnect mpls 8. end 9. show mpls l2transport vc DETAILED STEPS or Action Command Purpose enable EXEC mode. privileged Enables 1 Step • Enter your password if prompted. Example: Router> enable configur Enters global configuration mode. e terminal Step 2 Example: terminal configure Router# interface andentersinterface Specifies theGigabit Ethernet port slot interface gigabitethernet / subslot / Step 3 configuration mode. Example: interface gigabitethernet 0/2/4 Router(config)# Any MPLS Transport over 26

27 Any MPLS over Transport Associated Commands Using Mode Protocol-Based MPLS over Ethernet Configuring Feature the L2VPN with in Port Purpose or Action Command Specifies thatthereisnoIPaddress assigned totheinterface. no ip addr ess Step 4 Example: Router(config-if)# no ip address negotiation Enables the auto negotiation protocol. auto Step 5 Example: Router(config-if)# auto negotiation and service Configures instance onaninterface anethernet id ethernet service instance Step 6 enters service mode. configuration instance Example: instance service 100 ethernet Router(config-if)# Binds the attachment circuit to a pseudowire VC. encapsulation vcid outer-id peer-r xconnect mpls Step 7 Example: 10.0.0.1 123 Router(config-if)# xconnect encapsulation mpls end EXEC mode. Exits to privileged 8 Step Example: Router(config-if)# end Displays vc l2transport mpls show overMPLSportmode. aboutEthernet information Step 9 Example: mpls l2transport vc Router# show Associated Using Ethernet over MPLS in Port Mode Commands Configuring with the L2VPN Protocol-Based Feature SUMMAR Y STEPS 1. enable 2. e terminal configur gigabitethernet . subinterface ] [ port / subslot / slot interface 3. 4. end pseudowir e 5. number interface 6. mpls encapsulation peer-addr 7. ess vcid-value neighbor exit 8. xconnect context context-name 9. l2vpn interface-number e pseudowir member 10. MPLS over Transport Any 27

28 Any MPLS over Transport Associated Commands Using Mode Protocol-Based MPLS over Ethernet Configuring Feature the L2VPN with in Port gigabitethernet interface-number 11. member 12. end 13. end atom 14. vc show l2vpn DETAILED STEPS or Action Purpose Command enable privileged Enables EXEC mode. Step 1 • Enter your password if prompted. Example: enable Device> e terminal configur Enters global configuration mode. Step 2 Example: Device# configure terminal theGigabit andentersinterface interface Ethernet Specifies . [ port / subslot / slot gigabitethernet interface Step 3 configuration mode. subinterface ] • Make sure the interface on the adjoining CE router Example: as this PE router. is on the same VLAN gigabitethernet4/0/0 interface Device(config)# Exits to privileged EXEC mode. end Step 4 Example: Device(config-if)# end the pseudowire interface and enters interface Specifies number interface pseudowir e Step 5 configuration mode. Example: Device(config)# interface pseudowire 100 mpls is encapsulation Specifies that Multiprotocol Label Switching (MPLS) Step 6 used as the data encapsulation method. Example: encapsulation mpls Device(config-if)# the peer IP address Specifies and virtual circuit (VC) ID vcid-value neighbor ess peer-addr Step 7 value of the Layer 2 VPN (L2VPN) pseudowire. Example: Device(config-if)# neighbor 10.0.0.1 123 configuration mode. exit Exits interface 8 Step Example: exit Device(config-if)# over Transport Any MPLS 28

29 MPLS over Transport Any Selection Tunnel Configuring Purpose or Action Command context cross connect a Layer 2 VPN (L2VPN) Creates l2vpn context-name xconnect context Step 9 mode. configuration and enters xconnect Example: con1 context xconnect l2vpn Device(config)# pseudowire to form a Layer 2 VPN Specifies a member interface-number member pseudowir e 10 Step (L2VPN) cross connect. Example: pseudowire 100 Device(config-xconnect)# member member Specifies the location of the Gigabit Ethernet interface-number member gigabitethernet 11 Step interface. Example: Device(config-xconnect)# member GigabitEthernet0/0/0.1 Exits to privileged EXEC mode. end Step 12 Example: Device(config-xconnect)# end end EXEC mode. Exits to privileged 13 Step Example: end Device(config-if)# atom vc information about Ethernet over MPLS port l2vpn show Displays 14 Step mode. Example: atom Device# show l2vpn vc Selection Tunnel Configuring Y STEPS SUMMAR 1. enable configur e terminal 2. name e-class pseudowir 3. encapsulation 4. mpls | peer { ip-addr ess | host-name }} [ disable-fallback ] 5. preferr ed-path { interface tunnel tunnel-number 6. exit subslot 7. port interface type slot / / 8. encapsulation encapsulation-type vcid outer-id name 9. pw-class peer-r xconnect MPLS over Transport Any 29

30 MPLS over Transport Any Selection Tunnel Configuring DETAILED STEPS or Action Command Purpose EXEC mode. privileged Enables enable 1 Step if prompted. • Enter your password Example: enable Router> e terminal Enters global configuration configur mode. 2 Step Example: terminal Router# configure classwithanamethatyouspecify apseudowire Establishes pseudowir e-class name Step 3 configuration mode. and enters pseudowire Example: ts1 Router(config)# pseudowire-class encapsulation. For AToM, the mpls Specifies encapsulation the tunneling Step 4 encapsulation type is mpls. Example: encapsulation Router(config-pw)# mpls tunnelorIPaddress Specifies theMPLStrafficengineering { tunnel-number | interface preferr ed-path tunnel 5 Step path. to be used as the preferred or hostname ip-addr ess | host-name }} [ disable-fallback peer { ] Example: path Router(config-pw)# preferred peer 10.18.18.18 modeandenables exit Exitsfrompseudowire configuration the 6 Step feature. Tunnel Selection Example: Router(config-pw)# exit aninterface configuration Specifies typeandentersinterface type / port subslot interface / slot Step 7 mode. Example: atm1/1/0 Router(config)# interface for the interface. the encapsulation Specifies encapsulation-type encapsulation Step 8 Example: Router(config-if)# encapsulation aal5 Binds the attachment circuit to a pseudowire VC. outer-id vcid pw-class name xconnect peer-r Step 9 Example: 10.0.0.1 123 pw-class Router(config-if)# xconnect ts1 Any MPLS over Transport 30

31 MPLS over Transport Any Tips Troubleshooting Examples vc l2transport thefollowing mpls command show outputfromthe sample Inthefollowing includes about the VCs: information because apreferred • VC101hasbeenassigned Thedefault pathcalledTunnel1. pathisdisabled, the preferred path fails. not be used if the preferred path should that the default path specified of a loopback an IP address path can address • VC 150 has been assigned on PE2. The default path fails. be used if the preferred font shows the preferred path information. output that is in boldface Command show Router# l2transport vc detail mpls Gi0/0/0.1 up, line protocol up, Eth VLAN Local interface: 222 up up Destination address: 10.16.16.16, VC ID: 101, VC status: Tunnel1, Preferred active path: disabled path: Default hop point2point Tunnel label: 3, next interface: Output Tu1, imposed label stack {17 16} 00:27:31 Create 00:27:31, last status change time: time: protocol: Signaling LDP, peer 10.16.16.16:0 up 16 MPLS VC labels: 25, remote local 6 Group ID: local 0, remote MTU: local 1500, remote 1500 Remote description: interface Sequencing: disabled send disabled, receive VC statistics: totals: receive 10, send 10 packet 1260, byte totals: receive send 1300 receive 0, send 0 packet drops: 0/50 protocol up, line up ATM1/0/0 interface: Local up, ATM AAL5 up VC status: VC ID: 150, 10.16.16.16, address: Destination path: 10.18.18.18, active Preferred ready path: Default 3, next label: Tunnel hop point2point Output interface: Tu2, imposed label stack {18 24} time: 00:07:37 Create time: last status change 00:15:08, Signaling up 10.16.16.16:0 peer LDP, protocol: VC labels: local 26, remote 24 MPLS 0 Group ID: local 2, remote 4470 4470, MTU: local remote description: interface Remote send Sequencing: receive disabled disabled, VC statistics: 0 0, send receive totals: packet 0, send 0 byte totals: receive drops: receive 0, send 0 packet Troubleshooting Tips cell-packing To debug ATM cell packing, issue the debug command. atm MPLS over Transport Any 31

32 Any MPLS over Transport Associated Commands Using Protocol-Based Tunnel Configuring Feature L2VPN with Selection L2VPN Configuring Selection Using Commands Associated with Tunnel Feature Protocol-Based Y STEPS SUMMAR enable 1. e terminal configur 2. name type template 3. pseudowir e 4. mpls encapsulation | ip-addr { peer | tunnel-number tunnel interface { ed-path ess preferr hostname 5. disable-fallback ] }} [ exit 6. ] subinterface . [ port / subslot / slot type interface 7. encapsulation-type 8. encapsulation 9. end 10. interface pseudowir e number ce template 11. sour type pseudowir e name vcid-value ess peer-addr neighbor 12. 13. end xconnect 14. context-name context l2vpn interface-number 15. member pseudowir e mpls member ip-addr ess vc-id encapsulation 16. 17. end DETAILED STEPS Purpose Command or Action EXEC mode. enable Enables privileged 1 Step • Enter your password if prompted. Example: Router> enable e terminal Enters global configuration mode. configur Step 2 Example: Router# configure terminal Creates atemplate pseudowire withanamethatyouspecify name e pseudowir type template Step 3 and enters pseudowire configuration mode. Example: ts1 Router(config)# template type pseudowire Specifies the tunneling encapsulation. For AToM, the encapsulation mpls Step 4 encapsulation type is mpls. Example: Router(config-pw)# encapsulation mpls Transport MPLS over Any 32

33 Any MPLS over Transport Associated Commands Using Protocol-Based Tunnel Configuring Feature L2VPN with Selection or Action Purpose Command Specifies theMPLStrafficengineering tunnelorIPaddress | tunnel interface { ed-path tunnel-number peer preferr 5 Step to be used as the preferred or hostname path. hostname }} [ disable-fallback ip-addr ] { | ess Example: 10.18.18.18 Router(config-pw)# preferred path peer exit mode and enables configuration Exits from pseudowire 6 Step the Tunnel Selection feature. Example: exit Router(config-pw)# Specifies type and enters interface an interface slot / subslot / port [ . subinterface ] interface type Step 7 configuration mode. Example: Router(config)# interface atm1/1/0 the encapsulation for the interface. Specifies encapsulation-type encapsulation 8 Step Example: Router(config-if)# encapsulation aal5 Exits to privileged EXEC mode. end 9 Step Example: Router(config-if)# end the pseudowire Specifies interface and enters interface interface pseudowir e number Step 10 mode. configuration Example: Router(config)# 100 pseudowire interface named oftypepseudowire thesourcetemplate Configures type sour name pseudowir e ce template 11 Step ts1. Example: template source type Router(config-if)# pseudowire ts1 the peer IP address and virtual circuit (VC) ID Specifies neighbor peer-addr ess vcid-value Step 12 value of a Layer 2 VPN (L2VPN) pseudowire. Example: 123 Router(config-if)# neighbor 10.0.0.1 EXEC mode. end Exits to privileged Step 13 Example: Router(config-if)# end MPLS over Transport Any 33

34 Any MPLS over Transport with associated CLIs Tips using Troubleshooting feature Protocol-Based the L2VPN the commands Purpose or Action Command Creates a Layer 2 VPN (L2VPN) context cross connect context xconnect l2vpn context-name 14 Step and enters xconnect mode. configuration Example: Router(config)# con1 context xconnect l2vpn to form a Layer 2 VPN pseudowire a member Specifies interface-number e pseudowir member Step 15 cross connect. (L2VPN) Example: member Router(config-xconnect)# pseudowire 100 Creates the Layer 2 packets. the VC to transport ip-addr encapsulation member mpls vc-id ess 16 Step Example: 123 10.0.0.1 Router(config-xconnect)# member mpls encapsulation end Exits to privileged EXEC mode. Step 17 Example: end Router(config-xconnect)# Protocol-Based Troubleshooting Tips using the commands associated feature CLIs with the L2VPN debug if the For example, tunnel selection. to troubleshoot command vc event atom l2vpn You can use the l2vpn tunnel interface that is used for the preferred path is shut down, the default path is enabled. The debug the following atom vc event command provides output: update_action vc_handle AToM SMGR [10.2.2.2, 101]: Processing imposition update, 62091860, 16 3, remote_vc_label rewrite: no parent route selected tunnel [10.2.2.2, SMGR AToM not up 101]: [10.2.2.2, Et3/2 SMGR Imposition 101]: Programmed, AToM Output Interface: AToM with Bits Experimental Setting Note . and CEM is supported Only EoMPLS Y STEPS SUMMAR enable 1. 2. configur e terminal 3. class-map class-name 4. match any policy-map 5. policy-name class-name 6. class MPLS over Transport Any 34

35 MPLS over Transport Any AToM with Bits Experimental Setting 7. mpls experimental value set exit 8. exit 9. subslot 10. slot type interface / / port policy-name input service-policy 11. end 12. interface-name ] [ dlci dlci ] [ input | output ] show 13. vc policy-map [ [ vpi / ] interface vci STEPS DETAILED or Action Command Purpose enable EXEC mode. privileged Enables Step 1 • Enter your password if prompted. Example: Router> enable Enters global configuration mode. configur e terminal Step 2 Example: Router# configure terminal Specifies the user-defined name of the traffic class and class-name class-map 3 Step enters class map configuration mode. Example: class1 class-map Router(config)# match that all packets will be matched. Use only the Specifies any 4 Step any keyword. Other keywords might cause unexpected Example: results. Router(config-cmap)# match any and the name of the traffic policy to configure Specifies policy-name policy-map 5 Step enters policy-map configuration mode. Example: policy-map policy1 Router(config-cmap)# Specifies thenameofapredefined trafficclass,whichwas class class-name Step 6 usedtoclassify command, withthe class-map configured Example: traffic to the traffic policy and enters policy-map class configuration mode. class1 class Router(config-pmap)# the value to which the MPLS bits are set if the Designates mpls set experimental value 7 Step packets match the specified policy map. Example: set mpls Router(config-pmap-c)# 7 experimental class configuration mode. exit Exits policy-map 8 Step Example: Transport over MPLS Any 35

36 MPLS over Transport Any Word the Control Enabling Purpose or Action Command exit Router(config-pmap-c)# exit mode. configuration Exits policy-map Step 9 Example: exit Router(config-pmap)# type and enters interface the interface Specifies interface type / subslot / port slot Step 10 mode. configuration Example: interface atm1/0/0 Router(config)# Attaches a traffic policy to an interface. policy-name input service-policy 11 Step Example: Router(config-if)# service-policy input policy1 Exits to privileged EXEC mode. end Step 12 Example: Router(config-if)# end to an interface. Displays the traffic policy attached [ vpi [ vc show policy-map ] interface-name interface / 13 Step ] [ dlci dlci ] [ vci | output ] input Example: Router# show policy-map interface serial3/0/0 Enabling Word the Control Y STEPS SUMMAR enable 1. configur 2. e terminal cw_enable 3. pseudowir e-class mpls encapsulation 4. ol-word contr 5. 6. end DETAILED STEPS Command or Action Purpose EXEC mode. Enables privileged enable Step 1 • Enter your password if prompted. Example: MPLS over Transport Any 36

37 Any MPLS over Transport with associated the commands CLIs the Control Enabling feature Protocol-Based the L2VPN Word using or Action Purpose Command Router> enable Enters global configuration mode. e terminal configur 2 Step Example: terminal Router# configure mode. pseudowir cw_enable Enters pseudowire class configuration e-class 3 Step Example: cw_enable pseudowire-class Router(config)# encapsulation mpls encapsulation. the tunneling Specifies 4 Step type is MPLS. • For AToM, the encapsulation Example: encapsulation Router(config-pw-class)# mpls the control Enables contr word. ol-word Step 5 Example: control-word Router(config-pw-class)# end EXEC mode. Exits to privileged 6 Step Example: end Router(config-pw-class)# Enabling the Control Word using the commands associated with the L2VPN Protocol-Based CLIs feature SUMMAR Y STEPS 1. enable 2. configur e terminal number 3. interface pseudowir e 4. encapsulation mpls ol-word 5. contr include 6. neighbor ess peer-addr vcid-value end 7. STEPS DETAILED Purpose or Action Command EXEC mode. enable Enables privileged 1 Step MPLS over Transport Any 37

38 MPLS over Transport Any Shutdown Port Ethernet AToM Remote MPLS Configuring or Action Purpose Command if prompted. • Enter your password Example: enable Router> e terminal configur mode. Enters global configuration Step 2 Example: Router# configure terminal pseudowire Creates with a value that you an interface e interface number pseudowir 3 Step mode. configuration and enters pseudowire specify Example: Router(config)# 1 pseudowire interface the tunneling mpls encapsulation encapsulation. Specifies Step 4 • For AToM, the encapsulation type is mpls. Example: mpls Router(config-pw)# encapsulation word. Enables the control contr ol-word include 5 Step Example: include control-word Router(config-pw)# Specifies and virtual circuit (VC) ID the peer IP address ess peer-addr neighbor vcid-value 6 Step pseudowire. value of a Layer 2 VPN (L2VPN) Example: 10.0.0.1 Router(config-pw)# neighbor 123 Exits to privileged EXEC mode. end 7 Step Example: Router(config-pw)# end Shutdown Port Ethernet AToM Remote MPLS Configuring Note Ethernet enabled feature over MPLS (AToM): Remote The Any Transport Port Shutdown is automatically on the router. is loaded supported when an image with the feature by default SUMMAR Y STEPS 1. enable 2. configur e terminal [ pseudowir ] pw-class-name 3. e-class over Any MPLS Transport 38

39 MPLS over Transport Any Shutdown Port Ethernet AToM Remote MPLS Configuring mpls 4. encapsulation 5. exit subslot / slot / port interface 6. type 7. ethernet number service number instance default encapsulation 8. pw-class-name pw-class vc-id ess peer-ip-addr xconnect 9. e notification no remote link 10. failur 11. remote link e notification failur end 12. STEPS DETAILED or Action Command Purpose privileged enable EXEC mode. Enables 1 Step • Enter your password if prompted. Example: Router> enable mode. Enters global configuration e terminal configur Step 2 Example: Router# configure terminal Specifies class and the name of a Layer 2 pseudowire [ pseudowir ] pw-class-name e-class Step 3 mode. enters pseudowire class configuration Example: eompls Router(config)# pseudowire-class encapsulation Specifies mpls that MPLS is used as the data encapsulation 4 Step for tunneling method Layer 2 traffic over the pseudowire. Example: mpls encapsulation Router(config-pw)# exit mode. Exits to global configuration Step 5 Example: Router(config-pw)# exit an interface type and enters interface Configures slot / subslot / port type interface 6 Step mode. configuration Example: interface GigabitEthernet1/0/0 Router (config)# an ethernet Configures on an interface service instance number ethernet instance number service 7 Step instance configuration mode. and enters service Example: 393 ethernet instance service Router(config-if)# MPLS Transport Any over 39

40 Any MPLS over Transport with associated the commands using Shutdown CLIs Ethernet AToM Remote MPLS Configuring feature Protocol-Based the L2VPN Port or Action Purpose Command Specifies the encapsulation type for the interface, such as default encapsulation 8 Step dot1q. Example: Note is supported Remote ethernet port shutdown default Router(config-if-srv)# encapsulation default. only with encapsulation Bindsanattachment circuittoapseudowire, andconfigures ess peer-ip-addr vc-id pw-class xconnect Step 9 over MPLS (AToM) static pseudowire. an Any Transport pw-class-name Example: 1 pw-class Router(config-if)# xconnect 10.1.1.1 eompls failur MPLSAToMremote Disables linkfailurenotification e notification and link no remote Step 10 shutdown. Example: failure Router(config-if-xconn)# remote link notification and Enables remote link failur e notification MPLS AToM remote link failure notification Step 11 shutdown. Example: failure link remote Router(config-if-xconn)# notification EXEC mode. Exits to privileged end 12 Step Example: end Router(config-if-xconn)# AToM Remote MPLS Port Ethernet Configuring Shutdown using the commands associated CLIs with the L2VPN Protocol-Based feature Note feature is automatically enabled over MPLS (AToM): Remote Port Shutdown The Any Transport Ethernet when an image with the feature supported is loaded on the router. by default SUMMAR Y STEPS 1. enable 2. configur e terminal ] template type pseudowir [ e-name pseudowir e 3. mpls encapsulation 4. 5. exit subslot port / / slot type interface 6. MPLS Transport over Any 40

41 Any MPLS over Transport with associated the commands using Shutdown CLIs Ethernet AToM Remote MPLS Configuring feature Protocol-Based the L2VPN Port pseudowir e number 7. interface 8. sour ce template e pseudowir type neighbor vcid-value ess peer-addr 9. end 10. xconnect 11. context l2vpn context-name 12. failur no remote e notification link e notification failur link remote 13. end 14. DETAILED STEPS Purpose Command or Action enable Enables privileged EXEC mode. 1 Step • Enter your password if prompted. Example: Device> enable configur mode. Enters global configuration e terminal Step 2 Example: configure terminal Device# Specifies the name of a Layer 2 pseudowire class and type e-name [ e pseudowir pseudowir template ] Step 3 class configuration enters pseudowire mode. Example: pseudowire eompls Device(config)# template type that MPLS is used as the data encapsulation encapsulation mpls Specifies Step 4 method for tunneling Layer 2 traffic over the pseudowire. Example: Device(config-pw)# encapsulation mpls Exits to global configuration mode. exit 5 Step Example: exit Device(config-pw)# type and enters interface Configures an interface slot subslot port type / / interface 6 Step mode. configuration Example: GigabitEthernet1/0/0 Device(config)# interface interface. the pseudowire Specifies pseudowir e number interface 7 Step Example: 100 pseudowire interface Device(config-if)# over Transport Any MPLS 41

42 MPLS over Transport Any MPLS over Transport for Any Examples Configuration or Action Purpose Command oftypepseudowire pseudowir ce template sour e named type thesourcetemplate Configures Step 8 eompls. Example: Device(config-if)# source template type pseudowire eompls Specifies the peer IP address and virtual circuit (VC) ID vcid-value peer-addr ess neighbor 9 Step value of a Layer 2 VPN (L2VPN) pseudowire. Example: 1 10.1.1.1 neighbor Device(config-if)# end EXEC mode. Exits to privileged 10 Step Example: end Device(config-if)# Creates a Layer 2 VPN (L2VPN) cross connect context context context-name xconnect l2vpn 11 Step configuration and enters xconnect mode. Example: con1 context xconnect l2vpn Device(config)# and Disables no remote link failur MPLSAToMremote linkfailurenotification e notification Step 12 shutdown. Example: Device(config-xconnect)# no remote link failure notification and Enables remote link failur e notification link failure notification MPLS AToM remote 13 Step shutdown. Example: failure link remote Device(config-xconnect)# notification end Exits to privileged EXEC mode. 14 Step Example: end Device(config-xconnect)# over MPLS Configuration Examples for Any Transport MPLS ATM over Example: of ATM over MPLS on two PE routers. The table below shows the configuration MPLS over Transport Any 42

43 Any MPLS over Transport Associated Commands Using Protocol-Based ATM over Example: Feature L2VPN with MPLS MPLS Configuration Example Table 5: ATM over PE2 PE1 ldp label protocol ldp label mpls protocol mpls force Loopback0 force Loopback0 ldp router-id mpls ldp router-id mpls ! ! interface Loopback0 Loopback0 interface 10.13.13.13 255.255.255.255 255.255.255.255 ip address ip address 10.16.12.12 ! ATM4/0/0 interface ATM4/0/0 interface pvc 0/100 pvc 0/100 l2transport l2transport encapsulation encapsulation aal0 aal0 10.13.13.13 xconnect 10.16.12.12 100 encapsulation 100 encapsulation mpls xconnect mpls ! ! ATM4/0/0.300 point-to-point interface interface ATM4/0/0.300 point-to-point no ip directed-broadcast no ip directed-broadcast no atm enable-ilmi-trap no atm enable-ilmi-trap l2transport pvc 0/300 l2transport pvc 0/300 aal0 encapsulation aal0 encapsulation 300 encapsulation mpls xconnect 10.13.13.13 mpls 10.16.12.12 xconnect 300 encapsulation with Example: ATM over MPLS Using L2VPN Commands Associated Protocol-Based Feature of ATM over MPLS on two PE routers. The table below shows the configuration MPLS over Transport Any 43

44 Transport MPLS Any over with Associated Commands Using MPLS ATM over Example: Feature Protocol-Based L2VPN 6: ATM over Table MPLS Configuration Example PE2 PE1 Any Transport over MPLS 44

45 Any MPLS over Transport Associated Commands Using Protocol-Based ATM over Example: Feature L2VPN with MPLS PE2 PE1 ldp protocol label mpls ldp protocol label mpls Loopback0 ldp router-id force mpls mpls force Loopback0 ldp router-id ! ! Loopback0 interface interface Loopback0 255.255.255.255 10.13.13.13 255.255.255.255 ip address 10.16.12.12 ip address ! interface ATM4/0/0 interface ATM4/0/0 pvc 0/100 l2transport pvc 0/100 l2transport aal0 encapsulation aal0 encapsulation interface pseudowire 100 interface pseudowire 100 encapsulation mpls encapsulation mpls neighbor 123 10.0.0.1 123 10.0.0.1 neighbor ! ! context A l2vpn xconnect context A l2vpn xconnect pseudowire pseudowire 100 member 100 member member atm 100 member atm 100 ! ! point-to-point point-to-point ATM4/0/0.300 interface ATM4/0/0.300 interface no ip directed-broadcast no atm enable-ilmi-trap l2transport no atm enable-ilmi-trap pvc 0/300 pvc 0/300 l2transport encapsulation aal0 encapsulation aal0 300 pseudowire interface mpls interface encapsulation 300 pseudowire 123 encapsulation mpls neighbor 10.0.0.1 MPLS over Transport Any 45

46 Any MPLS over Transport over ATM AAL5 Configuration Example: Mode in VC Class MPLS Configuring PE2 PE1 123 10.0.0.1 neighbor ! ! A context xconnect l2vpn l2vpn member pseudowire xconnect A 300 context 300 pseudowire member atm 300 member atm 300 member Configuration over ATM AAL5 Configuring Example: Mode MPLS in VC Class The following example configures ATM AAL5 over MPLS in VC class configuration mode. The VC class to an interface. is then applied enable configure terminal vc-class atm aal5class encapsulation aal5 atm1/0/0 interface class-int aal5class pvc 1/200 l2transport mpls xconnect 10.13.13.13 100 encapsulation ATM AAL5 over MPLS in VC class configuration configures example The following mode. The VC class to a PVC. is then applied enable terminal configure atm aal5class vc-class encapsulation aal5 interface atm1/0/0 pvc 1/200 l2transport aal5class class-vc xconnect 10.13.13.13 100 encapsulation mpls Mode ATM AAL5 MPLS in VC Class Configuration Example: Configuring over Commands Feature Protocol-Based L2VPN Using with Associated example mode. The VC class The following ATM AAL5 over MPLS in VC class configuration configures to an interface. is then applied enable terminal configure atm aal5class vc-class aal5 encapsulation interface atm1/0/0 class-int aal5class pvc 1/200 l2transport pseudowire 100 interface mpls encapsulation Any Transport over MPLS 46

47 Any MPLS over Transport MPLS with MPLS Fast Ethernet Example: Reroute Engineering Traffic over 123 neighbor 10.0.0.1 exit l2vpn xconnect context A pseudowire member 100 member atm 100 exit MPLS Reroute Example: Ethernet Traffic Engineering Fast with over MPLS over MPLS with fast The following configuration example and the figure show the configuration of Ethernet reroute on AToM PE routers. characteristics: Routers PE1 and PE2 have the following PE2, using an explicit between is configured path through • A TE tunnel called Tunnel41 a link PE1and called L1. AToM VCs are configured to travel through the FRR-protected tunnel Tunnel41. tunnel is Tunnel1. • The link L1 is protected by FRR, the backup the L2 link. • PE2 is configured to forward the AToM traffic back to PE1 through Reroute Figure 3: Fast Configuration PE1 Configuration label protocol ldp mpls mpls traffic-eng tunnels Loopback1 mpls ldp router-id force ! T41 pseudowire-class mpls encapsulation interface preferred-path Tunnel41 disable-fallback ! IP1 pseudowire-class encapsulation mpls peer 10.4.0.1 disable-fallback preferred-path ! interface Loopback1 ip address 10.0.0.27 255.255.255.255 ! interface Tunnel1 Loopback1 ip unnumbered tunnel destination 10.0.0.1 traffic-eng tunnel mode mpls 1 1 tunnel mpls traffic-eng priority traffic-eng tunnel bandwidth mpls 10000 name FRR mpls traffic-eng path-option 1 explicit tunnel ! interface Tunnel41 Loopback1 ip unnumbered destination tunnel 10.0.0.4 mpls traffic-eng tunnel mode priority tunnel mpls traffic-eng 1 1 1000 bandwidth traffic-eng mpls tunnel MPLS Any Transport over 47

48 Any MPLS over Transport MPLS with MPLS Fast Ethernet Example: Reroute Engineering Traffic over traffic-eng path-option 1 explicit name name-1 tunnel mpls tunnel mpls traffic-eng fast-reroute ! POS0/0/0 interface description pe1name POS8/0/0 10.1.0.2 ip address 255.255.255.252 traffic-eng tunnels mpls mpls traffic-eng backup-path Tunnel1 crc 16 internal clock source pos ais-shut pos report lrdi 155000 ip rsvp bandwidth 155000 ! POS0/3/0 interface pe1name description POS10/1/0 ip address 10.1.0.14 255.255.255.252 traffic-eng mpls tunnels crc 16 clock source internal bandwidth 155000 ip rsvp 155000 ! gigabitethernet3/0/0.1 interface encapsulation dot1Q 203 IP1 xconnect 10.0.0.4 2 pw-class ! gigabitethernet3/0/0.2 interface encapsulation 204 dot1Q T41 xconnect 10.0.0.4 4 pw-class ! 1 ospf router 0 network 10.0.0.0 0.255.255.255 area traffic-eng router-id Loopback1 mpls area mpls traffic-eng 0 ! ip classless ip route 10.4.0.1 255.255.255.255 Tunnel41 ! ip explicit-path name xxxx-1 enable next-address 10.4.1.2 10.1.0.10 next-address P Configuration ip cef tunnels mpls traffic-eng ! Loopback1 interface 255.255.255.255 ip address 10.0.0.1 ! interface FastEthernet1/0/0 255.255.255.0 10.4.1.2 ip address traffic-eng tunnels mpls 10000 bandwidth ip rsvp 10000 ! POS8/0/0 interface POS0/0 description xxxx ip address 10.1.0.1 255.255.255.252 traffic-eng mpls tunnels pos ais-shut lrdi pos report ip rsvp 155000 155000 bandwidth ! Transport MPLS over Any 48

49 Any MPLS over Transport Associated Commands Using Reroute Fast Engineering Protocol-Based MPLS with MPLS over Ethernet Example: Feature L2VPN with Traffic interface POS10/1/0 description xxxx POS0/3 ip address 10.1.0.13 255.255.255.252 tunnels mpls traffic-eng ip rsvp bandwidth 155000 155000 ! 1 router ospf 0 network 0.255.255.255 10.0.0.0 area traffic-eng router-id Loopback1 mpls mpls traffic-eng area 0 PE2 Configuration ip cef mpls ldp protocol label tunnels mpls traffic-eng ldp router-id force Loopback1 mpls ! interface Loopback1 255.255.255.255 10.0.0.4 ip address ! 2 interface loopback 10.4.0.1 ip address 255.255.255.255 ! Tunnel27 interface ip unnumbered Loopback1 tunnel destination 10.0.0.27 tunnel mode mpls traffic-eng traffic-eng autoroute announce tunnel mpls tunnel mpls traffic-eng priority 1 1 bandwidth 1000 traffic-eng mpls tunnel traffic-eng mpls tunnel xxxx-1 name 1 explicit path-option ! interface FastEthernet0/0/0.2 dot1Q encapsulation 203 10.0.0.27 2 encapsulation mpls xconnect ! interface FastEthernet0/0/0.3 encapsulation dot1Q 204 4 encapsulation xconnect 10.0.0.27 mpls ! interface FastEthernet1/1/0 ip address 10.4.1.1 255.255.255.0 mpls traffic-eng tunnels 10000 ip rsvp bandwidth 10000 ! 1 ospf router 0 area 0.255.255.255 10.0.0.0 network Loopback1 router-id traffic-eng mpls mpls traffic-eng area 0 ! xxxx-1 enable ip explicit-path name 10.4.1.2 next-address next-address 10.1.0.10 Traffic Reroute MPLS with Fast MPLS over Engineering Example: Ethernet Using Commands Associated with L2VPN Protocol-Based Feature over MPLS with fast The following configuration example and the figure show the configuration of Ethernet reroute on AToM PE routers. MPLS Any Transport over 49

50 Any MPLS over Transport Associated Commands Using Reroute Fast Engineering Protocol-Based MPLS with MPLS over Ethernet Example: Feature L2VPN with Traffic Routers characteristics: PE1 and PE2 have the following • A TE tunnel called Tunnel41 is configured between PE1and PE2, using an explicit path through a link the FRR-protected tunnel Tunnel41. called L1. AToM VCs are configured to travel through • The link L1 is protected by FRR, the backup tunnel is Tunnel1. the L2 link. • PE2 is configured to forward the AToM traffic back to PE1 through Configuration 4: Fast Figure Reroute PE1 Configuration protocol label mpls ldp mpls traffic-eng tunnels mpls force Loopback1 ldp router-id ! template T41 pseudowire type mpls encapsulation disable-fallback interface Tunnel41 preferred-path ! type pseudowire IP1 template encapsulation mpls preferred-path disable-fallback 10.4.0.1 peer ! Loopback1 interface ip address 10.0.0.27 255.255.255.255 ! interface Tunnel1 ip unnumbered Loopback1 tunnel destination 10.0.0.1 traffic-eng mpls mode tunnel mpls 1 1 priority traffic-eng tunnel bandwidth tunnel mpls traffic-eng 10000 tunnel mpls traffic-eng path-option 1 explicit name FRR ! interface Tunnel41 ip unnumbered Loopback1 10.0.0.4 tunnel destination tunnel mode mpls traffic-eng tunnel mpls traffic-eng priority 1 1 1000 tunnel mpls traffic-eng bandwidth name name-1 mpls tunnel path-option 1 explicit traffic-eng fast-reroute tunnel mpls traffic-eng ! interface POS0/0/0 description pe1name POS8/0/0 ip address 10.1.0.2 255.255.255.252 mpls traffic-eng tunnels traffic-eng backup-path Tunnel1 mpls crc 16 source clock internal pos ais-shut lrdi pos report 155000 155000 bandwidth ip rsvp Transport Any MPLS over 50

51 Any MPLS over Transport Associated Commands Using Reroute Fast Engineering Protocol-Based MPLS with MPLS over Ethernet Example: Feature L2VPN with Traffic ! interface POS0/3/0 description pe1name POS10/1/0 ip address 10.1.0.14 255.255.255.252 tunnels mpls traffic-eng crc 16 clock source internal ip rsvp bandwidth 155000 155000 ! gigabitethernet3/0/0.1 interface 203 dot1Q encapsulation interface 100 pseudowire type source template T41 pseudowire neighbor 10.0.0.4 2 ! l2vpn xconnect context con1 ! gigabitethernet3/0/0.2 interface 204 encapsulation dot1Q interface pseudowire 100 IP1 source template pseudowire type 4 10.0.0.4 neighbor ! xconnect con2 l2vpn context ! ospf 1 router network 10.0.0.0 0.255.255.255 area 0 Loopback1 mpls router-id traffic-eng traffic-eng mpls 0 area ! ip classless Tunnel41 ip route 10.4.0.1 255.255.255.255 ! name xxxx-1 enable ip explicit-path 10.4.1.2 next-address next-address 10.1.0.10 P Configuration ip cef mpls traffic-eng tunnels ! interface Loopback1 ip address 10.0.0.1 255.255.255.255 ! interface FastEthernet1/0/0 ip address 10.4.1.2 255.255.255.0 mpls tunnels traffic-eng ip rsvp bandwidth 10000 10000 ! POS8/0/0 interface POS0/0 xxxx description 10.1.0.1 255.255.255.252 ip address mpls traffic-eng tunnels pos ais-shut lrdi pos report 155000 ip rsvp bandwidth 155000 ! POS10/1/0 interface description xxxx POS0/3 ip address 10.1.0.13 255.255.255.252 tunnels traffic-eng mpls bandwidth 155000 155000 ip rsvp Any MPLS Transport over 51

52 Any MPLS over Transport Associated Commands Using Reroute Fast Engineering Protocol-Based MPLS with MPLS over Ethernet Example: Feature L2VPN with Traffic ! router ospf 1 network 10.0.0.0 0.255.255.255 area 0 router-id traffic-eng mpls Loopback1 mpls traffic-eng area 0 PE2 Configuration ip cef ldp protocol label mpls traffic-eng tunnels mpls mpls ldp router-id Loopback1 force ! interface Loopback1 10.0.0.4 ip address 255.255.255.255 ! interface loopback 2 ip address 10.4.0.1 255.255.255.255 ! interface Tunnel27 Loopback1 ip unnumbered tunnel destination 10.0.0.27 tunnel mode mpls traffic-eng autoroute tunnel announce mpls traffic-eng tunnel mpls traffic-eng priority 1 1 bandwidth tunnel mpls traffic-eng 1000 mpls traffic-eng path-option 1 explicit name xxxx-1 tunnel ! interface FastEthernet0/0/0.2 dot1Q encapsulation 203 interface pseudowire 100 encapsulation mpls neighbor 10.0.0.1 123 ! context l2vpn xconnect A member pseudowire 100 gigabitethernet 0/0/0.1 member ! interface FastEthernet0/0/0.3 204 encapsulation dot1Q interface pseudowire 100 encapsulation mpls neighbor 10.0.0.1 123 ! A l2vpn xconnect context 100 pseudowire member 0/0/0.1 member gigabitethernet ! interface FastEthernet1/1/0 255.255.255.0 ip address 10.4.1.1 mpls tunnels traffic-eng ip rsvp bandwidth 10000 10000 ! ospf 1 router network 10.0.0.0 0 0.255.255.255 area mpls traffic-eng router-id Loopback1 traffic-eng area 0 mpls ! enable xxxx-1 name ip explicit-path next-address 10.4.1.2 10.1.0.10 next-address over Any MPLS Transport 52

53 MPLS over Transport Any Selection Tunnel Configuring Example: Tunnel Selection Example: Configuring an path specifies paths for PE1. One preferred shows how to set up two preferred example The following The other preferred address on MPLS traffic engineering of a loopback path specifies tunnel. an IP address on PE2. on PE1 that uses a TE tunnel to reach the IP address PE2. There is a static route configured PE1 Configuration ldp protocol label mpls traffic-eng tunnels mpls tdp router-id Loopback0 tag-switching pseudowire-class pw1 encapsulation mpls Tunnel1 disable-fallback preferred-path interface ! pw2 pseudowire-class mpls encapsulation 10.18.18.18 peer preferred-path ! Loopback0 interface ip address 10.2.2.2 255.255.255.255 no ip directed-broadcast no ip mroute-cache ! interface Tunnel1 Loopback0 ip unnumbered no ip directed-broadcast tunnel destination 10.16.16.16 tunnel traffic-eng mpls mode tunnel traffic-eng 7 7 mpls priority 1500 bandwidth traffic-eng mpls tunnel mpls traffic-eng path-option 1 explicit name path-tu1 tunnel ! interface Tunnel2 ip unnumbered Loopback0 no ip directed-broadcast 10.16.16.16 tunnel destination traffic-eng mpls mode tunnel 7 7 priority traffic-eng mpls tunnel bandwidth mpls traffic-eng 1500 tunnel 1 dynamic traffic-eng path-option tunnel mpls ! interface gigabitethernet0/0/0 no ip address no ip directed-broadcast auto no negotiation ! gigabitethernet0/0/0.1 interface 222 dot1Q encapsulation no ip directed-broadcast xconnect 10.16.16.16 101 pw-class pw1 ! interface ATM1/0/0 no ip address no ip directed-broadcast no atm enable-ilmi-trap no atm ilmi-keepalive pvc 0/50 l2transport encapsulation aal5 10.16.16.16 150 pw-class pw2 xconnect ! MPLS over Transport Any 53

54 MPLS over Transport Any Selection Tunnel Configuring Example: interface FastEthernet2/0/1 255.255.255.0 10.0.0.1 ip address no ip directed-broadcast ip tag-switching tunnels mpls traffic-eng ip rsvp 15000 15000 bandwidth ! 1 ospf router log-adjacency-changes 10.0.0.0 0 network area 0.0.0.255 network 10.2.2.2 0.0.0.0 area 0 Loopback0 mpls router-id traffic-eng area traffic-eng mpls 0 ! Tunnel2 255.255.255.255 10.18.18.18 ip route ! name path-tu1 enable ip explicit-path next-address 10.0.0.1 index 3 next-address 10.0.0.1 PE2 Configuration ldp mpls label protocol mpls traffic-eng tunnels Loopback0 ldp router-id mpls interface Loopback0 ip address 10.16.16.16 255.255.255.255 no ip directed-broadcast no ip mroute-cache ! interface Loopback2 ip address 10.18.18.18 255.255.255.255 no ip directed-broadcast ! interface FastEthernet1/1/0 10.0.0.2 ip address 255.255.255.0 no ip directed-broadcast tunnels traffic-eng mpls ip mpls no cdp enable bandwidth 15000 ip rsvp 15000 ! FastEthernet1/1/1 interface no ip address no ip directed-broadcast no cdp enable ! FastEthernet1/1/1.1 interface 222 dot1Q encapsulation no ip directed-broadcast no cdp enable 10.2.2.2 route l2transport mpls 101 ! interface ATM5/0/0 no ip address no ip directed-broadcast no atm enable-ilmi-trap no atm ilmi-keepalive pvc 0/50 l2transport encapsulation aal5 xconnect mpls 150 encapsulation 10.2.2.2 ! router ospf 1 over MPLS Any Transport 54

55 Any MPLS over Transport Associated Commands Using Protocol-Based Tunnel Configuring Example: Feature L2VPN with Selection log-adjacency-changes network 10.0.0.0 0.0.0.255 area 0 0 area 0.0.0.0 10.16.16.16 network Loopback0 mpls traffic-eng router-id traffic-eng area mpls 0 Commands Example: Configuring Tunnel with Associated Selection Using Feature L2VPN Protocol-Based an The following paths for PE1. One preferred shows how to set up two preferred example path specifies on MPLS traffic engineering tunnel. an IP address of a loopback address path specifies The other preferred on PE2. on PE1 that uses a TE tunnel to reach the IP address PE2. There is a static route configured PE1 Configuration protocol label mpls ldp tunnels mpls traffic-eng tdp router-id tag-switching Loopback0 pw1 pseudowire type template encapsulation mpls interface Tunnel1 disable-fallback preferred-path ! pseudowire template type pw2 encapsulation mpls 10.18.18.18 preferred-path peer ! Loopback0 interface 10.2.2.2 255.255.255.255 ip address no ip directed-broadcast no ip mroute-cache ! Tunnel1 interface ip unnumbered Loopback0 no ip directed-broadcast tunnel destination 10.16.16.16 mode mpls traffic-eng tunnel priority tunnel mpls traffic-eng 7 7 tunnel mpls traffic-eng bandwidth 1500 name path-tu1 mpls path-option 1 explicit tunnel traffic-eng ! interface Tunnel2 ip unnumbered Loopback0 no ip directed-broadcast destination tunnel 10.16.16.16 traffic-eng tunnel mode mpls mpls priority traffic-eng 7 7 tunnel tunnel mpls traffic-eng 1500 bandwidth traffic-eng mpls tunnel 1 dynamic path-option ! gigabitethernet0/0/0 interface no ip address no ip directed-broadcast no negotiation auto ! interface gigabitethernet0/0/0.1 encapsulation dot1Q 222 no ip directed-broadcast pseudowire 100 interface pw1 source template type pseudowire MPLS over Transport Any 55

56 Any MPLS over Transport Associated Commands Using Protocol-Based Tunnel Configuring Example: Feature L2VPN with Selection neighbor 101 10.16.16.16 ! l2vpn xconnect context con1 ! ATM1/0/0 interface no ip address no ip directed-broadcast no atm enable-ilmi-trap no atm ilmi-keepalive pvc 0/50 l2transport aal5 encapsulation pseudowire 100 interface source template type pseudowire pw2 neighbor 10.16.16.16 150 ! context l2vpn xconnect con1 ! interface FastEthernet2/0/1 10.0.0.1 255.255.255.0 ip address no ip directed-broadcast ip tag-switching traffic-eng mpls tunnels bandwidth 15000 15000 ip rsvp ! router ospf 1 log-adjacency-changes network 10.0.0.0 0.0.0.255 area 0 0 0.0.0.0 network 10.2.2.2 area mpls traffic-eng router-id Loopback0 0 mpls traffic-eng area ! Tunnel2 ip route 10.18.18.18 255.255.255.255 ! ip explicit-path name path-tu1 enable 10.0.0.1 next-address 3 next-address index 10.0.0.1 PE2 Configuration mpls label protocol ldp mpls tunnels traffic-eng ldp router-id Loopback0 mpls Loopback0 interface 10.16.16.16 ip address 255.255.255.255 no ip directed-broadcast no ip mroute-cache ! Loopback2 interface 10.18.18.18 255.255.255.255 ip address no ip directed-broadcast ! FastEthernet1/1/0 interface 10.0.0.2 ip address 255.255.255.0 no ip directed-broadcast mpls traffic-eng tunnels ip mpls no cdp enable ip rsvp bandwidth 15000 15000 ! interface FastEthernet1/1/1 no ip address no ip directed-broadcast no cdp enable MPLS Any Transport over 56

57 Any MPLS over Transport in xconnect Values for L2VPN Configuring Example: Interworking Mode Configuration MTU ! interface FastEthernet1/1/1.1 encapsulation dot1Q 222 no ip directed-broadcast no cdp enable 101 mpls l2transport route 10.2.2.2 ! ATM5/0/0 interface no ip address no ip directed-broadcast no atm enable-ilmi-trap no atm ilmi-keepalive pvc 0/50 l2transport aal5 encapsulation interface pseudowire 100 mpls encapsulation 10.2.2.2 150 neighbor ! l2vpn xconnect context A 100 member pseudowire member GigabitEthernet0/0/0.1 ! 1 router ospf log-adjacency-changes 0 network 10.0.0.0 0.0.0.255 area 0.0.0.0 network 10.16.16.16 area 0 router-id traffic-eng mpls Loopback0 area mpls traffic-eng 0 Configuration Mode for L2VPN Example: Configuring MTU Values in xconnect Interworking ThePE1routerhasaserialinterface Thefollowing example showsanL2VPN example. Interworking configured with an MTU value of 1492 bytes. The PE2 router uses xconnect configuration mode to set a matching MTU to form an interworking of 1492 bytes, which allows the two routers VC. If the PE2 router did not set the MTU value in xconnect configuration mode, the interface would be set to 1500 bytes by default and the VC would not come up. Note interworking is not supported on Cisco ASR 900 RSP3 Module. L2VPN PE1 Configuration atom-ipiw pseudowire-class mpls encapsulation ip interworking ! Loopback0 interface 255.255.255.255 10.1.1.151 ip address ! Serial2/0/0 interface mtu 1492 no ip address encapsulation ppp no fair-queue serial restart-delay 0 MPLS Any Transport over 57

58 Any MPLS over Transport in xconnect Values for L2VPN Configuring Example: Interworking Mode Configuration MTU xconnect 123 pw-class atom-ipiw 10.1.1.152 ! Serial4/0/0 interface 255.255.255.252 10.151.100.1 ip address ppp encapsulation ip mpls serial restart-delay 0 ! ospf 1 router log-adjacency-changes network 0 area 0.0.0.0 10.1.1.151 area network 10.151.100.0 0.0.0.3 0 ! ldp router-id Loopback0 mpls PE2 Configuration pseudowire-class atom-ipiw encapsulation mpls interworking ip ! interface Loopback0 255.255.255.255 10.1.1.152 ip address ! FastEthernet0/0/0 interface no ip address atom-ipiw 123 pw-class 10.1.1.151 xconnect mtu 1492 ! interface Serial4/0/0 10.100.152.2 255.255.255.252 ip address ppp encapsulation mpls ip serial restart-delay 0 ! ospf 1 router log-adjacency-changes network 10.1.1.152 0.0.0.0 area 0 10.100.152.0 0.0.0.3 area 0 network ! ldp router-id Loopback0 mpls The show mpls l2transport binding command shows that the MTU value for the local and remote routers is 1492 bytes. PE1 l2transport Router# show mpls binding VC ID: 123 10.1.1.152, Address: Destination Label: 105 Local VC Type: 1, Cbit: GroupID: PPP, 0 n/a MTU: 1492, Desc: Interface RA [2] CW [1], CC Type: VCCV: [2] LSPV CV Type: 205 Label: Remote GroupID: VC Type: 1, 0 Cbit: FastEthernet, Desc: n/a MTU: 1492, Interface VCCV: CC Type: RA [2] LSPV CV Type: [2] vc detail Router# show mpls l2transport up, line Serial2/0/0 interface: protocol up, PPP up Local Transport Any MPLS over 58

59 Any MPLS over Transport in xconnect Values for L2VPN Configuring Example: Interworking Mode Configuration MTU interworking type is IP MPLS is PPP, VC type up VC status: VC ID: 123, 10.1.1.152, address: Destination 205} stack label imposed Serial4/0/0, interface: Output {1003 Preferred not configured path: active path: Default point2point hop: Next change time: Create status last 00:25:29, time: 00:24:54 protocol: Signaling LDP, peer up 10.1.1.152:0 Hello: Targeted Id) -> 10.1.1.152 10.1.1.151(LDP (local/remote) Status TLV support : enabled/supported machine : established, state LruRru Label/status no fault Last local dataplane status rcvd: rcvd: Last local SSS circuit status no fault status sent: no fault Last local SSS circuit no fault Last local LDP TLV status sent: no fault rcvd: status LDP TLV remote Last remote MPLS VC labels: local 205 105, 0 Group ID: local n/a, remote local 1492, remote 1492 MTU: description: interface Remote Sequencing: receive disabled, send disabled VC statistics: receive 30, send 29 packet totals: receive 3364 send 2946, totals: byte 0 0, send receive drops: packet PE2 show mpls l2transport Router# binding 10.1.1.151, Address: Destination VC ID: 123 Local Label: 205 VC Type: FastEthernet, GroupID: 0 Cbit: 1, n/a MTU: 1492, Desc: Interface VCCV: RA [2] CC Type: LSPV CV Type: [2] Label: 105 Remote GroupID: 1, VC Type: FastEthernet, Cbit: 0 Interface MTU: 1492, Desc: n/a CW [1], VCCV: CC Type: RA [2] [2] LSPV CV Type: vc detail l2transport mpls show Router# up, FastEthernet Local up, line up Fe0/0/0 interface: protocol MPLS interworking is FastEthernet, VC type type is IP up address: 10.1.1.151, VC ID: 123, VC status: Destination stack {1002 label 105} Output imposed Se4/0/0, interface: not configured path: Preferred active path: Default point2point hop: Next time: 00:25:19 Create time: 00:25:19, last status change LDP, Signaling protocol: peer up 10.1.1.151:0 Hello: Targeted Id) -> 10.1.1.151 10.1.1.152(LDP (local/remote) Status TLV support : enabled/supported : established, LruRru Label/status state machine no fault local dataplane status rcvd: Last local Last SSS circuit status rcvd: no fault no fault local status sent: Last SSS circuit local no fault sent: status Last LDP TLV Last no fault rcvd: status LDP TLV remote 205, VC labels: remote local 105 MPLS ID: local Group remote 0 n/a, remote 1492 MTU: local 1492, Remote interface description: send disabled, disabled Sequencing: receive MPLS Any Transport over 59

60 Any MPLS over Transport Associated Commands Using Interworking for L2VPN Mode Protocol-Based in xconnect Values MTU Configuring Example: Feature L2VPN with Configuration VC statistics: packet totals: receive 29, send 30 2900, 3426 send byte receive totals: 0 packet drops: receive 0, send in xconnect Values Configuration for L2VPN MTU Configuring Example: Mode Commands Associated Using Interworking with L2VPN Protocol-Based Feature configured example showsanL2VPN Interworking example. ThePE1routerhasaserialinterface Thefollowing configuration with an MTU value of 1492 bytes. The PE2 router uses xconnect MTU mode to set a matching VC. If the PE2 router did not set the of 1492 bytes, which allows the two routers to form an interworking mode, the interface would be set to 1500 bytes by default and the VC configuration MTU value in xconnect would not come up. PE1 Configuration pseudowire atom-ipiw template type encapsulation mpls interworking ip ! interface Loopback0 ip address 10.1.1.151 255.255.255.255 ! Serial2/0/0 interface mtu 1492 no ip address ppp encapsulation no fair-queue serial restart-delay 0 pseudowire interface 100 source template type pseudowire atom-ipiw 10.1.1.152 123 neighbor ! l2vpn xconnect context con1 member member pseudowire 100 ! interface Serial4/0/0 ip address 10.151.100.1 255.255.255.252 ppp encapsulation mpls ip serial restart-delay 0 ! 1 ospf router log-adjacency-changes network 10.1.1.151 0.0.0.0 area 0 area network 10.151.100.0 0.0.0.3 0 ! mpls Loopback0 ldp router-id PE2 Configuration type pseudowire atom-ipiw template mpls encapsulation interworking ip ! Loopback0 interface 10.1.1.152 255.255.255.255 ip address Transport Any MPLS over 60

61 Any MPLS over Transport Associated Commands Using Interworking for L2VPN Mode Protocol-Based in xconnect Values MTU Configuring Example: Feature L2VPN with Configuration ! interface FastEthernet0/0/0 no ip address interface pseudowire 100 pseudowire source template atom-ipiw type neighbor 10.1.1.151 123 ! con1 l2vpn xconnect context member pseudowire1 member ! interface Serial4/0/0 ip address 10.100.152.2 255.255.255.252 encapsulation ppp ip mpls serial restart-delay 0 ! router ospf 1 log-adjacency-changes 10.1.1.152 network 0.0.0.0 0 area 10.100.152.0 0.0.0.3 area 0 network ! mpls ldp router-id Loopback0 The is 1492 show l2vpn binding command routers shows that the MTU value for the local and remote atom bytes. PE1 show Device# binding l2vpn atom VC ID: 123 Destination Address: 10.1.1.152, 105 Local Label: GroupID: Cbit: 1, VC Type: PPP, 0 1492, Interface Desc: n/a MTU: CC Type: CW [1], RA [2] VCCV: [2] CV Type: LSPV Remote Label: 205 Cbit: 1, VC Type: FastEthernet, GroupID: 0 Interface n/a Desc: MTU: 1492, CC Type: VCCV: RA [2] CV Type: LSPV [2] show vc detail atom l2vpn Device# Serial2/0/0 up, PPP up Local interface: protocol up, line is PPP, interworking type is IP MPLS VC type up address: 10.1.1.152, VC ID: 123, VC status: Destination Output interface: Serial4/0/0, imposed label stack {1003 205} Preferred path: not configured Default path: active point2point Next hop: Create time: 00:25:29, last status 00:24:54 time: change LDP, protocol: Signaling up 10.1.1.152:0 peer Id) -> 10.1.1.152 Targeted Hello: 10.1.1.151(LDP (local/remote) : enabled/supported Status TLV support Label/status machine : established, LruRru state local no fault rcvd: status dataplane Last Last no fault rcvd: status SSS circuit local no fault Last local SSS circuit status sent: LDP TLV status sent: no fault Last local no fault remote LDP TLV status rcvd: Last 105, MPLS VC labels: local remote 205 n/a, 0 remote Group ID: local 1492 remote local 1492, MTU: description: interface Remote MPLS Transport Any over 61

62 Any MPLS over Transport (AToM) MPLS over Port Any Configuring Examples: Shutdown Ethernet Remote Transport send disabled Sequencing: disabled, receive VC statistics: 29 30, send receive totals: packet 3364 byte send 2946, receive totals: 0, send drops: packet 0 receive PE2 Device# show l2vpn binding atom Address: Destination VC ID: 123 10.1.1.151, 205 Local Label: FastEthernet, GroupID: VC Type: 1, Cbit: 0 n/a Desc: Interface 1492, MTU: CC Type: VCCV: RA [2] CV Type: LSPV [2] Remote Label: 105 1, 0 VC Type: Cbit: GroupID: FastEthernet, n/a MTU: 1492, Interface Desc: CC Type: CW [1], RA [2] VCCV: [2] LSPV CV Type: vc detail l2vpn show Device# atom Fe0/0/0 up, line protocol up, FastEthernet up Local interface: is IP VC type is FastEthernet, interworking type MPLS Destination address: 10.1.1.151, VC ID: 123, VC status: up 105} label {1002 Output interface: Se4/0/0, imposed stack Preferred path: not configured Default path: active point2point hop: Next time: 00:25:19, time: Create 00:25:19 change status last up 10.1.1.151:0 peer LDP, protocol: Signaling Id) -> 10.1.1.151 Targeted Hello: 10.1.1.152(LDP TLV support (local/remote) : enabled/supported Status : established, Label/status state machine LruRru Last local dataplane status rcvd: no fault no fault Last SSS circuit status rcvd: local Last no fault sent: status SSS circuit local no fault Last sent: status LDP TLV local status rcvd: Last remote LDP TLV no fault VC labels: local 205, remote 105 MPLS Group 0 remote ID: local n/a, 1492 remote local MTU: 1492, Remote description: interface send Sequencing: receive disabled, disabled VC statistics: 29, send packet totals: receive 30 2900, send 3426 byte totals: receive drops: receive 0, send 0 packet Any Transport Configuring Examples: over MPLS (AToM) Remote Ethernet Port Shutdown Ethernet port shutdown: example The following shows how to enable remote terminal configure ! eompls pseudowire-class mpls encapsulation ! GigabitEthernet1/0/0 interface Any MPLS over Transport 62

63 Any MPLS over Transport Associated Commands Using Shutdown Port Ethernet Remote Protocol-Based MPLS over Transport Any Configuring Examples: Feature L2VPN with (AToM) xconnect 1 pw-class eompls 10.1.1.1 remote link failure notification The following example shows how to disable remote Ethernet port shutdown: configure terminal ! pseudowire-class eompls encapsulation mpls ! GigabitEthernet1/0/0 interface 1 pw-class eompls xconnect 10.1.1.1 link notification failure no remote command show The related output reports operational status for all remote L2 Tunnels by interface. Router# interface G1/0/0 show GigabitEthernet1/0/0 is up remote down, line protocol is L2 Tunnel is GigMac GigabitEthernet, address is 0003.ff4e.12a8 4 Port (bia 0003.ff4e.12a8) Hardware Internet address is 10.9.9.2/16 1/255 load 255/255, rely DLY 10 usec, Kbit, BW 1000000 bytes, MTU 1500 ip interface Router# show brief Status Protocol Interface IP-Address OK? Method GigabitEthernet2/0/0 unassigned YES NVRAM L2 Tunnel remote down up administratively unassigned down down GigabitEthernet2/1/0 YES NVRAM Note is configured. Remote Ethernet port shutdown is enabled by default when EVC "default encapsulation" MPLS (AToM) Remote Ethernet Port Examples: Configuring Any Transport over Feature Using Commands Associated with L2VPN Protocol-Based Shutdown The following example shows how to enable remote Ethernet port shutdown: configure terminal ! template type pseudowire eompls encapsulation mpls ! GigabitEthernet1/0/0 interface 100 pseudowire interface eompls pseudowire template source type neighbor 10.1.1.1 1 ! context con1 l2vpn xconnect remote link failure notification shows how to disable remote Ethernet example The following port shutdown: configure terminal ! template type pseudowire eompls mpls encapsulation ! GigabitEthernet1/0/0 interface 100 pseudowire interface template eompls pseudowire type source Transport MPLS Any over 63

64 MPLS over Transport Any MPLS over Transport for Any References Additional 1 neighbor 10.1.1.1 ! con1 context xconnect l2vpn notification failure link no remote L2 Tunnels by interface. show operational status for all remote command The related output reports G1/0/0 interface show Router# GigabitEthernet1/0/0 line protocol down, remote is L2 Tunnel is up is 0003.ff4e.12a8 (bia 0003.ff4e.12a8) Hardware GigabitEthernet, address 4 Port is GigMac Internet address is 10.9.9.2/16 Kbit, 1/255 255/255, rely DLY 10 usec, load BW 1000000 bytes, MTU 1500 show brief ip interface Router# IP-Address OK? Method Status Protocol Interface up GigabitEthernet2/0/0 unassigned YES NVRAM L2 Tunnel remote down down GigabitEthernet2/1/0 unassigned YES NVRAM administratively down Additional References for Any Transport MPLS over Documents Related Related Title Document Topic Cisco IOS commands Cisco IOS Master List, All Releases Command MPLS commands Command CiscoIOSMultiprotocol LabelSwitching Reference Technical Assistance Link Description provides http://www .cisco.com/cisco/web/support/index.html TheCiscoSupport andDocumentation website software, documentation, todownload onlineresources to install and configure and tools. Use these resources technical and resolve and to troubleshoot the software issueswithCiscoproducts to andtechnologies. Access most tools on the Cisco Support and Documentation website requires a Cisco.com user ID and password. Transport over MPLS Feature Information for Any The following This in this module. described or features about the feature information table provides release support for a given feature in a given software release table lists only the software release that introduced subsequent train. Unless noted otherwise, releases of that software release train also support that feature. image support. to find information support and Cisco software Use Cisco Feature about platform Navigator on Cisco.com is not required. . An account , go to www.cisco.com/go/cfn Navigator To access Cisco Feature Transport Any over MPLS 64

65 MPLS over Transport Any MPLS over Transport for Any Information Feature Transport over MPLS Table Information for Any 7: Feature Information Name Feature Releases Feature overMPLS AnyTransport Cisco IOS XE Release on the Cisco ASR 920 was introduced This feature (ASR-920-12CZ-A, 3.13.0S Routers ASR-920-12CZ-D, ASR-920-4SZ-A, ASR-920-4SZ-D). MPLS over Transport Any 65

66 over Any Transport MPLS for Any MPLS over Information Transport Feature Transport MPLS over Any 66

Related documents

doj final opinion

doj final opinion

UNITED STAT ES DIS TRICT COURT IC F OR THE D ISTR T OF CO LU M BIA UNITED STAT F AMERICA, : ES O : : la in t if f, P 99 No. on cti l A vi Ci : 96 (GK) -24 : and : TOBACCO-F UND, : REE KIDS ACTION F : ...

More info »
342&343 MP 2018

342&343 MP 2018

न ई NEW DELHI . /Petition No.: 342 /MP/2018 and 343 /MP/2018 /Coram: . . , /Shri P. K. Pujari, Chairperson . ए . , / Dr. M.K. Iyer, Member . , . ए I.S. Jha, Member Sh. / आ ई . nd of May आ न 2 / Date o...

More info »
Detailed Directory of Business Managers

Detailed Directory of Business Managers

Detailed Directory of Business Managment by Cluster, Area and Org Un *** Function Code: AQ - Acquisitions, BL - Billings, BP - Biweekly Payroll, GN - General, MP - Monthly Payroll, TR - Travel Please ...

More info »
Detailed Directory of Business Managers

Detailed Directory of Business Managers

Detailed Directory of Business Managment by Cluster, Area and Org Un *** Function Code: AQ - Acquisitions, BL - Billings, BP - Biweekly Payroll, GN - General, MP - Monthly Payroll, TR - Travel Please ...

More info »
ayout 1

ayout 1

0465039146-FM:FM 12/5/06 12:25 AM Page i C O D E

More info »
Security and Privacy Controls for Federal Information Systems and Organizations

Security and Privacy Controls for Federal Information Systems and Organizations

-53 NIST Special Publication 800 Revision 4 Security and Privacy Controls for Federal Information Systems and Organizations JOINT TASK FORCE TRANSFORMATION INITIATIVE This publication is available fre...

More info »
Federally Available Data (FAD) Resource Document

Federally Available Data (FAD) Resource Document

Federally Available Data Resource Document 04/01/2019 FEDER ALLY AVAILABLE DATA (FAD) RESOURCE Release Version DOCUMENT April 1, 2019 This document provides detailed data notes, FAD availability, stra...

More info »
AcqKnowledge 4 Software Guide

AcqKnowledge 4 Software Guide

® Acq 4 Software G uide Knowledge Check BIOPAC.COM > Sup port > Manuals for updates For Life Science Research Applications Data Acquisition and Analysis with BIOPAC Hardware Systems Reference Manual f...

More info »
OCS Operations Field Directory

OCS Operations Field Directory

Gulf of Mexico OCS Region OCS Operations Field Directory (Includes all active and expired fields and leases) Quarterly Repor t, as of March 31 , 201 9 U.S. Department of the Interior Bureau of Ocean E...

More info »
DODF 082 03 05 2019 INTEGRA

DODF 082 03 05 2019 INTEGRA

o - 82 ANO XLVIII EDIÇÃO N BRASÍLIA - DF, SEXTA-FEIRA, 3 DE MAIO DE 2019 PODER EXECUTIVO SUMÁRIO SEÇÃO II SEÇÃO III SEÇÃO I PÁG. PÁG. PÁG. Poder Legislativo ... 44 . 1 DECRETO Nº 39.797, DE 02 DE MAIO...

More info »
Wilshire Community Plan

Wilshire Community Plan

W I RE IL SH l u n i t y P m a n C m o BLE O T CONT E NTS A F C TIV I TY A L OG M U NI T Y P L A N M C O I. I ntroduct i on II. F un c t i o n of the C o mm unity P l a n II I . L a nd Us e P oli c ie...

More info »
migrationprofileguide2012 1oct2012

migrationprofileguide2012 1oct2012

MIGRATION PROFILES : MIGRATION PROFILES : Making the Most of the Process Making the Most of the Process MIGRATION PROFILES - Making the Most of the Process 17 route des Morillons CH-1211 Geneva 19, Sw...

More info »
24040709 RTCA System Software Manual.indb

24040709 RTCA System Software Manual.indb

RTCA Software Manual Version November 2009 Software Version 1.2 2 4 0 4 0 7 0 9 R T C A S y s t e m S o f t w a r e M a 21.09.2009 16:09:45 u a l . i n d b 1 24040709 RTCA System Software Manual.indb ...

More info »
handbook

handbook

258 P PM 02 : 12 age 12/22/05 d .qx 06 _c 1 am d CH R 6 APT E e Dy e i r o s h ems T st namic Sy N a I T H LEN E TH R E STH E D nd LI A B . SM iv P t f rom a Dy n a m i c Sy s tems De v elo pm 276 e e...

More info »
20 Jul Prof Sarah Childs The Good Parliament report

20 Jul Prof Sarah Childs The Good Parliament report

The Good Parliament Professor Sarah Childs July 2016

More info »
PowerPoint Presentation

PowerPoint Presentation

Abdullah Mueen Eamonn Keogh Time Series Data Mining Using the Matrix Profile: A Unifying View of Motif Discovery, Anomaly Detection, Segmentation, Classification, Clustering and Similarity Joins We wi...

More info »
5 6 Inequalities in Two Triangles

5 6 Inequalities in Two Triangles

Compare the given measures. m m ACB GDE 1. and SOLUTION: , and and In AB > EG . By the converse of the Hinge Theorem, ANSWER: ACB m > GDE m and 2. KM JL SOLUTION: , In and and . By the Hinge Theorem, ...

More info »
c9nj00028c1

c9nj00028c1

Chemistry. of Journal New for (ESI) Material Supplementary Electronic 2019 is journal This The Recherche © Royal Society of Chemistry and the Centre National de la Scientifique Supporting Information ...

More info »
508Chap4book.book

508Chap4book.book

U.S. Geological Survey Techniques of Water-Resources Investigations Book 9 Handbooks for Water-Resources Investigations National Field Manual for the Collection of Water-Quality Data Chapter A4. COLLE...

More info »