Downloads |
Table Of Contents
Prerequisites for Any Transport over MPLS
Restrictions for Any Transport over MPLS
ATM AAL5 over MPLS Restrictions
ATM Cell Relay over MPLS Restrictions
Ethernet over MPLS (EoMPLS) Restrictions
Per-Subinterface MTU for Ethernet over MPLS Restrictions
Frame Relay over MPLS Restrictions
Experimental Bits with AToM Restrictions
Remote Ethernet Port Shutdown Restrictions
Information About Any Transport over MPLS
How AToM Transports Layer 2 Packets
MPLS Traffic Engineering Fast Reroute
Maximum Transmission Unit Guidelines for Estimating Packet Size
Estimating Packet Size: Example
Per-Subinterface MTU for Ethernet over MPLS
Frame Relay over MPLS and DTE, DCE, and NNI Connections
Local Management Interface and Frame Relay over MPLS
QoS Features Supported with AToM
OAM Cell Emulation for ATM AAL5 over MPLS
OAM Cell Emulation for ATM AAL5 over MPLS in VC Class Configuration Mode
Any Transport over MPLS (AToM): Remote Ethernet Port Shutdown
AToM Load Balancing with Single PW
How to Configure Any Transport over MPLS
Configuring the Pseudowire Class
Changing the Encapsulation Type and Removing a Pseudowire
Configuring ATM AAL5 over MPLS
Configuring ATM AAL5 over MPLS on PVCs
Configuring ATM AAL5 over MPLS in VC Class Configuration Mode
Configuring OAM Cell Emulation for ATM AAL5 over MPLS
Configuring OAM Cell Emulation for ATM AAL5 over MPLS on PVCs
Configuring OAM Cell Emulation for ATM AAL5 over MPLS in VC Class Configuration Mode
Configuring ATM Cell Relay over MPLS
Configuring ATM Cell Relay over MPLS in VC Mode
Configuring ATM Cell Relay over MPLS in VC Mode Using VC Class Configuration Mode
Configuring ATM Cell Relay over MPLS in PVP Mode
Configuring Ethernet over MPLS
Configuring Ethernet over MPLS in Port Mode
Configuring Ethernet over MPLS with VLAN ID Rewrite
Configuring per-Subinterface MTU for Ethernet over MPLS
Configuring Frame Relay over MPLS
Configuring Frame Relay over MPLS with DLCI-to-DLCI Connections
Configuring Frame Relay over MPLS with Port-to-Port Connections
Configuring HDLC or PPP over MPLS
Setting Experimental Bits with AToM
Configuring MPLS AToM Remote Ethernet Port Shutdown
Configuring AToM Load Balancing with Single PW
Configuration Examples for Any Transport over MPLS
Example: Configuring ATM AAL5 over MPLS in VC Class Configuration Mode
Example: Ethernet over MPLS with MPLS Traffic Engineering Fast Reroute
Example: Configuring OAM Cell Emulation
Example: Configuring ATM Cell Relay over MPLS
Example: Configuring per-Subinterface MTU for Ethernet over MPLS
Example: Configuring MTU Values in xconnect Configuration Mode for L2VPN Interworking
Examples: Configuring Any Transport over MPLS (AToM): Remote Ethernet Port Shutdown
Feature Information for Any Transport over MPLS
Any Transport over MPLS
First Published: January 1, 2001Last Updated: July 15, 2011This module describes how to configure Any Transport over MPLS (AToM) transports data link layer (Layer 2) packets over a Multiprotocol Label Switching (MPLS) backbone. AToM enables service providers to connect customer sites with existing Layer 2 networks by using a single, integrated, packet-based network infrastructure—a Cisco MPLS network. Instead of using separate networks with network management environments, service providers can deliver Layer 2 connections over an MPLS backbone. AToM provides a common framework to encapsulate and transport supported Layer 2 traffic types over an MPLS network core.
AToM supports the following like-to-like transport types:
•
ATM Adaptation Layer Type-5 (AAL5) over MPLS
•
•
•
•
•
Finding Feature Information
Your software release may not support all the features documented in this module. For the latest feature information and caveats, see the release notes for your platform and software release. To find information about the features documented in this module, and to see a list of the releases in which each feature is supported, see the "Feature Information for Any Transport over MPLS" section.
Use Cisco Feature Navigator to find information about platform support and Cisco software image support. To access Cisco Feature Navigator, go to http://www.cisco.com/go/cfn. An account on Cisco.com is not required.
Contents
•
•
•
•
•
•
Prerequisites for Any Transport over MPLS
•
•
•
•
•
•
Restrictions for Any Transport over MPLS
•
•
•
•
•
•
•
•
General Restrictions
•
•
•
ATM AAL5 over MPLS Restrictions
•
ATM Cell Relay over MPLS Restrictions
•
•
•
•
For configuring ATM cell relay over MPLS in VP mode, the following restrictions apply:
•
•
•
Ethernet over MPLS (EoMPLS) Restrictions
•
•
•
•
•
Per-Subinterface MTU for Ethernet over MPLS Restrictions
•
–
–
–
•
–
–
•
•
•
Frame Relay over MPLS Restrictions
Frame Relay traffic shaping is not supported with AToM switched VCs.
HDLC over MPLS Restrictions
•
•
PPP over MPLS Restrictions
•
•
•
•
Tunnel Selection Restrictions
•
•
•
•
Experimental Bits with AToM Restrictions
•
•
•
•
Remote Ethernet Port Shutdown Restrictions
This feature is not symmetrical if the remote PE router is running an older version image or is on another platform that does not support the EoMPLS remote Ethernet port shutdown feature and the local PE is running an image which supports this feature.
Information About Any Transport over MPLS
To configure AToM, you must understand the following concepts:
•
•
•
•
•
•
•
•
•
How AToM Transports Layer 2 Packets
AToM encapsulates Layer 2 frames at the ingress PE and sends them to a corresponding PE at the other end of a pseudowire, which is a connection between the two PE routers. The egress PE removes the encapsulation and sends out the Layer 2 frame.
The successful transmission of the Layer 2 frames between PE routers is due to the configuration of the PE routers. You set up the connection, called a pseudowire, between the routers. You specify the following information on each PE router:
•
•
•
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.
Step 1 defines the interface or subinterface on the PE router:
Router# interface interface-type interface-numberStep 2 specifies the encapsulation type for the interface, such as dot1q:
Router(config-if)# encapsulation encapsulation-typeStep 3 does the following:
•
•
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.
•
Router(config-if)# xconnect peer-router-id vcid encapsulation mplsAs an alternative, you can set up a pseudowire class to specify the tunneling method and other characteristics. For more information, see the "Configuring the Pseudowire Class" section.
Benefits of AToM
The following list explains some of the benefits of enabling Layer 2 packets to be sent in the MPLS network:
•
•
•
MPLS Traffic Engineering Fast Reroute
AToM can use MPLS traffic engineering (TE) tunnels with fast reroute (FRR) support. AToM VCs can be rerouted around a failed link or node at the same time as MPLS and IP prefixes.
Enabling fast reroute on AToM does not require any special commands; you can use standard fast reroute commands. At the ingress PE, an AToM tunnel is protected by fast reroute when it is routed to an FRR-protected TE tunnel. Both link and node protection are supported for AToM VCs at the ingress PE.
In the following example, the primary link is disabled, which causes the backup tunnel (Tunnel 1) to become the primary path. The output in boldface font shows the status of the tunnel:
Router# execute-on slot 3 debug mpls l2transport fast-reroute========= Line Card (Slot 3) =========AToM fast reroute debugging is onSLOT 3:Sep 16 17:58:56.346: AToM SMGR: Processing TFIB FRR event for 10.4.0.1SLOT 3:Sep 16 17:58:56.346: AToM SMGR: Finished processing TFIB FRR event for 10.4.0.1SLOT 3:Sep 16 17:58:56.346: AToM SMGR: Processing TFIB FRR event for Tunnel41SLOT 3:Sep 16 17:58:56.346: AToM SMGR: Finished processing TFIB FRR event for Tunnel41Sep 16 17:58:58.342: %LINK-3-UPDOWN: Interface POS0/0/0, changed state to downSep 16 17:58:58.342: %OSPF-5-ADJCHG: Process 1, Nbr 10.0.0.1 on POS0/0 from FULL to DOWN, Neighbor Down: Interface down or detachedSep 16 17:58:59.342: %LINEPROTO-5-UPDOWN: Line protocol on Interface POS0/0/0, changed state to downMaximum Transmission Unit Guidelines for Estimating Packet Size
The following calculation helps you determine the size of the packets traveling through the core network. You set the maximum transmission unit (MTU) on the core-facing interfaces of the P and PE routers to accommodate packets of this size. The MTU should be greater than or equal to the total bytes of the items in the following equation:
Core MTU >= (Edge MTU + Transport header + AToM header + (MPLS label stack * MPLS label size))The following sections describe the variables used in the equation.
Edge MTU
The edge MTU is the MTU for the customer-facing interfaces.
Transport Header
The Transport header depends on the transport type. Table 1 lists the specific sizes of the headers.
AToM Header
The AToM header is 4 bytes (control word). The control word is optional for Ethernet, PPP, HDLC, and cell relay transport types. The control word is required for Frame Relay and ATM AAL5 transport types.
MPLS Label Stack
The MPLS label stack size depends on the configuration of the core MPLS network:
•
•
•
•
•
•
•
Other circumstances can increase the MPLS label stack size. Therefore, analyze the complete data path between the AToM tunnel endpoints and determine the maximum MPLS label stack size for your network. Then multiply the label stack size by the size of the MPLS label.
Estimating Packet Size: Example
The estimated packet size in the following example is 1526 bytes, based on the following assumptions:
•
•
•
•
Edge MTU + Transport header + AToM header + (MPLS label stack * MPLS label) = Core MTU1500 + 18 + 0 + (2 * 4 ) = 1526You must configure the P and PE routers in the core to accept packets of 1526 bytes.
Per-Subinterface MTU for Ethernet over MPLS
Cisco IOS XE software includes the ability to specify MTU values in xconnect subinterface configuration mode. When you use xconnect subinterface configuration mode to set the MTU value, you establish a pseudowire connection for situations where the interfaces have different MTU values that cannot be changed.
If you specify an MTU value in xconnect subinterface configuration mode that is outside the range of supported MTU values (64 bytes to the maximum number of bytes supported by the interface), the command might be rejected. If you specify an MTU value that is out of range in xconnect subinterface configuration mode, the router enters the command in subinterface configuration mode.
For example, if you specify an MTU of 1501 in xconnect subinterface configuration mode, and that value is out of range, the router enters the command in subinterface configuration mode, where it is accepted:
Router# configure terminalRouter(config)# interface gigabitethernet0/0/2.1Router(config-subif)# xconnect 10.10.10.1 100 encapsulation mplsRouter(config-subif-xconn)# mtu ?<64 - 1500> MTU size in bytesRouter(config-subif-xconn)# mtu 1501 <<================Router(config-subif)# mtu ?<64 - 17940> MTU size in bytesIf the MTU value is not accepted in either xconnect subinterface configuration mode or subinterface configuration mode, then the command is rejected.
Frame Relay over MPLS and DTE, DCE, and NNI Connections
You can configure an interface as a DTE device or a DCE switch, or as a switch connected to a switch with network-to-network interface (NNI) connections. Use the following command in interface configuration mode:
frame-relay intf-type [dce | dte | nni]
The keywords are explained in Table 2.
.
Local Management Interface and Frame Relay over MPLS
Local Management Interface (LMI) is a protocol that communicates status information about PVCs. When a PVC is added, deleted, or changed, the LMI notifies the endpoint of the status change. LMI also provides a polling mechanism that verifies that a link is up.
How LMI Works
To determine the PVC status, LMI checks that a PVC is available from the reporting device to the Frame Relay end-user device. If a PVC is available, LMI reports that the status is "Active," which means that all interfaces, line protocols, and core segments are operational between the reporting device and the Frame Relay end-user device. If any of those components is not available, the LMI reports a status of "Inactive."
Note
Figure 1 is a sample topology that helps illustrate how LMI works.
Figure 1 Sample Topology
In Figure 1, note the following:
•
•
•
•
The LMI protocol behavior depends on whether you have DLCI-to-DLCI or port-to-port connections.
DLCI-to-DLCI Connections
If you have DLCI-to-DLCI connections, LMI runs locally on the Frame Relay ports between the PE and CE devices:
•
•
–
–
–
For DTE or DCE configurations, the following LMI behavior exists: The Frame Relay device accessing the network (DTE) does not report PVC status. Only the network device (DCE) or NNI can report status. Therefore, if a problem exists on the DTE side, the DCE is not aware of the problem.
Port-to-Port Connections
If you have port-to-port connections, the PE routers do not participate in the LMI status-checking procedures. LMI operates between the CE routers only. The CE routers must be configured as DCE-DTE or NNI-NNI.
QoS Features Supported with AToM
The following tables list the QoS features supported by AToM:
•
•
•
OAM Cell Emulation for ATM AAL5 over MPLS
If a PE router does not support the transport of Operation, Administration, and Maintenance (OAM) cells across a label switched path (LSP), you can use OAM cell emulation to locally terminate or loop back the OAM cells. You configure OAM cell emulation on both PE routers, which emulates a VC by forming two unidirectional LSPs. You use Cisco software commands on both PE routers to enable OAM cell emulation.
After you enable OAM cell emulation on a router, you can configure and manage the ATM VC in the same manner as you would a terminated VC. A VC that has been configured with OAM cell emulation can send loopback cells at configured intervals toward the local CE router. The endpoint can be either of the following:
•
•
The OAM cells include the following cells:
•
•
These cells identify and report defects along a VC. When a physical link or interface failure occurs, intermediate nodes insert OAM AIS cells into all the downstream devices affected by the failure. When a router receives an AIS cell, it marks the ATM VC down and sends an RDI cell to let the remote end know about the failure.
OAM Cell Emulation for ATM AAL5 over MPLS in VC Class Configuration Mode
You can configure OAM cell emulation as part of a VC class and then apply the VC class to an interface, a subinterface, or a VC. When you configure OAM cell emulation in VC class configuration mode and then apply the VC class to an interface, the settings in the VC class apply to all the VCs on the interface, unless you specify a different OAM cell emulation value at a lower level, such as the subinterface or VC level. For example, you can create a VC class that specifies OAM cell emulation and sets the rate of AIS cells to every 30 seconds. You can apply the VC class to an interface. Then, for one PVC, you can enable OAM cell emulation and set the rate of AIS cells to every 15 seconds. All the PVCs on the interface use the cell rate of 30 seconds, except for the one PVC that was set to 15 seconds.
Any Transport over MPLS (AToM): Remote Ethernet Port Shutdown
This Cisco IOS XE feature allows a service provider edge (PE) router on the local end of an Ethernet over MPLS (EoMPLS) pseudowire to detect a remote link failure and cause the shutdown of the Ethernet port on the local customer edge (CE) router. Because the Ethernet port on the local CE router is shut down, the router does not lose data by continuously sending traffic to the failed remote link. This is beneficial if the link is configured as a static IP route.
Figure 2 illustrates a condition in an EoMPLS WAN, with a down Layer 2 tunnel link between a CE router (Customer Edge 1) and the PE router (Provider Edge 1). A CE router on the far side of the Layer 2 tunnel (Customer Edge 2), continues to forward traffic to Customer Edge 1 through the L2 tunnel.
Figure 2 Remote Link Outage in EoMPLS WAN
Previous to this feature, the Provider Edge 2 router could not detect a failed remote link. Traffic forwarded from Customer Edge 2 to Customer Edge 1 would be lost until routing or spanning tree protocols detected the down remote link. If the link was configured with static routing, the remote link outage would be even more difficult to detect.
With this feature, the Provider Edge 2 router detects the remote link failure and causes a shutdown of the local Customer Edge 2 Ethernet port. When the remote L2 tunnel link is restored, the local interface is automatically restored as well. The possibility of data loss is thus diminished.
With reference to Figure 2, the Remote Ethernet Shutdown sequence is generally described as follows:
1.
2.
3.
4.
5.
6.
This feature is enabled by default for Ethernet over MPLS (EoMPLS). You can also enable this feature by using the remote link failure notification command in xconnect configuration mode as shown in the following example:
pseudowire-class eomplsencapsulation mpls!interface GigabitEthernet1/0/0xconnect 10.13.13.13 1 pw-class eomplsremote link failure notification!This feature can be disabled using the no remote link failure notification command in xconnect configuration mode. Use the show ip interface brief privileged EXEC command to display the status of all remote L2 tunnel links. Use the show interface privileged EXEC command to show the status of the L2 tunnel on a specific interface.
Note
AToM Load Balancing with Single PW
Prior to Cisco IOS XE Release 3.4S, the Cisco ASR 1000 Series Aggregation Services Router did not perform load balancing for packets within the same pseudowire (PW) at the Provide Edge (PE) even if Equal Cost Multiple Paths (ECMPs) were available between PEs in an MPLS cloud. Only one of the routing options from the table would be used, and the other paths would be left unused. The AToM Load Balancing with Single PW feature enables load balancing for packets within the same pseudowire by further classifying packets within the same pseudowire into different flows based on certain fields in the packet received on an attachment circuit. For example, for Ethernet this load balancing is based on the source MAC address in the incoming packets.
In Cisco IOS XE Release 3.4S, this feature is available only for the Ethernet family of attachment circuits (ACs); so the flow-identification logic is based on source MAC address. All packets with the same source MAC address follow one path and are identified as flows.
How to Configure Any Transport over MPLS
This section explains how to perform a basic AToM configuration and includes the following procedures:
•
•
•
•
•
•
•
•
•
•
•
•
•
Configuring the Pseudowire Class
Note
•
% Incomplete command.
SUMMARY STEPS
1.
2.
3.
4.
DETAILED STEPS
Changing the Encapsulation Type and Removing a Pseudowire
Once you specify the encapsulation mpls command, you cannot remove it using the no encapsulation mpls command. Nor can you change the command's setting using the encapsulation l2tpv3 command. Those methods result in the following error message:
Encapsulation changes are not allowed on an existing pw-class.To remove the encapsulation mpls command, you must delete the pseudowire with the no pseudowire-class command.
To change the type of encapsulation, remove the pseudowire using the no pseudowire-class command and reconfigure the pseudowire to specify the new encapsulation type.
Configuring ATM AAL5 over MPLS
•
•
Configuring ATM AAL5 over MPLS on PVCs
SUMMARY STEPS
1.
2.
3.
4.
5.
6.
7.
8.
DETAILED STEPS
Examples
The following is sample output from the show mpls l2transport vc command that shows that ATM AAL5 over MPLS is configured on a PVC:
Router# show mpls l2transport vcLocal intf Local circuit Dest address VC ID Status--------- ------------- ------------ ----- ------ATM1/0 ATM AAL5 1/100 10.4.4.4 100 UPConfiguring ATM AAL5 over MPLS in VC Class Configuration Mode
SUMMARY STEPS
1.
2.
3.
4.
5.
6.
7.
8.
9.
10.
11.
DETAILED STEPS
Examples
In the following example, the command output from the show atm class-links command verifies that ATM AAL5 over MPLS is configured as part of a VC class. The command output shows the type of encapsulation and that the VC class was applied to an interface.
Router# show atm class-links 1/100Displaying vc-class inheritance for ATM1/0/0.0, vc 1/100:no broadcast - Not configured - using defaultencapsulation aal5 - VC-class configured on main interfaceConfiguring OAM Cell Emulation for ATM AAL5 over MPLS
•
•
•
Configuring OAM Cell Emulation for ATM AAL5 over MPLS on PVCs
SUMMARY STEPS
1.
2.
3.
4.
5.
6.
7.
8.
9.
10.
DETAILED STEPS
Examples
The following output from the show atm pvc command shows that OAM cell emulation is enabled on the ATM PVC:
Router# show atm pvc 5/500ATM4/1/0.200: VCD: 6, VPI: 5, VCI: 500UBR, PeakRate: 1AAL5-LLC/SNAP, etype:0x0, Flags: 0x34000C20, VCmode: 0x0OAM Cell Emulation: enabled, F5 End2end AIS Xmit frequency: 1 second(s)OAM frequency: 0 second(s), OAM retry frequency: 1 second(s)OAM up retry count: 3, OAM down retry count: 5OAM Loopback status: OAM DisabledOAM VC state: Not ManagedVerifiedILMI VC state: Not ManagedInPkts: 564, OutPkts: 560, InBytes: 19792, OutBytes: 19680InPRoc: 0, OutPRoc: 0InFast: 4, OutFast: 0, InAS: 560, OutAS: 560InPktDrops: 0, OutPktDrops: 0CrcErrors: 0, SarTimeOuts: 0, OverSizedSDUs: 0Out CLP=1 Pkts: 0OAM cells received: 26F5 InEndloop: 0, F5 InSegloop: 0, F5 InAIS: 0, F5 InRDI: 26OAM cells sent: 77F5 OutEndloop: 0, F5 OutSegloop: 0, F5 OutAIS: 77, F5 OutRDI: 0OAM cell drops: 0Status: UPConfiguring OAM Cell Emulation for ATM AAL5 over MPLS in VC Class Configuration Mode
SUMMARY STEPS
1.
2.
3.
4.
5.
6.
7.
8.
9.
10.
11.
DETAILED STEPS
Configuring ATM Cell Relay over MPLS
•
•
•
Configuring ATM Cell Relay over MPLS in VC Mode
SUMMARY STEPS
1.
2.
3.
4.
5.
6.
7.
8.
DETAILED STEPS
Example
The following sample output from the show atm vc command shows that the interface is configured for VC mode cell relay:
Router# show atm vc 7ATM3/0: VCD: 7, VPI: 23, VCI: 100UBR, PeakRate: 149760AAL0-Cell Relay, etype:0x10, Flags: 0x10000C2D, VCmode: 0x0OAM Cell Emulation: not configuredInBytes: 0, OutBytes: 0Status: UPConfiguring ATM Cell Relay over MPLS in VC Mode Using VC Class Configuration Mode
SUMMARY STEPS
1.
2.
3.
4.
5.
6.
7.
8.
9.
DETAILED STEPS
Configuring ATM Cell Relay over MPLS in PVP Mode
SUMMARY STEPS
1.
2.
3.
4.
5.
6.
7.
DETAILED STEPS
Examples
The following output from the show atm vp command shows that the interface is configured for VP mode cell relay:
Router# show atm vp 1ATM5/0 VPI: 1, Cell Relay, PeakRate: 149760, CesRate: 0, DataVCs: 1, CesVCs: 0, Status: ACTIVEVCD VCI Type InPkts OutPkts AAL/Encap Status6 3 PVC 0 0 F4 OAM ACTIVE7 4 PVC 0 0 F4 OAM ACTIVETotalInPkts: 0, TotalOutPkts: 0, TotalInFast: 0, TotalOutFast: 0,TotalBroadcasts: 0 TotalInPktDrops: 0, TotalOutPktDrops: 0Configuring Ethernet over MPLS
•
•
•
Configuring Ethernet over MPLS in VLAN Mode to Connect Two VLAN Networks That Are in Different Locations.
SUMMARY STEPS
1.
2.
3.
4.
5.
DETAILED STEPS
Configuring Ethernet over MPLS in Port Mode
SUMMARY STEPS
1.
2.
3.
4.
5.
6.
DETAILED STEPS
Examples
The sample output in the following example shows two VCs for Ethernet over MPLS:
•
•
Router# show mpls l2transport vcLocal intf Local circuit Dest address VC ID Status------------- -------------------- --------------- ---------- ----------Gi4/0/0.1 Eth VLAN 2 10.1.1.1 2 UPGi8/0/1 Ethernet 10.1.1.1 8 UPThe sample output from the show mpls l2transport vc detail command displays the same information in a different format:
Router# show mpls l2transport vc detailLocal interface: Gi4/0/0.1 up, line protocol up, Eth VLAN 2 upDestination address: 10.1.1.1, VC ID: 2, VC status: up...Local interface: Gi8/0/1 up, line protocol up, Ethernet upDestination address: 10.1.1.1, VC ID: 8, VC status: upConfiguring Ethernet over MPLS with VLAN ID Rewrite
SUMMARY STEPS
1.
2.
3.
4.
5.
6.
7.
8.
DETAILED STEPS
Examples
The following sample output from the show controllers eompls forwarding-table command shows VLAN ID rewrite configured on a router with an engine 2 3-port Gigabit Ethernet line card. In this example, the output in boldface font shows the VLAN ID rewrite information.
On PE1
Router# execute slot 0 show controllers eompls forwarding-table 0 2Port # 0, VLAN-ID # 2, Table-index 2EoMPLS configured: 1tag_rew_ptr = D001BB58Leaf entry? = 1FCR index = 20**tagrew_psa_addr = 0006ED60**tagrew_vir_addr = 7006ED60**tagrew_phy_addr = F006ED60[0-7] loq 8800 mtu 4458 oq 4000 ai 3 oi 04019110 (encaps size 4)cw-size 4 vlanid-rew 3gather A30 (bufhdr size 32 EoMPLS (Control Word) Imposition profile 81)2 tag: 18 18counters 1182, 10 reported 1182, 10.Local OutputQ (Unicast): Slot:2 Port:0 RED queue:0 COS queue:0Output Q (Unicast): Port:0 RED queue:0 COS queue:0On PE2
Router# execute slot 0 show controllers eompls forwarding-table 0 3Port # 0, VLAN-ID # 3, Table-index 3EoMPLS configured: 1tag_rew_ptr = D0027B90Leaf entry? = 1FCR index = 20**tagrew_psa_addr = 0009EE40**tagrew_vir_addr = 7009EE40**tagrew_phy_addr = F009EE40[0-7] loq 9400 mtu 4458 oq 4000 ai 8 oi 84000002 (encaps size 4)cw-size 4 vlanid-rew 2gather A30 (bufhdr size 32 EoMPLS (Control Word) Imposition profile 81)2 tag: 17 18counters 1182, 10 reported 1182, 10.Local OutputQ (Unicast): Slot:5 Port:0 RED queue:0 COS queue:0Output Q (Unicast): Port:0 RED queue:0 COS queue:0Configuring per-Subinterface MTU for Ethernet over MPLS
SUMMARY STEPS
1.
2.
3.
4.
5.
6.
7.
8.
9.
10.
DETAILED STEPS
Configuring Frame Relay over MPLS
•
•
Configuring Frame Relay over MPLS with DLCI-to-DLCI Connections
SUMMARY STEPS
1.
2.
3.
4.
5.
6.
7.
8.
9.
DETAILED STEPS
Configuring Frame Relay over MPLS with Port-to-Port Connections
SUMMARY STEPS
1.
2.
3.
4.
5.
DETAILED STEPS
Configuring HDLC or PPP over MPLS
SUMMARY STEPS
1.
2.
3.
4.
5.
DETAILED STEPS
Configuring Tunnel Selection
SUMMARY STEPS
1.
2.
3.
4.
5.
6.
7.
8.
9.
DETAILED STEPS
Examples
In the following sample output from the show mpls l2transport vc command incudes the following information about the VCs:
•
•
Command output that is in boldface font shows the preferred path information.
Router# show mpls l2transport vc detailLocal interface: Gi0/0/0.1 up, line protocol up, Eth VLAN 222 upDestination address: 10.16.16.16, VC ID: 101, VC status: upPreferred path: Tunnel1, activeDefault path: disabledTunnel label: 3, next hop point2pointOutput interface: Tu1, imposed label stack {17 16}Create time: 00:27:31, last status change time: 00:27:31Signaling protocol: LDP, peer 10.16.16.16:0 upMPLS VC labels: local 25, remote 16Group ID: local 0, remote 6MTU: local 1500, remote 1500Remote interface description:Sequencing: receive disabled, send disabledVC statistics:packet totals: receive 10, send 10byte totals: receive 1260, send 1300packet drops: receive 0, send 0Local interface: ATM1/0/0 up, line protocol up, ATM AAL5 0/50 upDestination address: 10.16.16.16, VC ID: 150, VC status: upPreferred path: 10.18.18.18, activeDefault path: readyTunnel label: 3, next hop point2pointOutput interface: Tu2, imposed label stack {18 24}Create time: 00:15:08, last status change time: 00:07:37Signaling protocol: LDP, peer 10.16.16.16:0 upMPLS VC labels: local 26, remote 24Group ID: local 2, remote 0MTU: local 4470, remote 4470Remote interface description:Sequencing: receive disabled, send disabledVC statistics:packet totals: receive 0, send 0byte totals: receive 0, send 0packet drops: receive 0, send 0Troubleshooting Tips
You can use the debug mpls l2transport vc event command to troubleshoot tunnel selection. For example, if the tunnel interface that is used for the preferred path is shut down, the default path is enabled.
Examples
Router# debug mpls l2transport vc eventAToM SMGR [10.2.2.2, 101]: Processing imposition update, vc_handle 62091860, update_action 3, remote_vc_label 16AToM SMGR [10.2.2.2, 101]: selected route no parent rewrite: tunnel not upAToM SMGR [10.2.2.2, 101]: Imposition Programmed, Output Interface: Fe3/2/1Setting Experimental Bits with AToM
SUMMARY STEPS
1.
2.
3.
4.
5.
6.
7.
8.
9.
10.
11.
12.
13.
DETAILED STEPS
Enabling the Control Word
SUMMARY STEPS
1.
2.
3.
4.
5.
6.
DETAILED STEPS
Configuring MPLS AToM Remote Ethernet Port Shutdown
Note
SUMMARY STEPS
1.
2.
3.
4.
5.
6.
7.
8.
9.
10.
DETAILED STEPS
Configuring AToM Load Balancing with Single PW
SUMMARY STEPS
1.
2.
3.
4.
5.
6.
DETAILED STEPS
Configuration Examples for Any Transport over MPLS
•
•
•
•
•
•
•
Example: ATM over MPLS
Example 1 shows the configuration of ATM over MPLS on two PE routers.
Example 1 ATM over MPLS Configuration Example
Example: Configuring ATM AAL5 over MPLS in VC Class Configuration Mode
The following example configures ATM AAL5 over MPLS in VC class configuration mode. The VC class is then applied to an interface.
enableconfigure terminalvc-class atm aal5classencapsulation aal5interface atm1/0/0class-int aal5classpvc 1/200 l2transportxconnect 10.13.13.13 100 encapsulation mplsThe following example configures ATM AAL5 over MPLS in VC class configuration mode. The VC class is then applied to a PVC.
enableconfigure terminalvc-class atm aal5classencapsulation aal5interface atm1/0/0pvc 1/200 l2transportclass-vc aal5classxconnect 10.13.13.13 100 encapsulation mplsExample: Ethernet over MPLS with MPLS Traffic Engineering Fast Reroute
The following configuration example and Figure 3 show the configuration of Ethernet over MPLS with fast reroute on AToM PE routers.
Routers PE1 and PE2 have the following characteristics:
•
•
•
Figure 3 Fast Reroute Configuration
PE1 Configurationmpls label protocol ldpmpls traffic-eng tunnelsmpls ldp router-id Loopback1 force!pseudowire-class T41encapsulation mplspreferred-path interface Tunnel41 disable-fallback!pseudowire-class IP1encapsulation mplspreferred-path peer 10.4.0.1 disable-fallback!interface Loopback1ip address 10.0.0.27 255.255.255.255!interface Tunnel1ip unnumbered Loopback1tunnel destination 10.0.0.1tunnel mode mpls traffic-engtunnel mpls traffic-eng priority 1 1tunnel mpls traffic-eng bandwidth 10000tunnel mpls traffic-eng path-option 1 explicit name FRR!interface Tunnel41ip unnumbered Loopback1tunnel destination 10.0.0.4tunnel mode mpls traffic-engtunnel mpls traffic-eng priority 1 1tunnel mpls traffic-eng bandwidth 1000tunnel mpls traffic-eng path-option 1 explicit name name-1tunnel mpls traffic-eng fast-reroute!interface POS0/0/0description pe1name POS8/0/0ip address 10.1.0.2 255.255.255.252mpls traffic-eng tunnelsmpls traffic-eng backup-path Tunnel1crc 16clock source internalpos ais-shutpos report lrdiip rsvp bandwidth 155000 155000!interface POS0/3/0description pe1name POS10/1/0ip address 10.1.0.14 255.255.255.252mpls traffic-eng tunnelscrc 16clock source internalip rsvp bandwidth 155000 155000!interface gigabitethernet3/0/0.1encapsulation dot1Q 203xconnect 10.0.0.4 2 pw-class IP1!interface gigabitethernet3/0/0.2encapsulation dot1Q 204xconnect 10.0.0.4 4 pw-class T41!router ospf 1network 10.0.0.0 0.255.255.255 area 0mpls traffic-eng router-id Loopback1mpls traffic-eng area 0!ip classlessip route 10.4.0.1 255.255.255.255 Tunnel41!ip explicit-path name xxxx-1 enablenext-address 10.4.1.2next-address 10.1.0.10P Configuration
ip cefmpls traffic-eng tunnels!interface Loopback1ip address 10.0.0.1 255.255.255.255!interface FastEthernet1/0/0ip address 10.4.1.2 255.255.255.0mpls traffic-eng tunnelsip rsvp bandwidth 10000 10000!interface POS8/0/0description xxxx POS0/0ip address 10.1.0.1 255.255.255.252mpls traffic-eng tunnelspos ais-shutpos report lrdiip rsvp bandwidth 155000 155000!interface POS10/1/0description xxxx POS0/3ip address 10.1.0.13 255.255.255.252mpls traffic-eng tunnelsip rsvp bandwidth 155000 155000!router ospf 1network 10.0.0.0 0.255.255.255 area 0mpls traffic-eng router-id Loopback1mpls traffic-eng area 0PE2 Configuration
ip cefmpls label protocol ldpmpls traffic-eng tunnelsmpls ldp router-id Loopback1 force!interface Loopback1ip address 10.0.0.4 255.255.255.255!interface loopback 2ip address 10.4.0.1 255.255.255.255!interface Tunnel27ip unnumbered Loopback1tunnel destination 10.0.0.27tunnel mode mpls traffic-engtunnel mpls traffic-eng autoroute announcetunnel mpls traffic-eng priority 1 1tunnel mpls traffic-eng bandwidth 1000tunnel mpls traffic-eng path-option 1 explicit name xxxx-1!interface FastEthernet0/0/0.2encapsulation dot1Q 203xconnect 10.0.0.27 2 encapsulation mpls!interface FastEthernet0/0/0.3encapsulation dot1Q 204xconnect 10.0.0.27 4 encapsulation mpls!interface FastEthernet1/1/0ip address 10.4.1.1 255.255.255.0mpls traffic-eng tunnelsip rsvp bandwidth 10000 10000!router ospf 1network 10.0.0.0 0.255.255.255 area 0mpls traffic-eng router-id Loopback1mpls traffic-eng area 0!ip explicit-path name xxxx-1 enablenext-address 10.4.1.2next-address 10.1.0.10Example: Configuring OAM Cell Emulation
The following example shows how to enable OAM cell emulation on an ATM PVC:
interface ATM 1/0/0pvc 1/200 l2transportencapsulation aal5xconnect 10.13.13.13 100 encapsulation mplsoam-ac emulation-enableoam-pvc manageThe following example shows how to set the rate at which an AIS cell is sent every 30 seconds:
interface ATM 1/0/0pvc 1/200 l2transportencapsulation aal5xconnect 10.13.13.13 100 encapsulation mplsoam-ac emulation-enable 30oam-pvc manageThe following example shows how to configure OAM cell emulation for ATM AAL5 over MPLS in VC class configuration mode. The VC class is then applied to an interface.
enableconfigure terminalvc-class atm oamclassencapsulation aal5oam-ac emulation-enable 30oam-pvc manageinterface atm1/0/0class-int oamclasspvc 1/200 l2transportxconnect 10.13.13.13 100 encapsulation mplsThe following example shows how to configure OAM cell emulation for ATM AAL5 over MPLS in VC class configuration mode. The VC class is then applied to a PVC.
enableconfigure terminalvc-class atm oamclassencapsulation aal5oam-ac emulation-enable 30oam-pvc manageinterface atm1/0/0pvc 1/200 l2transportclass-vc oamclassxconnect 10.13.13.13 100 encapsulation mplsThe following example shows how to configure OAM cell emulation for ATM AAL5 over MPLS in VC class configuration mode. The VC class is then applied to an interface. One PVC is configured with OAM cell emulation at an AIS rate of 10. That PVC uses the AIS rate of 10 instead of 30.
enableconfigure terminalvc-class atm oamclassencapsulation aal5oam-ac emulation-enable 30oam-pvc manageinterface atm1/0/0class-int oamclasspvc 1/200 l2transportoam-ac emulation-enable 10xconnect 10.13.13.13 100 encapsulation mplsExample: Configuring ATM Cell Relay over MPLS
The following example shows how to configure ATM cell relay over MPLS in VC class configuration mode. The VC class is then applied to an interface.
enableconfigure terminalvc-class atm cellrelayencapsulation aal0interface atm1/0/0class-int cellrelaypvc 1/200 l2transportxconnect 10.13.13.13 100 encapsulation mplsThe following example shows how to configure ATM cell relay over MPLS in VC class configuration mode. The VC class is then applied to a PVC.
enableconfigure terminalvc-class atm cellrelayencapsulation aal0interface atm1/0/0pvc 1/200 l2transportclass-vc cellrelayxconnect 10.13.13.13 100 encapsulation mplsThe following example shows how to configure a pseudowire class to transport single ATM cells over a virtual path:
pseudowire-class vp-cell-relayencapsulation mplsinterface atm 5/0atm pvp 1 l2transportxconnect 10.0.0.1 123 pw-class vp-cell-relayExample: Configuring per-Subinterface MTU for Ethernet over MPLS
Figure 4 shows a configuration that enables matching MTU values between VC endpoints.
As shown in Figure 4, PE1 is configured in xconnect subinterface configuration mode with an MTU value of 1500 bytes in order to establish an end-to-end VC with PE2, which also has an MTU value of 1500 bytes. If PE1 was not set with an MTU value of 1500 bytes, in xconnect subinterface configuration mode, the subinterface would inherit the MTU value of 2000 bytes set on the interface. This would cause a mismatch in MTU values between the VC endpoints, and the VC would not come up.
Figure 4 Configuring MTU Values in xconnect Subinterface Configuration Mode
The following examples show the router configurations in Figure 4:
CE1 Configuration
interface gigabitethernet0/0/0mtu 1500no ip address!interface gigabitethernet0/0/0.1encapsulation dot1Q 100ip address 10.181.182.1 255.255.255.0PE1 Configuration
interface gigabitethernet0/0/0mtu 2000no ip address!interface gigabitethernet0/0/0.1encapsulation dot1Q 100xconnect 10.1.1.152 100 encapsulation mplsmtu 1500!interface gigabitethernet0/0/0.2encapsulation dot1Q 200ip address 10.151.100.1 255.255.255.0mpls ipPE2 Configuration
interface gigabitethernet1/0/0mtu 2000no ip address!interface gigabitethernet1/0/0.2encapsulation dot1Q 200ip address 10.100.152.2 255.255.255.0mpls ip!interface fastethernet0/0/0no ip address!interface fastethernet0/0/0.1description default MTU of 1500 for FastEthernetencapsulation dot1Q 100xconnect 10.1.1.151 100 encapsulation mplsCE2 Configuration
interface fastethernet0/0/0no ip addressinterface fastethernet0/0/0.1encapsulation dot1Q 100ip address 10.181.182.2 255.255.255.0The show mpls l2transport binding command, issued from router PE1, shows a matching MTU value of 1500 bytes on both the local and remote routers:
Router# show mpls l2transport bindingDestination Address: 10.1.1.152, VC ID: 100Local Label: 100Cbit: 1, VC Type: FastEthernet, GroupID: 0MTU: 1500, Interface Desc: n/aVCCV: CC Type: CW [1], RA [2]CV Type: LSPV [2]Remote Label: 202Cbit: 1, VC Type: FastEthernet, GroupID: 0MTU: 1500, Interface Desc: n/aVCCV: CC Type: RA [2]CV Type: LSPV [2]Router# show mpls l2transport vc detailLocal interface: Gi0/0/0.1 up, line protocol up, Eth VLAN 100 upDestination address: 10.1.1.152, VC ID: 100, VC status: upOutput interface: Gi0/0/0.2, imposed label stack {202}Preferred path: not configuredDefault path: activeNext hop: 10.151.152.2Create time: 1d11h, last status change time: 1d11hSignaling protocol: LDP, peer 10.1.1.152:0 upTargeted Hello: 10.1.1.151(LDP Id) -> 10.1.1.152MPLS VC labels: local 100, remote 202Group ID: local 0, remote 0MTU: local 1500, remote 1500Remote interface description:Sequencing: receive disabled, send disabledVC statistics:packet totals: receive 41, send 39byte totals: receive 4460, send 5346packet drops: receive 0, send 0Configuring Tunnel Selection
The following example shows how to set up two preferred paths for PE1. One preferred path specifies an MPLS traffic engineering tunnel. The other preferred path specifies an IP address of a loopback address on PE2. There is a static route configured on PE1 that uses a TE tunnel to reach the IP address on PE2.
PE1 Configuration
mpls label protocol ldpmpls traffic-eng tunnelstag-switching tdp router-id Loopback0pseudowire-class pw1encapsulation mplspreferred-path interface Tunnel1 disable-fallback!pseudowire-class pw2encapsulation mplspreferred-path peer 10.18.18.18!interface Loopback0ip address 10.2.2.2 255.255.255.255no ip directed-broadcastno ip mroute-cache!interface Tunnel1ip unnumbered Loopback0no ip directed-broadcasttunnel destination 10.16.16.16tunnel mode mpls traffic-engtunnel mpls traffic-eng priority 7 7tunnel mpls traffic-eng bandwidth 1500tunnel mpls traffic-eng path-option 1 explicit name path-tu1!interface Tunnel2ip unnumbered Loopback0no ip directed-broadcasttunnel destination 10.16.16.16tunnel mode mpls traffic-engtunnel mpls traffic-eng priority 7 7tunnel mpls traffic-eng bandwidth 1500tunnel mpls traffic-eng path-option 1 dynamic!interface gigabitethernet0/0/0no ip addressno ip directed-broadcastno negotiation auto!interface gigabitethernet0/0/0.1encapsulation dot1Q 222no ip directed-broadcastxconnect 10.16.16.16 101 pw-class pw1!interface ATM1/0/0no ip addressno ip directed-broadcastno atm enable-ilmi-trapno atm ilmi-keepalivepvc 0/50 l2transportencapsulation aal5xconnect 10.16.16.16 150 pw-class pw2!interface FastEthernet2/0/1ip address 10.0.0.1 255.255.255.0no ip directed-broadcasttag-switching ipmpls traffic-eng tunnelsip rsvp bandwidth 15000 15000!router ospf 1log-adjacency-changesnetwork 10.0.0.0 0.0.0.255 area 0network 10.2.2.2 0.0.0.0 area 0mpls traffic-eng router-id Loopback0mpls traffic-eng area 0!ip route 10.18.18.18 255.255.255.255 Tunnel2!ip explicit-path name path-tu1 enablenext-address 10.0.0.1index 3 next-address 10.0.0.1PE2 Configuration
mpls label protocol ldpmpls traffic-eng tunnelsmpls ldp router-id Loopback0interface Loopback0ip address 10.16.16.16 255.255.255.255no ip directed-broadcastno ip mroute-cache!interface Loopback2ip address 10.18.18.18 255.255.255.255no ip directed-broadcast!interface FastEthernet1/1/0ip address 10.0.0.2 255.255.255.0no ip directed-broadcastmpls traffic-eng tunnelsmpls ipno cdp enableip rsvp bandwidth 15000 15000!interface FastEthernet1/1/1no ip addressno ip directed-broadcastno cdp enable!interface FastEthernet1/1/1.1encapsulation dot1Q 222no ip directed-broadcastno cdp enablempls l2transport route 10.2.2.2 101!interface ATM5/0/0no ip addressno ip directed-broadcastno atm enable-ilmi-trapno atm ilmi-keepalivepvc 0/50 l2transportencapsulation aal5xconnect 10.2.2.2 150 encapsulation mpls!router ospf 1log-adjacency-changesnetwork 10.0.0.0 0.0.0.255 area 0network 10.16.16.16 0.0.0.0 area 0mpls traffic-eng router-id Loopback0mpls traffic-eng area 0Example: Configuring MTU Values in xconnect Configuration Mode for L2VPN Interworking
The following example shows an L2VPN Interworking example. The PE1 router has a serial interface configured with an MTU value of 1492 bytes. The PE2 router uses xconnect configuration mode to set a matching MTU of 1492 bytes, which allows the two routers to form an interworking 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.
PE1 Configuration
pseudowire-class atom-ipiwencapsulation mplsinterworking ip!interface Loopback0ip address 10.1.1.151 255.255.255.255!interface Serial2/0/0mtu 1492no ip addressencapsulation pppno fair-queueserial restart-delay 0xconnect 10.1.1.152 123 pw-class atom-ipiw!interface Serial4/0/0ip address 10.151.100.1 255.255.255.252encapsulation pppmpls ipserial restart-delay 0!router ospf 1log-adjacency-changesnetwork 10.1.1.151 0.0.0.0 area 0network 10.151.100.0 0.0.0.3 area 0!mpls ldp router-id Loopback0PE2 Configuration
pseudowire-class atom-ipiwencapsulation mplsinterworking ip!interface Loopback0ip address 10.1.1.152 255.255.255.255!interface FastEthernet0/0/0no ip addressxconnect 10.1.1.151 123 pw-class atom-ipiwmtu 1492!interface Serial4/0/0ip address 10.100.152.2 255.255.255.252encapsulation pppmpls ipserial restart-delay 0!router ospf 1log-adjacency-changesnetwork 10.1.1.152 0.0.0.0 area 0network 10.100.152.0 0.0.0.3 area 0!mpls ldp router-id Loopback0The show mpls l2transport binding command shows that the MTU value for the local and remote routers is 1492 bytes.
PE1
Router# show mpls l2transport bindingDestination Address: 10.1.1.152, VC ID: 123Local Label: 105Cbit: 1, VC Type: PPP, GroupID: 0MTU: 1492, Interface Desc: n/aVCCV: CC Type: CW [1], RA [2]CV Type: LSPV [2]Remote Label: 205Cbit: 1, VC Type: FastEthernet, GroupID: 0MTU: 1492, Interface Desc: n/aVCCV: CC Type: RA [2]CV Type: LSPV [2]Router# show mpls l2transport vc detailLocal interface: Serial2/0/0 up, line protocol up, PPP upMPLS VC type is PPP, interworking type is IPDestination address: 10.1.1.152, VC ID: 123, VC status: upOutput interface: Serial4/0/0, imposed label stack {1003 205}Preferred path: not configuredDefault path: activeNext hop: point2pointCreate time: 00:25:29, last status change time: 00:24:54Signaling protocol: LDP, peer 10.1.1.152:0 upTargeted Hello: 10.1.1.151(LDP Id) -> 10.1.1.152Status TLV support (local/remote) : enabled/supportedLabel/status state machine : established, LruRruLast local dataplane status rcvd: no faultLast local SSS circuit status rcvd: no faultLast local SSS circuit status sent: no faultLast local LDP TLV status sent: no faultLast remote LDP TLV status rcvd: no faultMPLS VC labels: local 105, remote 205Group ID: local n/a, remote 0MTU: local 1492, remote 1492Remote interface description:Sequencing: receive disabled, send disabledVC statistics:packet totals: receive 30, send 29byte totals: receive 2946, send 3364packet drops: receive 0, send 0PE2
Router# show mpls l2transport bindingDestination Address: 10.1.1.151, VC ID: 123Local Label: 205Cbit: 1, VC Type: FastEthernet, GroupID: 0MTU: 1492, Interface Desc: n/aVCCV: CC Type: RA [2]CV Type: LSPV [2]Remote Label: 105Cbit: 1, VC Type: FastEthernet, GroupID: 0MTU: 1492, Interface Desc: n/aVCCV: CC Type: CW [1], RA [2]CV Type: LSPV [2]Router# show mpls l2transport vc detailLocal interface: Fe0/0/0 up, line protocol up, FastEthernet upMPLS VC type is FastEthernet, interworking type is IPDestination address: 10.1.1.151, VC ID: 123, VC status: upOutput interface: Se4/0/0, imposed label stack {1002 105}Preferred path: not configuredDefault path: activeNext hop: point2pointCreate time: 00:25:19, last status change time: 00:25:19Signaling protocol: LDP, peer 10.1.1.151:0 upTargeted Hello: 10.1.1.152(LDP Id) -> 10.1.1.151Status TLV support (local/remote) : enabled/supportedLabel/status state machine : established, LruRruLast local dataplane status rcvd: no faultLast local SSS circuit status rcvd: no faultLast local SSS circuit status sent: no faultLast local LDP TLV status sent: no faultLast remote LDP TLV status rcvd: no faultMPLS VC labels: local 205, remote 105Group ID: local n/a, remote 0MTU: local 1492, remote 1492Remote interface description:Sequencing: receive disabled, send disabledVC statistics:packet totals: receive 29, send 30byte totals: receive 2900, send 3426packet drops: receive 0, send 0Examples: Configuring Any Transport over MPLS (AToM): Remote Ethernet Port Shutdown
The following example shows how to enable remote Ethernet port shutdown:
configure terminal!pseudowire-class eomplsencapsulation mpls!interface GigabitEthernet1/0/0xconnect 10.1.1.1 1 pw-class eomplsremote link failure notificationThe following example shows how to disable remote Ethernet port shutdown:
configure terminal!pseudowire-class eomplsencapsulation mpls!interface GigabitEthernet1/0/0xconnect 10.1.1.1 1 pw-class eomplsno remote link failure notificationThe related show command output reports operational status for all remote L2 Tunnels by interface.
Router# show interface G1/0/0GigabitEthernet1/0/0 is L2 Tunnel remote down, line protocol is upHardware is GigMac 4 Port GigabitEthernet, address is 0003.ff4e.12a8 (bia 0003.ff4e.12a8)Internet address is 10.9.9.2/16MTU 1500 bytes, BW 1000000 Kbit, DLY 10 usec, rely 255/255, load 1/255Router# show ip interface briefInterface IP-Address OK? Method Status ProtocolGigabitEthernet2/0/0 unassigned YES NVRAM L2 Tunnel remote down upGigabitEthernet2/1/0 unassigned YES NVRAM administratively down downAdditional References
Related Documents
Standards
MIBs
RFCs
Technical Assistance
Feature Information for Any Transport over MPLS
Table 6 lists the features in this module and provides links to specific configuration information.
Use Cisco Feature Navigator to find information about platform support and software image support. Cisco Feature Navigator enables you to determine which software images support a specific software release, feature set, or platform. To access Cisco Feature Navigator, go to http://www.cisco.com/go/cfn. An account on Cisco.com is not required.
Note
Table 6 Feature Information for Any Transport over MPLS
Any Transport over MPLS (AToM): ATM AAL5 over MPLS (AAL5oMPLS)
Cisco IOS XE Release 3.2S
In Cisco IOS XE Release 3.2S, this feature was introduced on the Cisco ASR 1000 Series Aggregation Services Routers.
The following sections provides information about this feature:
•
This feature introduced no new or modified commands.
Any Transport over MPLS (AToM): ATM OAM Emulation
Cisco IOS XE Release 3.2S
In Cisco IOS XE Release 3.2S, this feature was introduced on the Cisco ASR 1000 Series Aggregation Services Routers.
The following section provides information about this feature:
•
This feature introduced no new or modified commands.
Any Transport over MPLS (AToM): Ethernet over MPLS (EoMPLS)
Cisco IOS XE Release 2.4
This feature allows you to transport Layer 2 Ethernet VLAN packets from various sources over an MPLS backbone. Ethernet over MPLS extends the usability of the MPLS backbone by enabling it to offer Layer 2 services in addition to already existing Layer 3 services. You can enable the MPLS backbone network to accept Layer 2 VLAN packets by configuring the PE routers at the both ends of the MPLS backbone.
In Cisco IOS XE Release 2.4, this feature was introduced on the Cisco ASR 1000 Series Routers.
The following sections provide information about this feature:
•
Any Transport over MPLS (AToM): Ethernet over MPLS: Port Mode (EoMPLS)
Cisco IOS XE Release 2.4
Ethernet over MPLS (EoMPLS) is the transport of Ethernet frames across an MPLS core. It transports all frames received on a particular Ethernet or virtual LAN (VLAN) segment, regardless of the destination Media Access Control (MAC) information. It does not perform MAC learning or MAC look up for forwarding packets from the Ethernet interface. Port mode allows a frame coming into an interface to be packed into an MPLS packet and transported over the MPLS backbone to an egress interface.
In Cisco IOS XE Release 2.4, this feature was introduced on the Cisco ASR 1000 Series Routers.
The following sections provide information about this feature:
•
Any Transport over MPLS-Ethernet over MPLS Enhancements: Fast Reroute
Cisco IOS XE Release 2.4
AToM can use MPLS traffic engineering (TE) tunnels with fast reroute (FRR) support. This features enhances FRR functionality for Ethernet over MPLS (EoMPLS).
In Cisco IOS XE Release 2.4, this feature was introduced on the Cisco ASR 1000 Series Routers.
The following sections provide information about this feature:
•
Any Transport over MPLS (AToM): Frame Relay over MPLS (FRoMPLS)
Cisco IOS XE Release 3.2.1S
In Cisco IOS XE Release 3.2.1S, this feature was introduced on the Cisco ASR 1000 Series Aggregation Services Routers.
The following section provides information about this feature:
•
This feature introduced no new or modified commands.
Any Transport over MPLS (AToM): HDLC over MPLS (HDLCoMPLS)
Cisco IOS XE Release 3.2S
In Cisco IOS XE Release 3.2S, this feature was introduced on the Cisco ASR 1000 Series Aggregation Services Routers.
The following section provides information about this feature:
•
This feature introduced no new or modified commands.
Any Transport over MPLS (AToM): Layer 2 Quality of Service (QoS)
Cisco IOS XE Release 2.3
This feature provides support for quality of service (QoS) features such as traffic policing, traffic shaping, packet marking, and mapping of the packets.
In Cisco IOS XE Release 2.3, this feature was introduced on the Cisco ASR 1000 Series Routers.
The following section provides information about this feature:
Any Transport over MPLS (AToM): PPP over MPLS (PPPoMPLS)
Cisco IOS XE Release 3.2S
In Cisco IOS XE Release 3.2S, this feature was introduced on the Cisco ASR 1000 Series Aggregation Services Routers.
The following section provides information about this feature:
•
This feature introduced no new or modified commands.
Any Transport over MPLS (AToM): Remote Ethernet Port Shutdown
Cisco IOS XE Release 2.4
This feature allows a service provider edge (PE) router on the local end of an Ethernet over MPLS (EoMPLS) pseudowire to detect a remote link failure and cause the shutdown of the Ethernet port on the local customer edge (CE) router. Because the Ethernet port on the local CE router is shut down, the router does not lose data by continuously sending traffic to the failed remote link. This is beneficial if the link is configured as a static IP route.
In Cisco IOS XE Release 2.4, this feature was introduced on the Cisco ASR 1000 Series Routers.
The following sections provide information about this feature:
•
ATM VC Class Support
Cisco IOS XE Release 2.3
The ATM VC Class Support feature allows you to specify AAL5 and AAL0 encapsulations as part of a VC class.
In Cisco IOS XE Release 2.3, this feature was introduced on the Cisco ASR 1000 Series Routers.
The following sections provide information about this feature:
•
AToM Tunnel Selection
Cisco IOS XE Release 2.3
The AToM Tunnel Selection feature allows you to specify the path that traffic uses. You can specify either an MPLS TE tunnel or destination IP address or domain name server (DNS) name.
You also have the option of specifying whether the VCs should use the default path (the path LDP uses for signaling) if the preferred path is unreachable. This option is enabled by default; you must explicitly disable it.
In Cisco IOS XE Release 2.3, this feature was introduced on the Cisco ASR 1000 Series Aggregation Services Routers.
The following sections provide information about this feature:
•
AToM: ATM Cell Relay over MPLS: VP Mode
Cisco IOS XE Release 2.3
The AToM: ATM Cell Relay over MPLS: VP Mode feature allows you to insert one ATM cell in each MPLS packet in VP mode.
In Cisco IOS XE Release 2.3, this feature was introduced on the Cisco ASR 1000 Series Routers.
The following sections provide information about this feature:
•
AToM: Single Cell Relay-VC Mode
Cisco IOS XE Release 2.3
The AToM Single Cell Relay-VC Mode feature allows you to insert one ATM cell in each MPLS packet in VC mode.
In Cisco IOS XE Release 2.3, this feature was introduced on the Cisco ASR 1000 Series Routers.
The following sections provide information about this feature:
•
MPLS MTU Command for GRE Tunnels
Cisco IOS XE Release 2.6
This feature allows you to set the MPLS MTU size in GRE tunnels to the maximum size besides the current default size.
The following command was modified for this release: mpls mtu.
MPLS L2VPN Clear Xconnect Command
Cisco IOS XE Release 3.1S
These features enable you to:
•
•
•
The following commands were introduced or modified by these features: cell-packing, clear xconnect, control-word, encapsulation (Any Transport over MPLS), oam-ac emulation-enable.
Per-Subinterface MTU for Ethernet over MPLS (EoMPLS)
Cisco IOS XE Release 2.4
This feature provides you with the ability to specify maximum transmission unit (MTU) values in xconnect subinterface configuration mode. When you use xconnect subinterface configuration mode to set the MTU value, you establish a pseudowire connection for situations where the interfaces have different MTU values that cannot be changed.
In Cisco IOS XE Release 2.4, this feature was introduced on the Cisco ASR 1000 Series Aggregation Services Routers.
The following section provides information about this feature:
•
No commands were new or modified for this release.
VLAN ID Rewrite
Cisco IOS XE Release 2.4
The VLAN ID rewrite feature enables you to use VLAN interfaces with different VLAN IDs at both ends of the tunnel.
In Cisco IOS XE Release 2.4, this feature was introduced on the Cisco ASR 1000 Series Routers.
The following sections provide information about this feature:
•
AToM Load Balancing with Single PW
Cisco IOS XE Release 3.4S
The AToM Load Balancing with Single PW feature enables load balancing for packets within the same pseudowire by further classifying packets within the same pseudowire into different flows based on some field in the packet received on attachment circuit.
In Cisco IOS XE Release 3.4S, this feature was introduced on the Cisco ASR 1000 Series Aggregation Services Routers.
The following sections provide information about this feature:
•
Cisco and the Cisco Logo are trademarks of Cisco Systems, Inc. and/or its affiliates in the U.S. and other countries. A listing of Cisco's trademarks can be found at www.cisco.com/go/trademarks. Third party trademarks mentioned are the property of their respective owners. The use of the word partner does not imply a partnership relationship between Cisco and any other company. (1005R)
Any Internet Protocol (IP) addresses and phone numbers used in this document are not intended to be actual addresses and phone numbers. Any examples, command display output, network topology diagrams, and other figures included in the document are shown for illustrative purposes only. Any use of actual IP addresses or phone numbers in illustrative content is unintentional and coincidental.
© 2001-2011 Cisco Systems, Inc. All rights reserved.
