OSM Configuration Note, 12.2SX - Configuring Multiprotocol Label Switching on the Optical Services Modules [Cisco 7600 Series Routers]

Table Of Contents

Configuring Multiprotocol Label Switching on the Optical Services Modules

Configuring MPLS

Understanding MPLS

MPLS Support on OSMs

Supported Features

MPLS Limitations and Restrictions

MPLS Limitations

Configuring MPLS

HDLC Over MPLS

HDLC Over MPLS Restrictions

Supported OSMs

Configuring HDLC Over MPLS

PPP Over MPLS

Supported OSMs

PPP Over MPLS Restrictions

Configuring PPP Over MPLS

Configuring MPLS QoS

Supported MPLS QoS Features

Understanding the MPLS Experimental Field

Configuring Class-Based Marking for MPLS (Supervisor Engine 2)

Configuring a Class Map to Classify MPLS Packets

Configuring a Policy Map to Set the MPLS Experimental Field

Attaching the Service Policy

Verifying QoS Operation

Configuration Examples

Ingress PE Router Configuration

Configuring MPLS VPN

MPLS VPN Support on OSMs

MPLS VPN Limitations and Restrictions

MPLS VPN Memory Requirements and Recommendations

MPLS Per-Label Load Balancing

Configuring MPLS VPN QoS

Configuration Example

Any Transport over MPLS

Restrictions for Any Transport over MPLS

Ethernet over MPLS Restrictions

ATM AAL5 over MPLS Restrictions

ATM Cell Relay over MPLS Restrictions

Frame Relay over MPLS Restrictions

Information About Any Transport over MPLS

How AToM Transports Layer 2 Packets

Compatibility with Previous Releases of AToM

Benefits of AToM

Prerequisites

AToM and QoS

Ethernet over MPLS

SUP720-3BXL-Based EoMPLS

Supervisor Engine 2-Based EoMPLS

Supported OSMs

Configuring EoMPLS VLAN Mode for Supervisor Engine 2 or OSM-Based System

Configuring EoMPLS VLAN Mode for SUP720-3BXL-Based System

Ethernet over MPLS VLAN Mode Configuration Guidelines

Verifying the Configuration

Configuring EoMPLS Port Mode for Supervisor Engine 2 or OSM-Based System

Configuring EoMPLS Port Mode for SUP720-3BXL-Based System

Ethernet over MPLS Port Mode Configuration Guidelines

ATM AAL5 over MPLS VC-Mode

Supported OSMs

Configuring ATM AAL5 over MPLS VC-Mode

Verifying the Configuration

Troubleshooting Tips

ATM Cell Relay over MPLS VC-Mode

Configuring ATM Cell Relay over MPLS VC-Mode

Verifying the Configuration

Troubleshooting Tips

Frame Relay Over MPLS

Supported Platforms and OSMs

Configuring Frame Relay over MPLS with DLCI-to-DLCI Connections

DETAILED STEPS

Verifying the Configuration

Layer 2 Local Switching

Layer 2 Local Switching-ATM to ATM

Supported Modules

Restrictions

Configuring ATM VC to VC Local Switching with AAL5 Encapsulation

Configuring ATM VC to VC Local Switching with AAL0 Encapsulation

Configuring ATM VP to VP Local Switching with AAL0 Encapsulation

Configuring Frame Relay DLCI Local Switching

Troubleshooting Tips

Enabling Other PE Devices to Transport Frame Relay Packets

Local Management Interface and Frame Relay over MPLS

DE/CLP and EXP Mapping on FR/ATMoMPLS VC

Match on ATM CLP Bit

Restrictions for Match on ATM CLP Bit

Configuring Match on ATM CLP Bit for Ingress Policy

Match on FR-DE Bit

Restrictions for Match on FR-DE Bit

Configuring Match on FR-DE Bit for Ingress Policy

Set on ATM CLP Bit

Restrictions for Set on ATM CLP Bit

Configuring Set on ATM CLP Bit for Egress Policy

Set on FR-DE Bit

Configuring Set on FR-DE for Egress Policy

How to Configure QoS with AToM

How to Set Experimental Bits with AToM

Ethernet over MPLS and EXP Bits

ATM AAL5 over MPLS and EXP Bits

ATM Cell Relay over MPLS and EXP Bits

Frame Relay over MPLS and EXP Bits

Setting the Priority of Packets with EXP Bits

Enabling Traffic Shaping

EoMPLS QoS Example

EoMPLS QoS Example—Displaying the Traffic Policy Assigned to an Interface

EoMPLS QoS Example— Configuring QoS on VLAN

ATMoMPLS QoS Example—Configuring Ingress QoS

FRoMPLS QoS Example —Configuring Ingress QoS

HQoS for EoMPLS Virtual Circuits

Prerequisites for the HQoS for EoMPLS VCs Feature

Restrictions for the HQoS for EoMPLS VCs Feature

Supported Features

Related Commands

Configuring the HQoS for EoMPLS VCs Feature

Creating and Assigning a Policy Map to Mark the QoS Group at the Incoming Interface

Configuring the Class Map to Match on a QoS Group

Creating the Child Policy Map for the Egress Interface

Configuring the Class Maps for Matching on an Input VLAN

Creating the Parent Policy Map and Attaching It to the Egress Interface

Configuration Examples for the HQoS for EoMPLS VCs Feature

Simple Hierarchical Configuration Example

Complete Hierarchical QoS Example

Multiple Parent Policies Using the Same Child Policy Example

Common Class-Map Templates Example

AToM Load Balancing

Load Balancing Guidelines

Lowest Use Mode Limitations

Virtual Private LAN Services on the Optical Services Modules

VPLS Overview

Full-Mesh Configuration

H-VPLS

Restrictions for VPLS

Supported Features

Multipoint-to-Multipoint Support

Non-Transparent Operation

Circuit Multiplexing

MAC-Address Learning Forwarding and Aging

Jumbo Frame Support

Q-in-Q Support and Q-in-Q to EoMPLS Support

VPLS Services

Transparent LAN Service

Ethernet Virtual Connection Service

Benefits of VPLS

Configuring VPLS

Prerequisites

Supported Modules

Basic VPLS Configuration

Configuring the PE Layer 2 Interface to the CE

Configuring Layer 2 VLAN Instance on the PE

Configuring MPLS WAN Interface on the PE

Configuring MPLS in the PE

Configuring the VFI in the PE

Associating the Attachment Circuit with the VSI at the PE

Full-Mesh Configuration Example

H-VPLS with MPLS Edge Configuration Example

MAC Limit Per VLAN

Traffic Engineering for Transport Tunnel

Load Balancing

QoS

Configuring Dot1q Transparency for EoMPLS

Restrictions

Configuring Multiprotocol Label Switching on the Optical Services Modules

This chapter describes how to configure Multiprotocol Label Switching (MPLS) and Any Transport over Multiprotocol Label Switching (AToM) on the Optical Services Modules (OSMs).

This chapter consists of these sections:

•Configuring MPLS

•HDLC Over MPLS

•PPP Over MPLS

•Configuring MPLS QoS

•Configuring MPLS VPN

•Configuring MPLS VPN QoS

•Any Transport over MPLS

•Ethernet over MPLS

•ATM AAL5 over MPLS VC-Mode

•ATM Cell Relay over MPLS VC-Mode

•Frame Relay Over MPLS

•Layer 2 Local Switching

•DE/CLP and EXP Mapping on FR/ATMoMPLS VC

•HQoS for EoMPLS Virtual Circuits

•AToM Load Balancing

•Virtual Private LAN Services on the Optical Services Modules

Configuring MPLS

These sections describe MPLS and provides configuration information:

•Understanding MPLS

•MPLS Support on OSMs

•Supported Features

•MPLS Limitations and Restrictions

•Configuring MPLS

Understanding MPLS

MPLS uses label switching to forward packets over various link-level technologies such as Packet-over-SONET, Frame Relay, ATM, and Ethernet. Labels are assigned to packets based on groupings or forwarding equivalence classes (FECs). Packets belonging to the same FEC get similar treatment. The label is added between the Layer 2 and the Layer 3 header (in a packet environment) or in the virtual path identifier/virtual channel identifier (VPI/VCI) field (in ATM networks).

In an MPLS network, the edge router performs a label lookup of the incoming label, swaps the incoming label with an outgoing label, and sends the packet to the next hop. Labels are imposed on packets only at the ingress edge of the MPLS network and are removed at the egress edge. The core network reads the labels, applies the appropriate services, and forwards the packets based on the labels.

MPLS Support on OSMs

MPLS is supported on the following Catalyst 6000 family and Cisco 7600 series OSMs:

•OC-3 POS:

–OSM-4OC3-POS-SI

–OSM-8OC3-POS-SI, SL

–OSM-16OC3-POS-SI, SL

–OSM-4OC3-POS-SI+

–OSM-8OC3-POS-SI+, SL+

•OC-12 POS:

–OSM-2OC12-POS-MM, SI, SL

–OSM-4OC12-POS-MM, SI, SL

–OSM-2OC12-POS-MM+, SI+, SL+

–OSM-4OC12-POS-MM+, SI+, SL+

•OC-12 ATM:

–OSM-2OC12-ATM-MM

–OSM-2OC12-ATM-SI

–OSM-2OC12-ATM-MM+

–OSM-2OC12-ATM-SI+

•OC-48 POS:

–OSM-1OC48-POS-SS, SI, SL

–OSM-1OC48-POS-SS+, SI+, SL+

•Channelized:

–OSM-1CHOC48/T3-SS

–OSM-1CHOC12/T3-SI

–OSM-1CHOC12/T1-SI

–OSM-12CT3/T1

Note You cannot use channelized OSMs as MPLS core-facing interfaces.

•OC-48 POS/DPT:

–OSM-2OC48/1DPT-SS, SI, SL

Note OSM-2OC48/1DPT-SS, SI, SL support MPLS in POS mode; OSM-2OC48/1DPT-SS, SI, SL also support MPLS in DPT mode with SUP720-3BXL-based systems.

•Gigabit Ethernet

–OSM-4GE-WAN-GBIC

–OSM-2+4GE-WAN+

•WS-X6182-2PA FlexWAN

•WS-X6582-2PA Enhanced FlexWAN

Supported Features

The following features are supported with the SUP720-3BXL and the supervisor engine 2:

Note Features in the Cisco IOS 12.2SX releases that are also supported in the Cisco IOS 12.2 mainline, 12.2T and 12.2S releases are documented in the corresponding publications for those releases. When applicable, this section refers to those publications for platform-independent features supported in the Cisco IOS 12.2SX releases. The Cisco IOS 12.2S releases do not support software images for the Cisco 7600 series routers, and the Cisco IOS 12.2S publications do not list support for the Cisco 7600 series routers.

•Multi-VRF for CE Routers (VRF Lite)—VRF-lite is a feature that enables a service provider to support two or more VPNs, where IP addresses can be overlapped among the VPNs. See http://www.cisco.com/en/US/products/hw/routers/ps259/prod_bulletin09186a00800921d7.html.

Note Multi-VRF for CE Routers (VRF Lite) is supported with the following features: IPv4 forwarding between VRFs interfaces, IPv4 ACLs, and IPv4 HSRP. Starting with Cisco IOS Release 12.2(18)SXE, Multi-VRF for CE Routers (VRF Lite) is supported with IPv4 multicast.

Note Multi-VRF for CE Routers (VRF Lite) is also supported with the Supervisor Engine 720 with PFC3A.

•MPLS Label Distribution Protocol (LDP)—MPLS label distribution protocol (LDP), as standardized by the Internet Engineering Task Force (IETF) and as enabled by Cisco IOS software, allows the construction of highly scalable and flexible IP Virtual Private Networks (VPNs) that support multiple levels of services. See http://www.cisco.com/univercd/cc/td/doc/product/software/ios122s/122snwft/release/122s14/fs2sldp.htm.

•Multiprotocol Label Switching (MPLS) on Cisco Routers—This feature provides basic MPLS support for imposing and removing labels on IP packets at label edge routers (LERs) and switching labels at label switch routers (LSR). See http://www.cisco.com/univercd/cc/td/doc/product/software/ios120/120newft/120limit/120st/120st21/fs_rtr.htm.

•MPLS Traffic Engineering-DiffServ Aware (DS-TE)—This feature provides extensions made to Multiprotocol Label Switching Traffic Engineering (MPLS TE) to make it DiffServ aware, allowing constraint-based routing of guaranteed traffic. See http://www.cisco.com/univercd/cc/td/doc/product/software/ios122s/122snwft/release/122s18/fsdserv3.htm.

•MPLS Traffic Engineering Forwarding Adjacency—This feature allows a network administrator to handle a traffic engineering, label-switched path (LSP) tunnel as a link in an Interior Gateway Protocol (IGP) network based on the Shortest Path First (SPF) algorithm. For information on forwarding adjacency with Intermediate System-to-Intermediate System (IS-IS) routing, see http://www.cisco.com/univercd/cc/td/doc/product/software/ios122s/122snwft/release/122s18/fstefa_3.htm.

For information on forwarding adjacency with Open Shortest Path First (OSPF) routing, see http://www.cisco.com/univercd/cc/td/doc/product/software/ios120/120newft/120limit/120s/120s24/ospffa.htm.

•MPLS Traffic Engineering (TE) Interarea Tunnels—This feature allows the router to establish MPLS TE tunnels that span multiple Interior Gateway Protocol (IGP) areas and levels, removing the restriction that had required the tunnel head-end and tail-end routers to be in the same area. See http://www.cisco.com/univercd/cc/td/doc/product/software/ios122s/122snwft/release/122s18/fsiarea3.htm.

•MPLS Virtual Private Networks (VPNs)—This feature allows you to deploy scalable IPv4 Layer 3 VPN backbone services over a Cisco IOS network. See http://www.cisco.com/univercd/cc/td/doc/product/software/ios120/120newft/120limit/120st/120st21/fs_vpn.htm.

•MPLS VPN Carrier Supporting Carrier (CSC)—The feature enables one MPLS VPN-based service provider to allow other service providers to use a segment of its backbone network. See http://www.cisco.com/univercd/cc/td/doc/product/software/ios122/122newft/122t/122t8/ftcsc8.htm.

•MPLS VPN—Carrier Supporting Carrier—IPv4 BGP Label Distribution—This feature enables you to configure your carrier supporting carrier network to enable Border Gateway Protocol (BGP) to transport routes and Multiprotocol Label Switching (MPLS) labels between the backbone carrier provider edge (PE) routers and the customer carrier customer edge (CE) routers. See http://www.cisco.com/univercd/cc/td/doc/product/software/ios122/122newft/122t/122t13/ftcscl13.htm.

•MPLS VPN—Interautonomous System Support—This feature allows an MPLS VPN to span service providers and autonomous systems. See http://www.cisco.com/univercd/cc/td/doc/product/software/ios120/120newft/120limit/120s/120s24/fsias24.htm.

•MPLS VPN—Inter-AS—IPv4 BGP Label Distribution: This feature enables you to set up a Virtual Private Network (VPN) service provider network so that the autonomous system boundary routers (ASBRs) exchange IPv4 routes with Multiprotocol Label Switching (MPLS) labels of the provider edge (PE) routers.See http://www.cisco.com/univercd/cc/td/doc/product/software/ios122/122newft/122t/122t13/ftiasl13.htm.

•Hot Standby Router Protocol (HSRP) Support for Multiprotocol Label Switching (MPLS) Virtual Private Networks (VPNs)—This feature ensures that the HSRP virtual IP address is added to the correct IP routing table and not to the default routing table. See http://www.cisco.com/en/US/products/sw/iosswrel/ps1834/products_feature_guide09186a008008021e.html.

•OSPF Sham Link: OSPF Sham-Link Support for MPLS VPN—This feature allows you to use a sham-link to connect Virtual Private Network (VPN) client sites that run the Open Shortest Path First (OSPF) protocol and share backdoor OSPF links in a Multiprotocol Label Switching (MPLS) VPN configuration. See http://www.cisco.com/univercd/cc/td/doc/product/software/ios122/122newft/122t/122t8/ospfshmk.htm.

•BGP Multipath Load Sharing for eBGP and iBGP—This feature allows you to configure multipath load balancing with both external BGP (eBGP) and internal BGP (iBGP) paths in Border Gateway Protocol (BGP) networks that are configured to use Multiprotocol Label Switching (MPLS) Virtual Private Networks (VPNs). See http://www.cisco.com/univercd/cc/td/doc/product/software/ios122/122newft/122t/122t4/fteibmpl.htm.

•Any Transport over MPLS (AToM). Transports Layer 2 packets over a Multiprotocol Label Switching (MPLS) backbone. See the "Any Transport over MPLS" section.

MPLS Limitations and Restrictions

The following platform-specific limitations and restrictions apply to the MPLS support on the OSM modules:

•MPLS Limitations

•MPLS Traffic Engineering with Fast ReRoute (FRR) protection—this feature is not yet supported.

MPLS Limitations

The following MPLS limitations apply:

•MTU checking and fragmentation is not supported on the OSMs except that checking is supported on the OSM-2+4GE-WAN+ on the receive path.

•With supervisor engine 2, MPLS Provider (P) functionality is not supported on Ethernet interfaces that also support Layer 2 switching. The only way to support P functionality on these interfaces is to create a trunk from a Gigabit Ethernet interface on, for example, a WS-6516-GBIC module to an interface on the OSM-4GE-WAN module that is configured to allow P switching. The interface on the WS-6516-GBIC module should be placed in trunking mode, and appropriate subinterfaces should be created on the OSM-4GE-WAN module interface. With SUP720-3BXL-based systems, MPLS Provider (P) functionality is supported.

•With supervisor engine 2, load sharing is supported on PE paths only and not on the P device.

•Encapsulation on the 2-Port OC-12 ATM OSM—MPLS is supported only when the interface is configured for AAL5SNAP (cell mode) encapsulation (default).

Note For information on other limitations and restrictions, see "MPLS VPN Limitations and Restrictions" section, "Ethernet over MPLS Restrictions" section, "ATM AAL5 over MPLS Restrictions" section, "ATM Cell Relay over MPLS Restrictions" section, "Frame Relay over MPLS Restrictions" section, and "Restrictions for VPLS" section.

Configuring MPLS

For information on configuring MPLS, refer to the Multiprotocol Label Switching on Cisco Routers feature module at the following URLs:

http://www.cisco.com/univercd/cc/td/doc/product/software/ios121/121newft/121t/121t5/mpls4t.htm

/en/US/docs/ios/12_2/switch/configuration/guide/xcftagov_external_docbase_0900e4b180753c36_4container_external_docbase_0900e4b18075440c.html#1021991

HDLC Over MPLS

HDLC over MPLS encapsulates HDLC protocol data units (PDUs) in MPLS packets and forwards them across the MPLS network. The PE routers do not participate in any protocol negotiation or authentication.

HDLC Over MPLS Restrictions

The following restrictions pertain to the HDLC over MPLS feature:

•Synchronous interfaces: The connections between the CE and PE routers on both ends of the backbone must have similar link layer characteristics. The connections between the CE and PE routers must both be synchronous.

•Interface configuration: You must configure HDLC over MPLS on router interfaces only. You cannot configure HDLC over MPLS on subinterfaces.

Note For HDLCoMPLS, SUP720-PFC3B-based systems and SUP720-PFC3BXL-based systems require that the core-facing cards must be WAN cards (enhanced OSMs, FlexWAN and Enhanced FlexWAN modules, and Shared Port Adapter [SPA] Interface Processors [SIPs]).

Supported OSMs

The following OSMs support HDLC over MPLS:

•OC-3 POS:

–OSM-4OC3-POS-SI+

–OSM-8OC3-POS-SI+, SL+

•OC-12 POS:

–OSM-2OC12-POS-MM+, SI+, SL+

–OSM-4OC12-POS-MM+, SI+, SL+

•OC-48 POS:

–OSM-2OC48/1DPT-SS, SI, SL

Note HDLCoMPLS is supported for POS mode only for the OSM-2OC48/1DPT-SS, SI, SL.

–OSM-1OC48-POS-SS+, SI+, SL+

Configuring HDLC Over MPLS

With HDLC over MPLS, the whole HDLC packet is transported. The ingress PE router removes only the HDLC flags and frame check sequence (FCS) bits. The contents of the packet are not used or changed.

SUMMARY STEPS

1. enable

2. configure terminal

3. interface serialslot/port

4. encapsulation encapsulation-type

5. xconnect peer-router-id vcid encapsulation mpls

DETAILED STEPS

Command or Action

Purpose

Step 1

enable
Example:

Router> enable

Enables privileged EXEC mode.

•Enter your password if prompted.

Step 2

configure terminal
Example:

Router# configure terminal

Enters global configuration mode.

Step 3

interface serialslot/port
Example:

Router(config)# interface serial5/0

Specifies a serial interface and enters interface configuration mode. You must configure HDLC over MPLS on router interfaces only. You cannot configure HDLC over MPLS on subinterfaces.

Step 4

encapsulation encapsulation-type
Example:

Router(config-if)# encapsulation hdlc

Specifies HDLC encapsulation.

Step 5

xconnect peer-router-id vcid encapsulation mpls
Example:

Router(config-fr-pw-switching)# xconnect 10.0.0.1 123 encapsulation mpls

Creates the VC to transport the Layer 2 packets.

This example shows an HDLC over MPLS configuration and verification:
PE1# show run int pos1/8
Building configuration...
Current configuration : 137 bytes
!
interface POS1/8
 mtu 5000
 no ip address
 mls qos trust dscp
 clock source internal
 xconnect 33.33.33.33 101 encapsulation mpls
end
PE1# sh mpls l2 vc 101
Local intf     Local circuit        Dest address    VC ID      Status
-------------  -------------------- --------------- ---------- ----------
PO1/8          HDLC                 33.33.33.33     101        UP
PE1#
PE1# sh mpls l2 vc 101 detail
Local interface: PO1/8 up, line protocol up, HDLC up
  Destination address: 33.33.33.33, VC ID: 101, VC status: up
    Tunnel label: imp-null, next hop point2point
    Output interface: PO4/4.1, imposed label stack {1396}
  Create time: 00:17:49, last status change time: 00:03:33
  Signaling protocol: LDP, peer 33.33.33.33:0 up
    MPLS VC labels: local 25, remote 1396
    Group ID: local 0, remote 0
    MTU: local 5000, remote 5000
    Remote interface description:
  Sequencing: receive disabled, send disabled
  VC statistics:
    packet totals: receive 1011, send 1010
    byte totals:   receive 104898, send 104562
    packet drops:  receive 0, send 0
PE1# sh mpls for | inc PO1/8
25     Untagged    l2ckt(101)        114705     PO1/8      point2point
PE1#
PE2#sh run int pos8/1
Building configuration...
Current configuration : 137 bytes
!
interface POS8/1
 mtu 5000
 no ip address
 mls qos trust dscp
 clock source internal
 xconnect 11.11.11.11 101 encapsulation mpls
end
PE2# sh mpls l2 vc 101
Local intf     Local circuit        Dest address    VC ID      Status
-------------  -------------------- --------------- ---------- ----------
PO8/1          HDLC                 11.11.11.11     101        UP
PE2#sh mpls l2 vc 101 detail
Local interface: PO8/1 up, line protocol up, HDLC up
  Destination address: 11.11.11.11, VC ID: 101, VC status: up
    Tunnel label: imp-null, next hop point2point
    Output interface: PO8/4.1, imposed label stack {25}
  Create time: 00:12:37, last status change time: 00:06:19
  Signaling protocol: LDP, peer 11.11.11.11:0 up
    MPLS VC labels: local 1396, remote 25
    Group ID: local 0, remote 0
    MTU: local 5000, remote 5000
    Remote interface description:
  Sequencing: receive disabled, send disabled
  VC statistics:
    packet totals: receive 1028, send 1028
    byte totals:   receive 105960, send 105940
    packet drops:  receive 0, send 0
PE2# sh mpls for | inc PO8/1
1396   Untagged    l2ckt(101)        114634     PO8/1      point2point
PE2#
CE1#sh run int pos3/0/0
Building configuration...
Current configuration : 127 bytes
!
interface POS3/0/0
 ip address 130.0.0.1 255.0.0.0
 no ip directed-broadcast
 no ip mroute-cache
 clock source internal
end
CE2# sh run int pos3/0
Building configuration...
Current configuration : 123 bytes
!
interface POS3/0
 mtu 5000
 ip address 130.0.0.2 255.0.0.0
 no ip directed-broadcast
 crc 16
 clock source internal
end
CE1# ping
Protocol [ip]:
Target IP address: 130.0.0.2
Repeat count [5]: 1000
Datagram size [100]:
Timeout in seconds [2]:
Extended commands [n]:
Sweep range of sizes [n]:
Type escape sequence to abort.
Sending 1000, 100-byte ICMP Echos to 130.0.0.2, timeout is 2 seconds:
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
!!!!!!!!!!!!!!!!!!!!
Success rate is 100 percent (1000/1000), round-trip min/avg/max = 1/1/4 ms
Note Keepalives are end to end, that is, from CE to CE.

PPP Over MPLS

PPP over MPLS encapsulates PPP PDUs in MPLS packets and forwards them across the MPLS network. The PE routers do not participate in any protocol negotiation or authentication.

Note For PPPoMPLS, all PPP negotiations (for example, link control protocol [LCP]) are end to end, that is, from CE to CE. The PE routers do not participate in the PPP negotiations.

Supported OSMs

The following OSMs support HDLC over MPLS:

•OC-3 POS:

–OSM-4OC3-POS-SI+

–OSM-8OC3-POS-SI+, SL+

•OC-12 POS:

–OSM-2OC12-POS-MM+, SI+, SL+

–OSM-4OC12-POS-MM+, SI+, SL+

•OC-48 POS:

–OSM-2OC48/1DPT-SS, SI, SL

–OSM-1OC48-POS-SS+, SI+, SL+

PPP Over MPLS Restrictions

The following restrictions pertain to the PPP over MPLS feature:

•Zero hops on a PE router: Zero hops on one router is not supported. However, you can have back-to-back PE routers.

•Synchronous interfaces: The connections between the CE and PE routers on both ends of the backbone must have similar link layer characteristics. The connections between the CE and PE routers must both be synchronous.

•Multilink PPP: Multilink PPP (MLPPP) is not supported. You cannot configure a PPPoMPLS VC on a MLPPP interface on the PE router.

Note While MLPPPoMPLS is not supported, it can be emulated. To achieve this, each member link of the MLPPP bundle on a CE requires a corresponding PPPoMPLS tunnel on the PE router that it directly connects to. For example, if an MLPPP bundle is comprised of three member links, you must configure three PPPoMPLS tunnels on each PE with each tunnel corresponding to a member link.

Configuring PPP Over MPLS

With PPP over MPLS, the ingress PE router removes the flags, address, control field, and the frame check sequence (FCS).

SUMMARY STEPS

1. enable

2. configure terminal

3. interface serialslot/port

4. encapsulation encapsulation-type

5. xconnect peer-router-id vcid encapsulation mpls

Detailed Steps

Command or Action

Purpose

Step 1

enable
Example:

Router> enable

Enables privileged EXEC mode.

•Enter your password if prompted.

Step 2

configure terminal
Example:

Router# configure terminal

Enters global configuration mode.

Step 3

interface serialslot/port
Example:

Router(config)# interface serial5/0

Specifies a serial interface and enters interface configuration mode. You must configure PPP over MPLS on router interfaces only. You cannot configure HDLC over MPLS on subinterfaces.

Step 4

encapsulation encapsulation-type
Example:

Router(config-if)# encapsulation ppp

Specifies PPP encapsulation.

Step 5

xconnect peer-router-id vcid encapsulation mpls
Example:

Router(config-fr-pw-switching)# xconnect 10.0.0.1 123 encapsulation mpls

Creates the VC to transport the Layer 2 packets.

This example shows configuration and verification:
PE1# sh run int pos1/8
Building configuration...
Current configuration : 156 bytes
!
interface POS1/8
 mtu 5000
 no ip address
 encapsulation ppp
 mls qos trust dscp
 clock source internal
 xconnect 33.33.33.33 101 encapsulation mpls
end
PE2# sh run int pos8/1
Building configuration...
Current configuration : 156 bytes
!
interface POS8/1
 mtu 5000
 no ip address
 encapsulation ppp
 mls qos trust dscp
 clock source internal
 xconnect 11.11.11.11 101 encapsulation mpls
end
This example show how to verify the configuration:
PE1#
PE1# sh mpls l2 vc 101
Local intf     Local circuit        Dest address    VC ID      Status    
-------------  -------------------- --------------- ---------- ----------
PO1/8          PPP                  33.33.33.33     101        UP        
PE1#
PE2# sh mpls l2 vc 101
Local intf     Local circuit        Dest address    VC ID      Status    
-------------  -------------------- --------------- ---------- ----------
PO8/1          PPP                  11.11.11.11     101        UP        
PE2#
PE1# sh mpls l2 vc 101 detail
Local interface: PO1/8 up, line protocol up, PPP up
  Destination address: 33.33.33.33, VC ID: 101, VC status: up
    Tunnel label: imp-null, next hop point2point
    Output interface: PO4/4.1, imposed label stack {2530}
  Create time: 00:02:02, last status change time: 00:01:16
  Signaling protocol: LDP, peer 33.33.33.33:0 up
    MPLS VC labels: local 413, remote 2530
    Group ID: local 0, remote 0
    MTU: local 5000, remote 5000
    Remote interface description: 
  Sequencing: receive disabled, send disabled
  VC statistics:
    packet totals: receive 19, send 18
    byte totals:   receive 1394, send 1058
    packet drops:  receive 0, send 0
PE2# sh mpls l2 vc 101 detail
Local interface: PO8/1 up, line protocol up, PPP up
  Destination address: 11.11.11.11, VC ID: 101, VC status: up
    Tunnel label: imp-null, next hop point2point
    Output interface: PO8/4.1, imposed label stack {413}
  Create time: 00:01:49, last status change time: 00:01:15
  Signaling protocol: LDP, peer 11.11.11.11:0 up
    MPLS VC labels: local 2530, remote 413
    Group ID: local 0, remote 0
    MTU: local 5000, remote 5000
    Remote interface description: 
  Sequencing: receive disabled, send disabled
  VC statistics:
    packet totals: receive 19, send 19
    byte totals:   receive 1074, send 1069
    packet drops:  receive 0, send 0
Note Keepalives are end to end, that is, from CE toCE.

Configuring MPLS QoS

These sections provide configuration information for MPLS QoS:

•Supported MPLS QoS Features

•Understanding the MPLS Experimental Field

•Configuring Class-Based Marking for MPLS (Supervisor Engine 2)

•Configuration Examples

Supported MPLS QoS Features

The OSMs support the following MPLS QoS features:

•OSM QoS features using MPLS EXP classification. See "Configuring QoS on the OSMs" section on page 1-2.

•MPLS EXP marking done by the OSMs when they are used with a Supervisor Engine 2. See "Configuring Class-Based Marking for MPLS (Supervisor Engine 2)" section.

•MPLS EXP policing and marking done by PFC3BXL when the OSMs are used with a Sup720-3BXL. For PFC3BXL policing and marking, refer to http://www.cisco.com/univercd/cc/td/doc/product/core/cis7600/software/122sx/swcg/qos.htm.

Note For AToM QoS features, see "How to Configure QoS with AToM" section.

Understanding the MPLS Experimental Field

Setting the MPLS experimental field value satisfies the requirement of service providers that do not want the value of the IP precedence field modified within IP packets transported through their networks.

By choosing different values for the MPLS experimental field, you can mark packets so that packets have the priority that they require during periods of congestion.

By default, the IP precedence value is copied into the MPLS experimental field during imposition.You can mark the MPLS EXP bits with a PFC3BXL policy.

Figure 1-1 shows a service provider's MPLS network that connects two sites of a customer's network.

Figure 1-1 MPLS Network Connecting Two Sites of a Customer's IP Network

Configuring Class-Based Marking for MPLS (Supervisor Engine 2)

To configure Class-based Marking for MPLS (Supervisor Engine 2), perform the tasks described in the following sections:

•Configuring a Class Map to Classify MPLS Packets

•Configuring a Policy Map to Set the MPLS Experimental Field.

Note Class-based marking for MPLS (supervisor engine 2) is supported only on the P-facing interface of the ingress PE.

Configuring a Class Map to Classify MPLS Packets

To configure a class map, perform this task beginning in global configuration mode:
Command

Purpose
Step 1
Router(config)# class-map class-name
Specifies the class map to which packets will be matched.
Step 2
Router(config-cmap)# match mpls experimental value
Specifies the packet characteristics that will be matched to the class.
Step 3
Router(config-cmap)# exit
Exits class-map configuration mode.
This example shows that all packets that contain MPLS experimental value 4 are matched by the traffic class exp4:
Router(config)# class-map exp4 
Router(config-cmap)# match mpls experimental 4 
Router(config-cmap)# exit
Configuring a Policy Map to Set the MPLS Experimental Field

To configure a policy map, perform this task beginning in global configuration mode:
Command

Purpose
Step 1
Router(config)# policy-map policy-name
Creates a policy map that can be attached to one or more interfaces to specify a service policy.
Step 2
Router(config-pmap)# class class-name
Specifies the name of the class map previously designated in the class-map command.
Step 3
Router(config-pmap-c)# set mpls experimental value¹
Designates the value to which the MPLS bits are set if the packets match the specified policy map.
Step 4
Router(config-pmap-c)# exit
Exits policy-map configuration mode.
¹You can also configure additional supported features, such as shaping.
This example shows that the value in the MPLS experimental field of each packet that is matched by the class-map exp4 is set to 5:
Router(config)# policy-map set_experimental_5 
Router(config-pmap)# class exp4 
Router(config-pmap-c)# set mpls experimental 5 
Router(config-pmap-c)# exit
Router(config-pmap)# exit
Attaching the Service Policy

To attach the service policy to an interface, perform this task beginning in global configuration mode:
Command

Purpose
Step 1
Router(config)# interface name
Designates the output interface.
Step 2
Router(config-if)# service-policy {input | output} 
policy-name
Attaches the specified policy map to the interface.
Step 3
Router(config-if)# exit
Exits interface configuration mode.
This example shows that the service policy set_experimental_5 is attached to an POS output interface:
Router(config)# interface POS6/1 
Router(config-if)# service-policy output set_experimental_5 
Router(config-if)# exit
Verifying QoS Operation

To verify the operation of MPLS QoS, perform this task:

Command

Purpose

Router# show policy-map interface [interface-name]

Displays detailed information about QoS.

Configuration Examples

Sample configurations provided in this section can be applied to either OSMs or FlexWAN modules supported on the Cisco 7600 series routers.

Ingress PE Router Configuration

In the following example, IP packets with IP precedence 1 entering an MPLS network are shaped to 2000000 bits per second and set to MPLS experimental field 5. When IP packets with IP precedence 0 enter the MPLS network, they are shaped to 3000000 bits per second and set to MPLS experimental field 3. When IP packets with any other IP precedence value enter the MPLS network, they are shaped to 5000000 bits per second.

Step 1 Define two traffic classes:
Router(config)# class-map gold
Router(config-cmap)# match mpls experimental 1
Router(config-cmap)# exit
Router(config)# class-map silver
Router(config-cmap)# match mpls experimental 0
Router(config-cmap)# exit
Note Traffic classes should be defined to match on MPLS experimental values instead of IP precedence values.

Step 2 Define a policy to take different actions on different traffic classes:
Router(config)# policy-map policy1
Router(config-pmap)# class gold
Router(config-pmap-c)# set mpls experimental 5
Router(config-pmap-c)# shape average 2000000
Router(config-pmap-c)# exit
Router(config-pmap)# class silver
Router(config-pmap-c)# set mpls experimental 3
Router(config-pmap-c)# shape average 3000000
Router(config-pmap-c)# exit
Router(config-pmap)# class class-default
Router(config-pmap-c)# shape average 5000000
Router(config-pmap-c)# exit
Router(config-pmap)# exit
Step 3 Apply the policy to the output interface of a PE router:
Router(config)# interface GE-WAN7/1
Router(config-if)# service-policy output policy1
Step 4 Verify the QoS configuration:
Router# show policy-map interface POS6/2
 POS6/2
  service-policy output:policy1
    class-map:gold (match-all)
      0 packets, 0 bytes
      30 second offered rate 0 bps, drop rate 0 bps
      match:mpls experimental  1
      queue size 0, queue limit 500
      packets output 0, packet drops 0
      tail/random drops 0, no buffer drops 0, other drops 0
      set:
       mpls experimental 5
      shape:cir 2000000,  Bc 8000,  Be 8000
        output bytes 0, shape rate 0 bps
    class-map:silver (match-all)
      9521 packets, 9425790 bytes
      30 second offered rate 3681000 bps, drop rate 1505000 bps
      match:mpls experimental  0
      queue size 0, queue limit 128
      packets output 2845, packet drops 6676
      tail/random drops 6676, no buffer drops 0, other drops 0
      set:
       mpls experimental 3
      shape:cir 3000000,  Bc 12000,  Be 12000
        output bytes 2816550, shape rate 642000 bps
    class-map:class-default (match-any)
      0 packets, 0 bytes
      30 second offered rate 0 bps, drop rate 0 bps
      match:any
        0 packets, 0 bytes
        30 second rate 0 bps
      queue size 0, queue limit 128
      packets output 0, packet drops 0
      tail/random drops 0, no buffer drops 0, other drops 0
      shape:cir 5000000,  Bc 20000,  Be 20000
        output bytes 0, shape rate 0 bps
Router#
Configuring MPLS VPN

These sections describe how to configure MPLS VPN:

•MPLS VPN Support on OSMs

•MPLS VPN Limitations and Restrictions

•MPLS VPN Memory Requirements and Recommendations

•MPLS Per-Label Load Balancing

MPLS VPN Support on OSMs

MPLS VPN is supported on the following OSMs:

•OC-3 POS:

–OSM-4OC3-POS-SI

–OSM-8OC3-POS-SI, SL

–OSM-16OC3-POS-SI, SL

–OSM-4OC3-POS-SI+

–OSM-8OC3-POS-SI+, SL+

•OC-12 POS:

–OSM-2OC12-POS-MM, SI, SL

–OSM-4OC12-POS-MM, SI, SL

–OSM-2OC12-POS-MM+, SI+, SL+

–OSM-4OC12-POS-MM+, SI+, SL+

•OC-12 ATM:

–OSM-2OC12-ATM-MM

–OSM-2OC12-ATM-SI

–OSM-2OC12-ATM-MM+

–OSM-2OC12-ATM-SI+

•OC-48 POS:

–OSM-1OC48-POS-SS, SI, SL

–OSM-1OC48-POS-SS+, SI+, SL+

•Channelized:

–OSM-1CHOC12/T3-SI

–OSM-1CHOC12/T1-SI

–OSM-12CT3/T1

•OC-48 POS/DPT¹:

–OSM-2OC48/1DPT-SS, SI, SL

•Gigabit Ethernet:

–OSM-4GE-WAN-GBIC

–OSM-2+4GE-WAN+

•WS-X6182-2PA FlexWAN

•WS-X6582-2PA Enhanced FlexWAN

MPLS VPN Limitations and Restrictions

The following MPLS VPN limitations apply:

•With supervisor engine 2-based systems, load sharing is supported on PE in ip2tag and tag2ip paths; load balancing in tag2tag paths is not supported without a unique configuration ("MPLS Per-Label Load Balancing" section). With SUP720-3BXL-based systems, load sharing is supported.

•With supervisor engine 2-based systems, MTU checking and fragmentation is not supported. With SUP720-3BXL-based systems, MTU checking and fragmentation is supported.

•For supervisor engine 2-based systems, a total of 511 VPN routing/forwarding instance routes (VRFs) are supported per system if OSMs are non-enhanced.

•For supervisor engine 2-based systems, a total of 1000 VRFs per chassis are supported if all OSMs are enhanced.

•For SUP720-3BXL-based systems, a total of 1000 VRFs per chassis are supported with enhanced OSMs; using a non-enhanced OSM causes the system to default to 511 VRFs.

•For a supervisor engine 2 or a SUP720-3BXL system, a total of 1000 VRFs per chassis with Flexwan modules only.

•With supervisor engine 2, MPLS Provider (P) functionality is not supported on Ethernet interfaces that also support Layer 2 switching. The only way to support P functionality on these interfaces is to create a trunk from a Gigabit Ethernet interface on, for example, a WS-6516-GBIC module to an interface on the OSM-4GE-WAN module that is configured to allow P switching. The interface on the WS-6516-GBIC module should be placed in trunking mode, and appropriate subinterfaces should be created on the OSM-4GE-WAN module interface. With SUP720-3BXL-based systems, MPLS Provider (P) functionality is supported.

MPLS VPN Memory Requirements and Recommendations

When a Cisco 7600 series router or a Catalyst 6500 series switch functions as a PE router in an MPLS VPN environment, the memory requirements that are listed in Table 1-1apply:

Table 1-1 MPLS VPN Memory Requirements and Recommendations

MSFC2 Memory Configuration

Maximum Number of Internet Routes, eBGP sessions, and VPNv4 routes

MSFC2 with 512 MB

100,000 Internet routes, 750 eBGP sessions, and 100,000 VPNv4 routes

Supervisor Engine 2 Memory Configuration

Maximum Number of Internet Routes, eBGP sessions, and VPNv4 routes

Supervisor Engine 2 with 256 MB

100,000 Internet routes, 750 eBGP sessions, and 175,000 VPNv4 routes

OSM Memory Configuration

Maximum Number of Internet Routes, eBGP sessions, and VPNv4 routes

OSM with 256 MB

100,000 Internet routes, 750 eBGP sessions, and 175,000 VPNv4 routes

FlexWAN Memory Configuration

Maximum Number of Internet Routes, eBGP sessions, and VPNv4 routes

FlexWAN with 2x128 MB

100,000 Internet routes, 750 eBGP sessions, and 100, 000 VPNv4 routes

If the number of Internet routes, eBGP sessions, and VPNv4 routes exceed those listed in Table 1-1, upgrade to the next memory option. If you have a FlexWAN module installed in the system, the number of Internet routes, eBGP sessions, and VPNv4 routes in the configuration file must not exceed the requirement listed in the table for FlexWAN.

MPLS Per-Label Load Balancing

Note MPLS Per-Label Load Balancing is supported on supervisor engine 2-based systems.

When the Cisco 7600 router is configured as a P router, you can ensure traffic is distributed among equal cost paths by using the mpls load-balance per-label command to enable or disable the load balancing for tag-to-tag traffic.

When enabled, MPLS per-label load balancing ensures that traffic is balanced based on the incoming labels (per prefix) among MPLS interfaces; each interface supports an equal number of incoming labels.
mpls load-balance per-label
[no] mpls load-balance per-label
The default is disabled.

Use the no form of the command to return to the default setting.

This example shows how to enable load balancing for tag-to-tag traffic:
Router(config)# mpls load-balance per-label
Router(config)# 
Note The mpls load-balance per-label command is only available for supervisor engine 2-based systems.

You can use the show mpls ttfib command to view the incoming label (indicated by an asterisk*) that is included in the load balancer. The following shows the output of the show mpls ttfib command:
Router# show mpls ttfib
Local  Outgoing    Packets Tag          LTL   Dest.   Destination    Outgoing 
Tag    Tag or VC   Switched             Index Vlanid  Mac Address    Interface
4116   21          0                    0xE0  1020    0000.0400.0000 PO4/1*
       34          0                    0x132 1019    00d0.040d.380a GE5/3
       45          0                    0xE3  4031    0000.0430.0000 PO4/4
4117   16	         0                    0x132 1019    00d0.040d.380a GE5/3*
       17          0                    0xE0  1020    0000.0400.0000 PO4/1
       18          0                    0xE3  4031    0000.0430.0000 PO4/4
4118   21          0                    0xE0  1020    0000.0400.0000 PO4/1*
       56          0                    0xE3  4031    0000.0430.0000 PO4/4
4119   35          0                    0xE3  4031    0000.0430.0000 PO4/4*
       47          0                    0xE0  1020    0000.0400.0000 PO4/1
Note The SUP720-3BXL handles MPLS labeled packets without commands. If the packet has three labels or less and the underlying packet is IPv4 then the SUP720-3BXL uses the source and destination IPv4 address. If the underlying packet is not IPv4 or more then three labels are present, then the SUP720-3BXL parses down as deep as the fifth or lowest label and uses it for hashing.

For information on configuring MPLS VPN, refer to the MPLS Virtual Private Networks feature module at this URL:

http://www.cisco.com/univercd/cc/td/doc/product/software/ios120/120newft/120t/120t7/vpn_en.htm.

Configuring MPLS VPN QoS

The OSMs support the following MPLS VPN QoS features:

•OSM QoS features using MPLS EXP classification. See "Configuring QoS on the OSMs" section on page 1-2.

•MPLS EXP marking done by the OSMs when they are used with a Supervisor Engine 2. See "Configuring Class-Based Marking for MPLS (Supervisor Engine 2)" section.

•MPLS EXP policing and marking done by PFC3BXL when the OSMs are used with a Sup720-3BXL. For PFC3BXL policing and marking, refer to http://www.cisco.com/univercd/cc/td/doc/product/core/cis7600/software/122sx/swcg/qos.htm.

In addition to these features, for Supervisor Engine 2-based systems, MPLS VPN also supports the set ip precedence command on the input WAN interfaces on the OSMs.

The following restrictions apply to the support for MPLS VPN QoS on the OSMs:

•PFC2 QoS features are not supported with MPLS VPN.

•MPLS VPN QoS is supported on the VPN interfaces only.

Match IP precedence and SET IP precedence and MPLS Experimental values are supported on the input interface only.

Configuration Example

The following example shows how to configure QoS on an MPLS VPN:
Router# configure terminal
Router(config)# class-map match-any vpn-class
Router(config-cmap)# match ip precedence 3
Router(config-cmap)# exit
Router(config)# policy-map VPN-MARKING
Router(config-pmap)# class vpn-class
Router(config-pmap-c)# set ip precedence 5
Router(config-pmap-c)# set mpls exp 5
Router(config-pmap-c)# ^Z
Router# configure terminal
Router(config)# interface ge-WAN 5/4
Router(config-if)# service-policy input VPN-MARKING
Router(config-if)# ^Z
Router# show running-config interface g5/4
Building configuration...
Current configuration :175 bytes
!
interface GE-WAN5/4
 ip vrf forwarding TEST
 ip address 194.3.1.3 255.255.255.0
 negotiation auto
 service-policy input VPN-MARKING
 mls qos trust dscp
end
Router#

Any Transport over MPLS

Any Transport over MPLS (AToM) transports Layer 2 packets over a Multiprotocol Label Switching (MPLS) backbone. AToM uses a directed Label Distribution Protocol (LDP) session between edge routers for setting up and maintaining connections. Forwarding occurs through the use of two level labels, switching between the edge routers. The external label (tunnel label) routes the packet over the MPLS backbone to the egress Provider Edge (PE) at the ingress PE. The VC label is a demuxing label that determines the connection at the tunnel endpoint (the particular egress interface on the egress PE as well as the VPI/VCI value for the AAL5 PDU, the DLCI value for Frame Relay PDU, or the VLAN identifier for an Ethernet frame).

AToM supports the following like-to-like transport types for SUP720-3BXL-based systems and for supervisor engine 2-based systems:

•Ethernet over MPLS (VLAN mode and port mode)

Note SUP720-3BXL-based systems support both hardware-based WAN as well as OSM-, FlexWAN, or FlexWAN2-based WAN.

•ATM AAL5 over MPLS

•ATM Cell Relay over MPLS

•Frame Relay over MPLS

Note SUP720-PFC3B-based systems and SUP720-PFC3BXL-based systems require that the core-facing cards must be WAN cards (enhanced OSMs, FlexWAN and Enhanced FlexWAN modules, and Shared Port Adapter [SPA] Interface Processors [SIPs]). This applies to Ethernet over MPLS, ATM AAL5 over MPLS, ATM Cell Relay over MPLS, and Frame Relay over MPLS.

Also, the specific MPLS core-facing line card may not be supported for a specific AToM technology; view specific AToM configurations in this chapter, in the FlexWAN and Enhanced FlexWAN Installation and Configuration Note, and in the Cisco 7600 Series Router SIP, SSC, and SPA Software Configuration Guide for more details.

Restrictions for Any Transport over MPLS

The following general restrictions pertain to all transport types under AToM:

•Sequencing: AToM does not support detecting of out-of-order packets.

•Address format: Configure the LDP router ID on all PE routers to be a loopback address with a /32 mask. Otherwise, some configurations might not properly function.

•Fragmentation and Reassembly: Ensure that the maximum transmission unit (MTU) of all intermediate links between endpoints is sufficient to carry the largest Layer 2 packet received.

•Control word: You cannot use CLI to enable or disable control word. Control word is mandatory for FRoMPLS and ATM AAL5 over MPLS. Control word is optional for ATM Cell Relay over MPLS; however, because there is no CLI option at this time, it is not imposed and is not expected to be present in the disposition packets.

Ethernet over MPLS Restrictions

The following restrictions pertain to the Ethernet over MPLS feature:

•Fragmentation and Reassembly: Ensure that the maximum transmission unit (MTU) of all intermediate links between endpoints is sufficient to carry the largest Layer 2 packet received.

•Packet Format: EoMPLS supports VLAN packets that conform to the IEEE's 802.1Q standard. The 802.1Q specification establishes a standard method for inserting VLAN membership information into Ethernet frames.

•Preserving 802.1 P bits and IP precedence bits: If QoS is disabled globally, both the 802.1p and IP precedence bits are preserved. When the QoS is enabled on a Layer 2 port, either 802.1q P bits or IP precedence bits can be preserved with the trusted configuration. However, by default the unpreserved bits are overwritten by the value of preserved bits. For instance, if you preserve the P bits, the IP precedence bits are overwritten with the value of the P bits. PFC3BXL provides a new command that allows you to trust the P bits while preserving the IP precedence bits. To preserve the IP precedence bits, use the no mls qos rewrite ip dscp command.

Note The no mls qos rewrite ip dscp command is not compatible with the MPLS and MPLS VPN features. See http://www.cisco.com/univercd/cc/td/doc/product/core/cis7600/software/122sx/swcg/qos.htm.

•Private VLANs: EoMPLS is not supported with private VLANs.

•Layer 2 Connections: The following restrictions apply to using Layer 2 connection with Ethernet over MPLS:

–You cannot have a direct Layer 2 connection between PEs with Ethernet over MPLS.

–You cannot have more than one Layer 2 connection between routers if those routers are configured to transport Ethernet VLAN packets over the MPLS backbone. Adding a second Layer 2 connection causes the spanning tree state to constantly toggle if you disable spanning tree on the peer router.

•Ethernet over MPLS and Trunks: The following restrictions apply to using trunks with Ethernet over MPLS. For more information, see the Cisco 7600 Series Router software documentation.

–Spanning Tree: To support Ethernet spanning tree bridge protocol data units (BPDUs) across an EoMPLS cloud, you must disable the supervisor engine spanning tree for the Ethernet over MPLS VLAN. This ensures that the EoMPLS VLANs are carried only on the trunk to the customer switch. Otherwise, the BPDUs are directed to the supervisor engine and not to the EoMPLS cloud.

–Native VLAN: The native VLAN of a trunk must not be configured as an EoMPLS VLAN.

• Layer 2 Protocol Tunneling: With PFC3BXL-based systems, there is a configuration choice for user to decide which specific protocols (for example, CDP, VTP, BPDUs). get tunneled across the MPLS cloud and which ones terminate locally. This is supported in software switching path.

• ISL encapsulation is not supported for the interface that receives EoMPLS packets.

• Unique VLANs are required across interfaces. You cannot use the same VLAN ID on different interfaces.

• EoMPLS tunnel destination route in routing and CEF table must be with a /32 mask to insure that there is an LSP from PE to PE.

•For a particular EoMPLS connection, both the ingress EoMPLS interface on the ingress PE and the egress EoMPLS interface on the egress PE have to be sub-interfaces with dot1Q encapsulation or neither is a sub-interface.

• 802.1Q in 802.1Q over EoMPLS is supported if outgoing interface connecting to MPLS network is a port on an Layer 2 card.

•Shaping of EoMPLS traffic is not supported if egress interface connecting to MPLS network is Layer 2 card.

•EoMPLS based on PFC3BXL does not perform any Layer 2 look up to determine if the destination MAC address resides on the local or remote segment and does not perform any Layer 2 address learning (as traditional LAN bridging does). This functionality (local switching or hair pinning) is available only when using OSM/FlexWAN-based modules as uplinks.

ATM AAL5 over MPLS Restrictions

The following restrictionapplies to the ATM AAL5 over MPLS feature.

•Fragmentation and Reassembly: Ensure that the maximum transmission unit (MTU) of all intermediate links between endpoints is sufficient to carry the largest Layer 2 packet received.

•Both CE-facing and core-facing cards must be WAN cards (enhanced OSMs, FLexWAN and Enhanced FlexWAN modules) and not LAN cards.

ATM Cell Relay over MPLS Restrictions

The following restrictions pertain to the ATM Cell Relay over MPLS feature:

•PVC configuration: You can configure ATM Cell Relay over MPLS on PVCs only.

•Single cell relay over MPLS (SCRoMPLS): In this release, each MPLS packet contains one ATM cell. In other words, each ATM cell is transported as a single packet.

Note Cell packing is not supported.

•For SCRoMPLS, if one end of the VC has a WS-X6182-2PA FlexWAN or a WS-X6582-2PA Enhanced FlexWAN with an ATM port adapter (PA) interface, then the VPIs/VCIs must match.

Note For SCRoMPLS, if there is a WS-X6182-2PA FlexWAN or a WS-X6582-2PA Enhanced FlexWAN with an ATM port adapter (PA) interface on one end of the VC and the VPIs/VCIs do not match then a VC does come up but does not switch traffic.

•Control word: The use of the control word is not supported.

•VCC mode: ATM Cell Relay over MPLS supports only virtual channel connection (VCC) mode.

•Fragmentation and Reassembly: Ensure that the maximum transmission unit (MTU) of all intermediate links between endpoints is sufficient to carry the largest Layer 2 packet received.

•Both CE-facing and core-facing cards must be WAN cards (enhanced OSMs, FLexWAN and Enhanced FlexWAN modules) and not LAN cards.

Frame Relay over MPLS Restrictions

The Frame Relay over MPLS feature has the following restriction:

•BECN, FECN, and DE Bits: OSMs do not update backward explicit congestion notification (BECN), forward explicit congestion notification (FECN), and discard eligibility (DE) bit counters; the bit counters remain at zero.

• Port-based mode (many-to-one): All the DLCIs coming in on a given interface/port are mapped to one MPLS LSP. This mode is not supported.

• FRF.12 is not supported on PE-CE link.

• LFI/MLPPP over FR DLCI that is transported over MPLS LSPs is not supported.

• Mapping DE bit on to MPLS EXP based on configured EXP value is not supported.

•Both CE-facing and core-facing cards must be WAN cards (enhanced OSMs, FLexWAN and Enhanced FlexWAN modules) and not LAN cards.

Information About Any Transport over MPLS

To configure AToM, you must understand the following concepts:

•How AToM Transports Layer 2 Packets

•Compatibility with Previous Releases of AToM

•Benefits of AToM

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 type of Layer 2 data that will be transported across the pseudowire, such as Ethernet, Frame Relay, or ATM

•The IP address of the loopback interface of the peer PE router, which enables the PE routers to communicate

•A VC ID that uniquely identifies the pseudowire

The following example shows the basic configuration steps on a PE router that enable the transport of Layer 2 packets. Each transport type (EoMPLS, ATMoMPLS, FRoMPLS) has slightly different steps.

First define the interface or subinterface on the PE router.
Router# interface interface-type interface-number
Then specify the encapsulation type for the interface, such as dot1q.
Router(config-if)# encapsulation encapsulation-type
The last step does the following:

•Makes a connection to the peer PE router by specifying the LDP router ID of the peer PE router.

•Identifies a unique identifier that is shared between the two PE routers. The vcid is a 32-bit identifier.

The combination of the peer-router-id and the VC ID must be a unique combination on the router. Two circuits cannot use the same combination of peer-router-id and VC ID.

•Specifies the tunneling method used to encapsulate data in the pseudowire. For AToM, the tunneling method used to encapsulate data is mpls.
Router(config-if)# xconnect peer-router-id vcid encapsulation mpls
Note The xconnect command as shown above is only applicable for some transports and not for FRoMPLS.

Compatibility with Previous Releases of AToM

In previous releases of AToM, the command used to configure AToM circuits was mpls l2 transport route. This command has been replaced with the xconnect command. You can use the xconnect command to configure FRoMPLS and EoMPLS circuits.

Note You must use the mpls l2 transport route command to configure ATM AAL5 over MPLS and ATM Cell Relay over MPLS circuits.

Benefits of AToM

The following list explains some of the benefits of enabling Layer 2 packets to be sent in the MPLS network:

•The AToM product set accommodates many types of Layer 2 packets, including Ethernet and Frame Relay, across multiple Cisco router platforms, including the Cisco 7600 series routers. This enables the service provider to transport all types of traffic over the backbone and accommodate all types of customers.

•AToM adheres to the standards developed for transporting Layer 2 packets over MPLS. (See the "Ethernet over MPLS" section for the specific standards that AToM follows.) This benefits the service provider who wants to incorporate industry-standard methodologies in the network. Other Layer 2 solutions are proprietary, which can limit the service provider's ability to expand the network and can force the service provider to use only one vendor's equipment.

•Upgrading to AToM is transparent to the customer. Because the service provider network is separate from the customer network, the service provider can upgrade to AToM without disruption of service to the customer. The customers assume that they are using a traditional Layer 2 backbone.

Prerequisites

Before configuring AToM, ensure that the network is configured as follows:

•Configure IP routing in the core so that the PE routers can reach each other via IP.

•Configure MPLS in the core so that a label switched path (LSP) exists between the PE routers.

AToM and QoS

MPLS AToM uses the three experimental bits in a label to determine the queue of packets. You statically set the experimental bits in both the VC label and the LSP tunnel label, because the LSP tunnel label might be removed at the penultimate router. See "How to Configure QoS with AToM" section and "HQoS for EoMPLS Virtual Circuits" section for more information.

Ethernet over MPLS

Ethernet over MPLS works by encapsulating Ethernet PDUs in MPLS packets and forwarding them across the MPLS network. Each PDU is transported as a single packet. There are various ways to configure Ethernet over MPLS:

•VLAN mode—transports Ethernet traffic from a source 802.1Q VLAN to a destination 802.1Q VLAN through a single VC over an MPLS network.

•Port mode—allows all traffic on a port to share a single VC across an MPLS network.

There are two methods to configure EoMPLS on a SUP720-3BXL-based system and one method for a supervisor engine 2-based system.

SUP720-3BXL-Based EoMPLS

With SUP720-3BXL-based systems the supervisor engine 720 supports the MPLS functionality. The supervisor engine 720 can receive Layer 2 traffic, impose labels, and switch the frames into the MPLS core without using an OSM or FlexWAN module.

You can also equip a SUP720-3BXL-based system with an OSM or a Flexwan module facing the core of MPLS network. In this case, you can use either OSM/FlexWAN-based configuration or the SUP720-3BXL-based configuration.

Note A system can have both an OSM/FlexWAN-based configuration and a SUP720-3BXL-based configuration enabled at the same time. Cisco supports this configuration but does not recommend it. Unless the uplinks to the MPLS core are through OSM/FlexWAN-enabled interfaces then OSM/FlexWAN-based EoMPLS connections are not active; this causes packets for OSM/FlexWAN-based EoMPLS arriving on non-WAN interfaces to be dropped.

Supervisor Engine 2-Based EoMPLS

You must equip a supervisor engine 2-based system with an OSM or a FlexWAN module facing the core of MPLS network.

Supported OSMs

Table 1-2 lists the POS/SDH OSMs that support EoMPLS.

Table 1-2 POS/SDH OSMs That Support EoMPLS

OC-3c OSMs

OC-12c OSMs

OC-48c OSMs

Gigabit Ethernet OSMs

OSM-4OC3-POS-SI
OSM-4OC3-POS-SI+
OSM-8OC3-POS-SI
OSM-8OC3-POS-SL
OSM-8OC3-POS-SI+
OSM-8OC3-POS-SL+
OSM-16OC3-POS-SI
OSM-16OC3-POS-SL

OSM-2OC12-POS-MM
OSM-2OC12-POS-SI
OSM-2OC12-POS-SL
OSM-2OC12-POS-MM+
OSM-2OC12-POS-SI+
OSM-4OC12-POS-MM
OSM-4OC12-POS-SI
OSM-4OC12-POS-SL
OSM-4OC12-POS-MM+
OSM-4OC12-POS-SI+

OSM-1OC48-POS-SS
OSM-1OC48-POS-SI
OSM-1OC48-POS-SL
OSM-1OC48-POS-SS+
OSM-1OC48-POS-SI+
OSM-1OC48-POS-SL+

OSM-4GE-WAN-GBIC
OSM-2+4GE-WAN+

Note Though the OSM-2OC12-POS-SI+ card contains 2 POS ports and 4 GigE ports, the GigE ports do not support mqc queuing or shaping.

Configuring EoMPLS VLAN Mode for Supervisor Engine 2 or OSM-Based System

To configure MPLS to transport Layer 2 VLAN packets between two endpoints in an OSM-based system, perform the following steps on the provider edge (PE) routers.

Note When OSPF is used as the IGP, all loopback addresses on PE routers must be configured with 32-bit masks to ensure proper operation of MPLS forwarding between PE routers.

SUMMARY STEPS

1. enable

2. configure terminal

3. vlan

4. interface gigabitEthernet

5. switchport

6. switchport trunk encapsulation dot1q

7. switchport trunk allowed vlan list

8. switchport mode trunk

9. exit

10. interface vlan

11. mpls l2transport route

DETAILED STEPS
Command

Purpose
Step 1
enable
Example:
Router> enable
Enables privileged EXEC mode.

•Enter your password if prompted.
Step 2

configure terminal
Example:

Router# configure terminal

Enters global configuration mode.

Step 3

vlan {vlan-id | vlan-range}
Example:

Router (config)# vlan 2-3

Enter VLAN ID or range.

Step 4

interface gigabitEthernet
Example:

Router(config)# interface gigabitEthernet

Specifies the Layer 2 interface and enters interface configuration mode.

Step 5

switchport
Example:

Router(config-if)# switchport

Configures the port for switching.

Step 6

switchport trunk encapsulation dot1
Example:

Router(config-if)# switchport trunk encapsulation dot1

Set the trunk characteristics when the interface is in trunking mode.

Step 7

switchport trunk allowed vlan list
Example:

Router(config-if)# switchport trunk allowed vlan list

Changes the allowed list for the specified VLANs.

Step 8

switchport mode trunk
Example:

Router(config-if)# switchport mode trunk

Specifies a trunking VLAN Layer 2 interface.

Step 9

exit
Example:

Router(config-if)# exit

Exits interface configuration mode.

Step 10

interface vlan vlanid
Example:

Router(config)# interface vlan vlanid

Creates a unique VLAN ID number.

Step 11

mpls l2transport route destination vc-id
Example:

Router(config-if)# mpls l2transport route 9.9.11.11 3

Specifies the VC to use to transport the Layer 2 VLAN packets.

The argument destination specifies the loopback address of the remote router.

The argument vc-id is a value you supply. It must be unique for each VC. The VC ID is used to connect the endpoints of the VC.
The following configuration shows a mode trunk configuration.

CE1 Configuration
!
interface GigabitEthernet1/0
no ip address
no ip mroute-cache
negotiation auto
no cdp enable
no shut
!
interface GigabitEthernet1/0.2
encapsulation dot1Q 2
ip address 180.8.0.1 255.255.0.0
no cdp enable
no shut
!
interface GigabitEthernet1/0.3
encapsulation dot1Q 3
ip address 180.9.0.1 255.255.0.0
no cdp enable
no shut
!
CE2 Configuration
!
interface GigabitEthernet4/0
no ip address
no ip directed-broadcast
negotiation auto
tag-switching ip
no cdp enable
no shut
!
interface GigabitEthernet4/0.2
encapsulation dot1Q 2
ip address 180.8.0.2 255.255.0.0
no ip directed-broadcast
no cdp enable
no shut
!
interface GigabitEthernet4/0.3
encapsulation dot1Q 3
ip address 180.9.0.2 255.255.0.0
no ip directed-broadcast
no cdp enable
no shut
!
PE1 Configuration
!
vlan 2-3
!
interface GigabitEthernet1/4
no ip address
switchport
switchport trunk encapsulation dot1q
switchport trunk allowed vlan 2-3
switchport mode trunk
no shut
!
interface Vlan2
no ip address
no ip mroute-cache
mpls l2transport route 11.11.11.11 2 
no shut
!
interface Vlan3
no ip address
no ip mroute-cache
mpls l2transport route 11.11.11.11 3 
no shut
!
PE2 Configuration
!
vlan 2-3
!
interface GigabitEthernet7/4
no ip address
switchport
switchport trunk encapsulation dot1q
switchport trunk allowed vlan 2-3
switchport mode trunk
no shut
!
interface Vlan2
no ip address
no ip mroute-cache
mpls l2transport route 13.13.13.13 2 
no shut
!
interface Vlan3
no ip address
no ip mroute-cache
mpls l2transport route 13.13.13.13 3 
no shut
!
Configuring EoMPLS VLAN Mode for SUP720-3BXL-Based System

To configure MPLS to transport Layer 2 VLAN packets between two endpoints in a supervisor engine 720-based system, perform the following steps on the provider edge (PE) routers.

Note You must configure Ethernet over MPLS (VLAN mode) on the subinterfaces.

SUMMARY STEPS

1. enable

2. configure terminal

3. vtp mode transparent

4. interface gigabitethernetslot/interface.subinterface

5. encapsulation dot1q vlan-id

6. xconnect peer-router-id vcid encapsulation mpls

DETAILED STEPS
Command or Action

Purpose

Step 1

enable
Example:

Router> enable

Enables privileged EXEC mode.

•Enter your password if prompted.

Step 2

configure terminal
Example:

Router# configure terminal

Enters global configuration mode.

Step 3

vtp mode transparent
Example:

Router(config)#vtp mode transparent

Disables VLAN Trunking Protocol (VTP).

Step 4

interface gigabitethernetslot/interface.subinterface
Example:

Router(config)# interface gigabitethernet4/0.1

Specifies the Gigabit Ethernet subinterface and enters subinterface configuration mode. Make sure the subinterface on the adjoining CE router is on the same VLAN as this PE router.

Step 5

encapsulation dot1q vlan-id
Example:

Router(config-subif)# encapsulation dot1q 100

Enables the subinterface to accept 802.1Q VLAN packets.

The subinterfaces between the CE and PE routers that are running Ethernet over MPLS must be in the same subnet. All other subinterfaces and backbone routers do not.
Step 6
xconnect peer-router-id vcid encapsulation mpls
Example:
Router(config-subif)# xconnect 10.0.0.1 123 
encapsulation mpls
Binds the attachment circuit to a pseudowire VC. The syntax for this command is the same as for all other Layer 2 transports.
Recall that you can use either OSM/FlexWAN-based configuration or the SUP720-3BXL-based configuration. The following configuration shows the use of both with dot1Q tunneling on the supervisor engine 2.

Note The IP address is configured on subinterfaces of the CE devices.

CE1 Configuration
!
interface GigabitEthernet1/0
no ip address
no ip mroute-cache
negotiation auto
no cdp enable
no shut
!
interface GigabitEthernet1/0.2
encapsulation dot1Q 2
ip address 180.8.0.1 255.255.0.0
no cdp enable
no shut
!
interface GigabitEthernet1/0.3
encapsulation dot1Q 3
ip address 180.9.0.1 255.255.0.0
no cdp enable
no shut
!
CE2 Configuration
!
interface GigabitEthernet4/0
no ip address
no ip directed-broadcast
negotiation auto
tag-switching ip
no cdp enable
no shut
!
interface GigabitEthernet4/0.2
encapsulation dot1Q 2
ip address 180.8.0.2 255.255.0.0
no ip directed-broadcast
no cdp enable
no shut
!
interface GigabitEthernet4/0.3
encapsulation dot1Q 3
ip address 180.9.0.2 255.255.0.0
no ip directed-broadcast
no cdp enable
no shut
!
PE1 Configuration (supervisor engine 2)
!
vlan 2-3
!
interface GigabitEthernet1/4
no ip address
switchport
switchport trunk encapsulation dot1q
switchport trunk allowed vlan 2-3
switchport mode trunk
no shut
!
interface Vlan2
no ip address
no ip mroute-cache
mpls l2transport route 11.11.11.11 2
no shut
!
interface Vlan3
no ip address
no ip mroute-cache
mpls l2transport route 11.11.11.11 3
no shut
!
PE2 Configuration (supervisor engine 720)
!
vtp mode transparent
!
interface GigabitEthernet7/4
no ip address
no shut
!
interface GigabitEthernet7/4.1
encapsulation dot1Q 2
xconnect 13.13.13.13 2 encapsulation mpls
no shut
!
interface GigabitEthernet7/4.2
encapsulation dot1Q 3
xconnect 13.13.13.13 3 encapsulation mpls
no shut
!
Ethernet over MPLS VLAN Mode Configuration Guidelines

When configuring Ethernet over MPLS in VLAN mode, use the following guidelines:

•The AToM control word is supported. However, if the peer PE does not support a control word, the control word is disabled. This negotiation is done by LDP label binding.

•Ethernet packets with hardware level cyclic redundancy check (CRC) errors, framing errors, and runt packets are discarded on input.

Verifying the Configuration

To verify and display the configuration of Layer 2 VLAN transport over MPLS tunnels, perform the following steps:

Step 1 To display a brief summary of IP status and configuration for all interfaces, issue the show vlan brief command. If the interface can provide two-way communication, the Protocol field is marked "up." If the interface hardware is usable, the Status field is marked "up."
Router# show vlan brief 
osr1#sh vlan brief
VLAN Name                             Status    Ports
---- -------------------------------- --------- -------------------------
1    default                          active    
2    VLAN0002                         active    
3    VLAN0003                         active    
1002 fddi-default                     act/unsup 
1003 token-ring-default               act/unsup 
1004 fddinet-default                  act/unsup 
1005 trnet-default                    act/unsup 
Step 2 To make sure the PE router endpoints have discovered each other, issue the show mpls ldp discovery command. When an PE router receives an LDP Hello message from another PE router, it considers that router and the specified label space to be "discovered."
Router# show mpls ldp discovery 
osr1#show mpls ldp discovery
 Local LDP Identifier:
    13.13.13.13:0
    Discovery Sources:
    Interfaces:
        GE-WAN3/3 (ldp): xmit/recv
            LDP Id: 12.12.12.12:0
    Targeted Hellos:
        13.13.13.13 -> 11.11.11.11 (ldp): active/passive, xmit/recv
            LDP Id: 11.11.11.11:0
Step 3 To make sure the label distribution session has been established, issue the show mpls ldp neighbor command. The third line of the output shows that the state of the LDP session is operational and shows that messages are being sent and received.
Router# show mpls ldp neighbor 
osr1#show mpls ldp neighbor
    Peer LDP Ident: 12.12.12.12:0; Local LDP Ident 13.13.13.13:0
        TCP connection: 12.12.12.12.646 - 13.13.13.13.11010
        State: Oper; Msgs sent/rcvd: 1649/1640; Downstream
        Up time: 23:42:45
        LDP discovery sources:
          GE-WAN3/3, Src IP addr: 34.0.0.2
        Addresses bound to peer LDP Ident:
          23.2.1.14       37.0.0.2        12.12.12.12     34.0.0.2        
          99.0.0.1        
    Peer LDP Ident: 11.11.11.11:0; Local LDP Ident 13.13.13.13:0
        TCP connection: 11.11.11.11.646 - 13.13.13.13.11013
        State: Oper; Msgs sent/rcvd: 1650/1653; Downstream
        Up time: 23:42:29
        LDP discovery sources:
          Targeted Hello 13.13.13.13 -> 11.11.11.11, active, passive
        Addresses bound to peer LDP Ident:
          11.11.11.11     37.0.0.1        23.2.1.13 
Step 4 To make sure the label forwarding table is built correctly, issue the show mpls forwarding-table command. The output shows the following data:

•Local tag—Label assigned by this router.

•Outgoing tag or VC—Label assigned by next hop.

•Prefix or Tunnel Id—Address or tunnel to which packets with this label are going.

•Bytes tag switched— Number of bytes switched out with this incoming label.

•Outgoing interface—Interface through which packets with this label are sent.

•Next Hop—IP address of neighbor that assigned the outgoing label.
Router# show mpls forwarding-table 
osr1#show mpls forwarding-table
Local  Outgoing    Prefix              Bytes tag  Outgoing   Next Hop    
tag    tag or VC   or Tunnel Id        switched   interface              
16     Untagged    223.255.254.254/32   \
                                     0          Gi2/1      23.2.0.1     
20     Untagged    l2ckt(2)          133093     Vl2        point2point  
21     Untagged    l2ckt(3)          185497     Vl3        point2point  
24     Pop tag     37.0.0.0/8        0          GE3/3      34.0.0.2     
25     17          11.11.11.11/32    0          GE3/3      34.0.0.2     
26     Pop tag     12.12.12.12/32    0          GE3/3      34.0.0.2     
osr1#
Step 5 To view the state of the currently routed VCs issue the show mpls l2transport vc command.
Router# show mpls l2transport vc
osr1#show mpls l2transport vc
Local intf     Local circuit        Dest address    VC ID      Status    
-------------  -------------------- --------------- ---------- ----------
Vl2            Eth VLAN 2           11.11.11.11     2          UP        
Vl3            Eth VLAN 3           11.11.11.11     3          UP 
Step 6 Add the keyword detail to see detailed information about each VC.
Router# show mpls l2transport vc detail
osr1#show mpls l2transport vc detail
Local interface: Vl2 up, line protocol up, Eth VLAN 2 up
  Destination address: 11.11.11.11, VC ID: 2, VC status: up
    Tunnel label: 17, next hop 34.0.0.2
    Output interface: GE3/3, imposed label stack {17 18}
  Create time: 01:24:44, last status change time: 00:10:55
  Signaling protocol: LDP, peer 11.11.11.11:0 up
    MPLS VC labels: local 20, remote 18
    Group ID: local 71, remote 89
    MTU: local 1500, remote 1500
    Remote interface description: 
  Sequencing: receive disabled, send disabled
  VC statistics:
    packet totals: receive 1009, send 1019
    byte totals:   receive 133093, send 138089
    packet drops:  receive 0, send 0
Local interface: Vl3 up, line protocol up, Eth VLAN 3 up
  Destination address: 11.11.11.11, VC ID: 3, VC status: up
    Tunnel label: 17, next hop 34.0.0.2
    Output interface: GE3/3, imposed label stack {17 19}
  Create time: 01:24:38, last status change time: 00:10:55
  Signaling protocol: LDP, peer 11.11.11.11:0 up
    MPLS VC labels: local 21, remote 19
    Group ID: local 72, remote 90
    MTU: local 1500, remote 1500
    Remote interface description: 
  Sequencing: receive disabled, send disabled
  VC statistics:
    packet totals: receive 1406, send 1414
    byte totals:   receive 185497, send 191917
    packet drops:  receive 0, send 0
Configuring EoMPLS Port Mode for Supervisor Engine 2 or OSM-Based System

To support 802.1Q-in-802.1Q traffic and native Ethernet traffic over EoMPLS in an OSM-based system, configure port-based EoMPLS by performing these tasks:

SUMMARY STEPS

1. enable

2. configure terminal

3. vlan

4. vlan dot1q tag native

5. interface gigabitEthernet

6. switchport

7. switchport mode dot1qtunnel

8. switchport access vlan

9. exit

10. interface vlan

11. mpls l2transport route

DETAILED STEPS
Command

Purpose

Step 1

enable
Example:

Router> enable

Enables privileged EXEC mode.

•Enter your password if prompted.

Step 2

configure terminal
Example:

Router# configure terminal

Enters global configuration mode.

Step 3

vlan {vlan-id | vlan-range}
Example:

Router (config)# vlan 2-3

Enter VLAN ID or range.
Step 4
vlan dot1q tag native
Example:

Router(config)# vlan dot1q tag native
Enables dot1q tagging for all VLANs in a trunk.
Step 5
interface gigabitEthernet
Router(config)# interface gigabitEthernet
Specifies the Layer 2 interface and enters interface configuration mode.
Step 6

switchport
Example:

Router(config-if)# switchport

Configures the port for switching.

Step 7

switchport mode dot1qtunnel
Example:

Router(config-if)# switchport mode dot1qtunnel

Set the trunking mode to tunneling.

Step 8

switchport access vlan vlan_id
Example:

Router(config-if)# switchport access vlan 7

Configures the port to accept traffic from the specified VLAN.

Step 9

exit
Example:

Router(config-if)# exit

Exits interface configuration mode.

Step 10

interface vlan vlanid
Example:

Router(config)# interface vlan vlanid

Creates a unique VLAN ID number.

Step 11

mpls l2transport route destination vc-id
Example:

Router(config-if)# mpls l2transport route 11.11.11.11 2

Specifies the VC to use to transport the Layer 2 VLAN packets.

The argument destination specifies the loopback address of the remote router.

The argument vc-id is a value you supply. It must be unique for each VC. The VC ID is used to connect the endpoints of the VC.
This example shows a port mode access configuration for untagged packets. It requires configuring the IP addresses on the main interface of the CE devices.

CE1 Configuration
!
interface GigabitEthernet1/0
ip address 180.8.0.1 255.255.0.0
no ip mroute-cache
negotiation auto
no cdp enable
no shut
!
CE 2 Configuration
!
interface GigabitEthernet4/0
ip address 180.8.0.2 255.255.0.0
no ip directed-broadcast
negotiation auto
tag-switching ip
no cdp enable
no shut
!
PE1 Configuration
!
vlan 2
!
interface GigabitEthernet1/4
no ip address
switchport
switchport access vlan 2
switchport mode access
no shut
!
interface Vlan2
no ip address
no ip mroute-cache
mpls l2transport route 11.11.11.11 2 
no shut
!
PE2 Configuration
!
vlan 2
!
interface GigabitEthernet7/4
no ip address
switchport
switchport access vlan 2
switchport mode access
no shut
!
interface Vlan2
no ip address
no ip mroute-cache
mpls l2transport route 13.13.13.13 2 
no shut
!
This configuration shows a port mode dot1Q-tunneling configuration. You must configure subinterfaces on the CE devices for this configuration. There is a specific access VLAN for the packets.

CE1 Configuration
!
interface GigabitEthernet1/0
no ip address
no ip mroute-cache
negotiation auto
no cdp enable
no shut
!
interface GigabitEthernet1/0.2
encapsulation dot1Q 2
ip address 180.8.0.1 255.255.0.0
no cdp enable
no shut
!
interface GigabitEthernet1/0.3
encapsulation dot1Q 3
ip address 180.9.0.1 255.255.0.0
no cdp enable
no shut
!
CE2 Configuration
!
interface GigabitEthernet4/0
no ip address
no ip directed-broadcast
negotiation auto
tag-switching ip
no cdp enable
no shut
!
interface GigabitEthernet4/0.2
encapsulation dot1Q 2
ip address 180.8.0.2 255.255.0.0
no ip directed-broadcast
no cdp enable
no shut
!
interface GigabitEthernet4/0.3
encapsulation dot1Q 3
ip address 180.9.0.2 255.255.0.0
no ip directed-broadcast
no cdp enable
no shut
!
PE1 Configuration

Note This configuration requires vlan dot1q tag native.
!
vlan 2
!
vlan dot1q tag native
!
interface GigabitEthernet1/4
no ip address
switchport
switchport access vlan 2
switchport trunk encapsulation dot1q
switchport mode dot1q-tunnel
no cdp enable
spanning-tree bpdufilter enable
no shut
!
interface Vlan2
no ip address
no ip mroute-cache
mpls l2transport route 11.11.11.11 2 
no shut
!
PE2 Configuration

Note This configuration requires vlan dot1q tag native.
!
vlan 2
!
vlan dot1q tag native
!
interface GigabitEthernet7/4
no ip address
switchport
switchport access vlan 2
switchport trunk encapsulation dot1q
switchport mode dot1q-tunnel
no cdp enable
spanning-tree bpdufilter enable
no shut
!
interface Vlan2
no ip address
no ip mroute-cache
mpls l2transport route 13.13.13.13 2 
no shut
!
Configuring EoMPLS Port Mode for SUP720-3BXL-Based System

To support 802.1Q-in-802.1Q traffic and native Ethernet traffic over EoMPLS in a supervisor engine 720-based system, configure port-based EoMPLS by performing these tasks:

SUMMARY STEPS

1. enable

2. configure terminal

3. interface gigabitethernetx/x

4. xconnect peer-router-id vcid encapsulation mpls

DETAILED STEPS
Command or Action

Purpose

Step 1

enable
Example:

Router> enable

Enables privileged EXEC mode.

•Enter your password if prompted.

Step 2

configure terminal
Example:

Router# configure terminal

Enters global configuration mode and enter interface configuration mode.

Step 3

interface gigabitethernetslot/interface
Example:

Router(config-if)# interface gigabitethernet4/0

Specifies the Gigabit Ethernet interface and enters subinterface configuration mode. Make sure the interface on the adjoining CE router is on the same VLAN as this PE router.
Step 4
xconnect peer-router-id vcid 
encapsulation mpls
Example:
Router(config-subif)# xconnect 10.0.0.1 
123 encapsulation mpls
Binds the attachment circuit to a pseudowire VC. The syntax for this command is the same as for all other Layer 2 transports.
Note When the underlying port of the VLAN is an access port or .1q in .1q tunnel, then you must use an OSM or FlexWAN module to access the MPLS core similarly to the supervisor engine 2 configurations in the example below.

The following example provides both SUP720-3BXL and supervisor engine 2 configurations. It also provides two configurations for the CE devices: one where the IP address is configured on the main interface and another where the IP address is configured on the subinterface.

CE1 Configuration (main interface)
!
interface GigabitEthernet1/0
ip address 180.8.0.1 255.255.0.0
no ip mroute-cache
negotiation auto
no cdp enable
no shut
!
CE1 Configuration (subinterface)
!
interface GigabitEthernet1/0
no ip address
no ip mroute-cache
negotiation auto
no cdp enable
no shut
!
interface GigabitEthernet1/0.2
encapsulation dot1Q 2
ip address 180.8.0.1 255.255.0.0
no cdp enable
no shut
!
interface GigabitEthernet1/0.3
encapsulation dot1Q 3
ip address 180.9.0.1 255.255.0.0
no cdp enable
no shut
!
!
CE2 Configuration (main interface)
!
interface GigabitEthernet4/0
ip address 180.8.0.2 255.255.0.0
no ip directed-broadcast
negotiation auto
tag-switching ip
no cdp enable
no shut
!
CE2 Configuration (subinterface)
!
interface GigabitEthernet4/0
no ip address
no ip directed-broadcast
negotiation auto
tag-switching ip
no cdp enable
no shut
!
interface GigabitEthernet4/0.2
encapsulation dot1Q 2
ip address 180.8.0.2 255.255.0.0
no ip directed-broadcast
no cdp enable
no shut
!
interface GigabitEthernet4/0.3
encapsulation dot1Q 3
ip address 180.9.0.2 255.255.0.0
no ip directed-broadcast
no cdp enable
no shut
!
PE1 Configuration (supervisor engine 2)
!
vlan 2
!
interface GigabitEthernet1/4
 no ip address
 switchport
 switchport access vlan 2
 switchport trunk encapsulation dot1q
 switchport mode dot1q-tunnel
 no cdp enable
 spanning-tree bpdufilter enable
 no shut
!
interface Vlan2
 no ip address
 no ip mroute-cache
 mpls l2transport route 11.11.11.11 2 
 no shut
!
PE2 Configuration (SUP720-3BXL)
!
interface GigabitEthernet7/4
no ip address
xconnect 13.13.13.13 2 encapsulation mpls
no shut
!
Ethernet over MPLS Port Mode Configuration Guidelines

When configuring Ethernet over MPLS in port mode, use the following guidelines:

•The AToM control word is supported. However, if the peer PE does not support a control word, the control word is disabled. This negotiation is done by LDP label binding.

•Ethernet packets with hardware level cyclic redundancy check (CRC) errors, framing errors, and runt packets are discarded on input.

•Port mode and Ethernet VLAN mode are mutually exclusive. If you enable a main interface for port-to-port transport, you cannot also enter commands on a subinterface.

Verifying the Configuration

To verify and display the configuration of Layer 2 VLAN transport over MPLS tunnels, perform the following steps:

Step 1 To display a brief summary of IP status and configuration for all interfaces, issue the show vlan brief command. If the interface can provide two-way communication, the Protocol field is marked "up." If the interface hardware is usable, the Status field is marked "up."
Router# show vlan brief 
osr1#sh vlan brief
VLAN Name                             Status    Ports
---- -------------------------------- --------- -------------------------------
1    default                          active    
2    VLAN0002                         active    Gi1/4
1002 fddi-default                     act/unsup 
1003 token-ring-default               act/unsup 
1004 fddinet-default                  act/unsup 
1005 trnet-default                    act/unsup 
Step 2 To make sure the PE router endpoints have discovered each other, issue the show mpls ldp discovery command. When an PE router receives an LDP Hello message from another PE router, it considers that router and the specified label space to be "discovered."
Router# show mpls ldp discovery 
osr1#show mpls ldp discovery
 Local LDP Identifier:
    13.13.13.13:0
    Discovery Sources:
    Interfaces:
        GE-WAN3/3 (ldp): xmit/recv
            LDP Id: 12.12.12.12:0
    Targeted Hellos:
        13.13.13.13 -> 11.11.11.11 (ldp): active/passive, xmit/recv
            LDP Id: 11.11.11.11:0
Step 3 To make sure the label distribution session has been established, issue the show mpls ldp neighbor command. The third line of the output shows that the state of the LDP session is operational and shows that messages are being sent and received.
Router# show mpls ldp neighbor 
osr1#show mpls ldp neighbor
    Peer LDP Ident: 12.12.12.12:0; Local LDP Ident 13.13.13.13:0
        TCP connection: 12.12.12.12.646 - 13.13.13.13.11010
        State: Oper; Msgs sent/rcvd: 1715/1706; Downstream
        Up time: 1d00h
        LDP discovery sources:
          GE-WAN3/3, Src IP addr: 34.0.0.2
        Addresses bound to peer LDP Ident:
          23.2.1.14       37.0.0.2        12.12.12.12     34.0.0.2        
          99.0.0.1        
    Peer LDP Ident: 11.11.11.11:0; Local LDP Ident 13.13.13.13:0
        TCP connection: 11.11.11.11.646 - 13.13.13.13.11013
        State: Oper; Msgs sent/rcvd: 1724/1730; Downstream
        Up time: 1d00h
        LDP discovery sources:
          Targeted Hello 13.13.13.13 -> 11.11.11.11, active, passive
        Addresses bound to peer LDP Ident:
          11.11.11.11     37.0.0.1        23.2.1.13 
Step 4 To make sure the label forwarding table is built correctly, issue the show mpls forwarding-table command. The output shows the following data:

•Local tag—Label assigned by this router.

•Outgoing tag or VC—Label assigned by next hop.

•Prefix or Tunnel Id—Address or tunnel to which packets with this label are going.

•Bytes tag switched— Number of bytes switched out with this incoming label.

•Outgoing interface—Interface through which packets with this label are sent.

•Next Hop—IP address of neighbor that assigned the outgoing label.
Router# show mpls forwarding-table 
osr1#show mpls forwarding-table
Local  Outgoing    Prefix              Bytes tag  Outgoing   Next Hop    
tag    tag or VC   or Tunnel Id        switched   interface              
16     Untagged    223.255.254.254/32   \
                                     0          Gi2/1      23.2.0.1     
20     Untagged    l2ckt(2)          55146580   Vl2        point2point  
24     Pop tag     37.0.0.0/8        0          GE3/3      34.0.0.2     
25     17          11.11.11.11/32    0          GE3/3      34.0.0.2     
26     Pop tag     12.12.12.12/32    0          GE3/3      34.0.0.2 
Step 5 To view the state of the currently routed VCs issue the show mpls l2transport vc command.
Router# show mpls l2transport vc
osr1#show mpls l2transport vc
Local intf     Local circuit        Dest address    VC ID      Status    
-------------  -------------------- --------------- ---------- ----------
Vl2            Eth VLAN 2           11.11.11.11     2          UP        
osr3#show mpls l2transport vc
Local intf     Local circuit        Dest address    VC ID      Status    
-------------  -------------------- --------------- ---------- ----------
Gi7/4          Ethernet             13.13.13.13     2          UP 
Step 6 Add the keyword detail to see detailed information about each VC.
Router# show mpls l2transport vc detail
osr1#show mpls l2transport vc detail
Local interface: Vl2 up, line protocol up, Eth VLAN 2 up
  Destination address: 11.11.11.11, VC ID: 2, VC status: up
    Tunnel label: 17, next hop 34.0.0.2
    Output interface: GE3/3, imposed label stack {17 18}
  Create time: 00:15:13, last status change time: 00:11:46
  Signaling protocol: LDP, peer 11.11.11.11:0 up
    MPLS VC labels: local 20, remote 18
    Group ID: local 71, remote 0
    MTU: local 1500, remote 1500
    Remote interface description: 
  Sequencing: receive disabled, send disabled
  VC statistics:
    packet totals: receive 407857, send 407684
    byte totals:   receive 53827205, send 55444697
    packet drops:  receive 0, send 0
ATM AAL5 over MPLS VC-Mode

ATM AAL5 over MPLS encapsulates ATM AAL5 SDUs in MPLS packets and forwards them across the MPLS network. Each ATM AAL5 SDU is transported as a single packet.

Supported OSMs

The following Catalyst 6000 family and Cisco 7600 series OSMs that support ATM AAL5 over MPLS:

•WS-X6182-2PA FlexWAN

•WS-X6582-2PA Enhanced FlexWAN

•OSM-2OC12-ATM-SI+

•OSM-2OC12-ATM-MM+

•ATM PA-A3

•ATM PA-A6

Configuring ATM AAL5 over MPLS VC-Mode

You can enable the MPLS backbone network to accept AAL5 PDUs by configuring the provider edge (PE) routers at the both ends of the MPLS backbone. To transport AAL5 PDUs over MPLS, set up a virtual circuit from the ingress PE router to the egress PE router. This virtual circuit transports the AAL5 PDUs from one PE router to the other.

SUMMARY STEPS

1. enable

2. configure terminal

3. interface atmslot/port

4. pvc vpi/vci l2transport

5. encapsulation aal5

6. mpls l2transport route destination vc-id

DETAILED STEPS
Command or Action

Purpose

Step 1

enable
Example:

Router> enable

Enables privileged EXEC mode.

•Enter your password if prompted.

Step 2

configure terminal
Example:

Router# configure terminal

Enters global configuration mode.

Step 3

interface atmslot/port
Example:

Router(config)# interface atm1/1

Specifies an ATM interface and enters interface configuration mode.

Step 4

pvc vpi/vci l2transport
Example:

Router(config-if)# pvc 1/200 l2transport

Assigns a virtual path identifier (VPI) and virtual circuit identifier (VCI). The l2transport keyword indicates that the PVC is a switched PVC instead of a terminated PVC.

You can configure ATM AAL5 on PVCs only.

Step 5

encapsulation aal5
Example:

Router(config-atm-vc)# encapsulation aal5

Specifies ATM AAL5 encapsulation for the PVC. Make sure you specify the same encapsulation type on the PE and CE routers.
Step 6
Router(config-if)# mpls l2transport route 
destination vc-id
Example:
Router(config-if)# mpls l2transport route 
12.12.12.12 300
Creates the VC to transport the Layer 2 packets.
Note You can configure VCs under point-to-point and multipoint subinterfaces, and all main interfaces.

Note You cannot configure multiple VCs with mixed encapsulations on OC-12 ATM OSMs under a multipoint subinterface or main interface; you can, however, configure multiple VCs with mixed encapsulation on WS-X6182-2PA FlexWAN or WS-X6582-2PA Enhanced FlexWAN modules under a multipoint subinterface or main interface with an Enhanced ATM Port Adapter (ATM PA).

The following example shows an AAL5 over MPLS configuration.
PE1

PE2
mpls label protocol ldp
mpls ldp router-id Loopback 0 force
!
interface Loopback0
 ip address 131.131.131.131 255.255.255.255
interface ATM9/1.502 point-to-point
 mls qos trust dscp
 pvc 4/42 l2transport
  encapsulation aal5
  mpls l2transport route 123.123.123.123 502 
 !
mpls label protocol ldp
mpls ldp router-id Loopback 0 force
!
interface Loopback0
 ip address 123.123.123.123 255.255.255.255
!
interface ATM9/1.502 point-to-point
 description hi-there! 
 mls qos trust dscp
 pvc 4/42 l2transport
  encapsulation aal5
  mpls l2transport route 131.131.131.131 502 
 !
Verifying the Configuration

The show running-config command displays the contents of the currently running configuration file or the configuration for a specific interface (example is for PE1 above).
c31#show running-config interface ATM9/1.502
Building configuration...
Current configuration : 155 bytes
!
interface ATM9/1.502 point-to-point
 mls qos trust dscp
 pvc 4/42 l2transport
  encapsulation aal5
  mpls l2transport route 123.123.123.123 502 
 ! !
end
The following show mpls 12transport vc command shows that the interface is configured for AAL5 over MPLS:
c31#show mpls l2transport vc vcid 502 detail 
Local interface: AT9/1.502 up, line protocol up, ATM AAL5 4/42 up
  Destination address: 123.123.123.123, VC ID: 502, VC status: up
    Tunnel label: 25, next hop point2point
    Output interface: PO4/1, imposed label stack {25 20}
  Create time: 1d02h, last status change time: 00:33:28
  Signaling protocol: LDP, peer 123.123.123.123:0 up
    MPLS VC labels: local 19, remote 20
    Group ID: local 82, remote 80
    MTU: local 4470, remote 4470
    Remote interface description: hi-there! 
  Sequencing: receive disabled, send disabled
  VC statistics:
    packet totals: receive 1554872, send 1558795
    byte totals:   receive 2280634366, send 2281764774
    packet drops:  receive 0, send 0
The show atm pvc command shows all ATM permanent virtual connections (PVCs) and traffic information.
c31#
c31#show atm pvc 4/42
ATM9/1.502: VCD: 2, VPI: 4, VCI: 42
UBR, PeakRate: 599040
AAL5 over MPLS, etype:0x1C, Flags: 0xC3F, VCmode: 0x0
InPkts: 1573889, OutPkts: 1569951, InBytes: 2297940310, OutBytes: 2296823212
InPRoc: 0, OutPRoc: 0
InFast: 0, OutFast: 0, InAS: 1573889, OutAS: 1569951
InPktDrops: 0,  OutPktDrops: 0
InByteDrops: 0, OutByteDrops: 0
OAM cells received: 0
F5 InEndloop: 0, F5 InSegloop: 0, F5 InAIS: 0, F5 InRDI: 0
F4 InEndloop: 0, F4 InSegloop: 0, F4 InAIS: 0, F4 InRDI: 0
OAM cells sent: 0
F5 OutEndloop: 0, F5 OutSegloop: 0, F5 OutRDI: 0
F4 OutEndloop: 0, F4 OutSegloop: 0, F4 OutRDI: 0
OAM cell drops: 0
Status: UP
The show atm vc command displays all ATM permanent virtual circuits (PVCs) and switched virtual circuits (SVCs) and traffic information.
c31#show atm vc 2
ATM9/1.502: VCD: 2, VPI: 4, VCI: 42
UBR, PeakRate: 599040
AAL5 over MPLS, etype:0x1C, Flags: 0xC3F, VCmode: 0x0
InPkts: 1573896, OutPkts: 1569957, InBytes: 2297940836, OutBytes: 2296823668
InPRoc: 0, OutPRoc: 0
InFast: 0, OutFast: 0, InAS: 1573896, OutAS: 1569957
InPktDrops: 0,  OutPktDrops: 0
InByteDrops: 0, OutByteDrops: 0
OAM cells received: 0
OAM cells sent: 0
Status: UP
Troubleshooting Tips

The debug acircuit, debug mpls l2transport ipc, debug cwan atom, and debug mpls l2transport vc commands help in troubleshooting.

ATM Cell Relay over MPLS VC-Mode

The single cell relay feature allows you to insert one ATM cell in each MPLS packet.

Configuring ATM Cell Relay over MPLS VC-Mode

Perform this task to configure ATM cell relay over MPLS VC-Mode.

SUMMARY STEPS

1. enable

2. configure terminal

3. interface atmslot/port

4. pvc vpi/vci l2transport

5. encapsulation aal0

6. mpls l2transport route destination vc-id

DETAILED STEPS
Command or Action

Purpose

Step 1

enable
Example:

Router> enable

Enables privileged EXEC mode.

•Enter your password if prompted.

Step 2

configure terminal
Example:

Router# configure terminal

Enters global configuration mode.

Step 3

interface atmslot/port
Example:

Router(config)# interface atm1/1

Specifies an ATM interface and enters interface configuration mode.

Step 4

pvc vpi/vci l2transport
Example:

Router(config-if)# pvc 0/100 l2transport

Assigns a virtual path identifier (VPI) and virtual circuit identifier (VCI). The l2transport keyword indicates that the PVC is a switched PVC instead of a terminated PVC.
Step 5
encapsulation aal0
Example:
Router(config-atm-vc)# encapsulation aal0
For ATM Cell Relay, this command specifies raw cell encapsulation for the interface.
Step 6
Router(config-if)# mpls l2transport route 
destination vc-id
Example:
Router(config-if)# mpls l2transport route 
13.13.13.13 100
Creates the VC to transport the Layer 2 packets.
Note You can configure VCs under point-to-point or multipoint subinterfaces, and all main interfaces.

Note You cannot configure multiple VCs with mixed encapsulations on OC-12 ATM OSMs under a multipoint subinterface or main interface; you can, however, configure multiple VCs with mixed encapsulation on WS-X6182-2PA FlexWAN or WS-X6582-2PA Enhanced FlexWAN modules under a multipoint subinterface or main interface with an Enhanced ATM Port Adapter (ATM PA).

Note If each of the PE routers has an OC-12 ATM OSM interface, the path identifiers/virtual channel identifiers (VPIs/VCIs) do not need to match. If one of the PE routers at an end of the VC has a WS-X6182-2PA FlexWAN or a WS-X6582-2PA Enhanced FlexWAN with an ATM port adapter (PA) interface, then the VPIs/VCIs must match.

The following example shows a Cell Relay over MPLS configuration.
PE1

PE2
mpls label protocol ldp
mpls ldp router-id Loopback 0 force 
!
interface Loopback0
 ip address 131.131.131.131 255.255.255.255
!
interface ATM9/1.501 point-to-point
 mls qos trust dscp
 pvc 4/41 l2transport
  encapsulation aal0
  mpls l2transport route 123.123.123.123 501 
mpls label protocol ldp
mpls ldp router-id Loopback 0 force 
!
interface Loopback0
 ip address 123.123.123.123 255.255.255.255
!
interface ATM9/1.501 point-to-point
 mls qos trust dscp
 pvc 4/41 l2transport
  encapsulation aal0
  mpls l2transport route 131.131.131.131 501 
 !
Verifying the Configuration

The show running-config command displays the contents of the currently running configuration file or the configuration for a specific interface (this is for PE1 above).
c31#show running-config interface ATM9/1.501 
Building configuration...
Current configuration : 155 bytes
!
interface ATM9/1.501 point-to-point
 mls qos trust dscp
 pvc 4/41 l2transport
  encapsulation aal0
  mpls l2transport route 123.123.123.123 501 
 !
end
The show mpls 12transport command shows that the interface is configured for VC mode cell relay.
c31#show mpls l2transport vc vcid 501 detail 
Local interface: AT9/1.501 up, line protocol up, ATM VCC CELL 4/41 up
  Destination address: 123.123.123.123, VC ID: 501, VC status: up
    Tunnel label: 25, next hop point2point
    Output interface: PO4/1, imposed label stack {25 19}
  Create time: 1d01h, last status change time: 00:15:55
  Signaling protocol: LDP, peer 123.123.123.123:0 up
    MPLS VC labels: local 18, remote 19
    Group ID: local 82, remote 80
    MTU: local n/a, remote n/a
    Remote interface description: 
  Sequencing: receive disabled, send disabled
  VC statistics:
    packet totals: receive 48755771, send 48895612
    byte totals:   receive 2535300092, send 2542571824
    packet drops:  receive 0, send 0
c31#
The show atm pvc command shows all ATM permanent virtual connections (PVCs) and traffic information.
c31#show atm pvc 4/41
ATM9/1.501: VCD: 1, VPI: 4, VCI: 41
UBR, PeakRate: 599040
AAL0-Cell Relay over MPLS, etype:0x1B, Flags: 0xC3E, VCmode: 0x0
InBytes: 2567612684, OutBytes: 2560342200
Status: UP
The show atm vc command shows all ATM permanent virtual circuits (PVCs) and switched virtual circuits (SVCs) and traffic information.
c31#show atm vc 1
ATM9/1.501: VCD: 1, VPI: 4, VCI: 41
UBR, PeakRate: 599040
AAL0-Cell Relay over MPLS, etype:0x1B, Flags: 0xC3E, VCmode: 0x0
InBytes: 2567615492, OutBytes: 2560345424
Status: UP
Troubleshooting Tips

The debug acircuit, debug mpls l2transport ipc, debug cwan atom, and debug mpls l2transport vc commands help in troubleshooting.

Frame Relay Over MPLS

Frame Relay over MPLS encapsulates Frame Relay protocol data units (PDUs) in MPLS packets and forwards them across the MPLS network.

Supported Platforms and OSMs

FRoMPLS is supported on the following Catalyst 6000 family and Cisco 7600 series OSMs:

•OC-3 POS:

–OSM-4OC3-POS-SI+

–OSM-8OC3-POS-SI+, SL+

•OC-12 POS:

–OSM-2OC12-POS-MM+, SI+, SL+

–OSM-4OC12-POS-MM+, SI+, SL+

•OC-48 POS:

–OSM-1OC48-POS-SS+, SI+, SL+

•Channelized:

–OSM-1CHOC12/T3-SI

–OSM-1CHOC12/T1-SI

•Channelized T3:

–OSM-12CT3/T1

•OC-48 DPT/POS:

–OSM-20C48/1DPT-SI

Note FRoMPLS is supported on any FlexWAN PA that supports Frame Relay encapsulation on the media type.

Configuring Frame Relay over MPLS with DLCI-to-DLCI Connections

Perform this task to configure Frame Relay over MPLS with DLCI-to-DLCI connections.

SUMMARY STEPS

1. enable

2. configure terminal

3. frame-relay switching

4. interface serialslot/port

5. frame-relay intf-type dce

6. encapsulation frame-relay [cisco | ietf]

7. connect connection-name interface dlci l2transport

8. xconnect peer-router-id vcid encapsulation mpls

DETAILED STEPS
Command or Action

Purpose

Step 1

enable
Example:

Router> enable

Enables privileged EXEC mode.

•Enter your password if prompted.

Step 2

configure terminal
Example:

Router# configure terminal

Enters global configuration mode.

Step 3

frame-relay switching
Example:

Router(config)# frame-relay switching

Enables permanent virtual circuit (PVC) switching on a Frame Relay device.

Step 4

interface serialslot/port
Example:

Router(config)# interface Serial3/10/1

Specifies a serial interface and enters interface configuration mode.
Step 5
encapsulation frame-relay [cisco | ietf]
Example:
Router(config-if)# encapsulation 
frame-relay ietf 
Specifies Frame Relay encapsulation for the interface. You can specify different types of encapsulations. You can set one interface to Cisco encapsulation and the other interface to IETF encapsulation.
Step 6

frame-relay intf-type dce
Example:

Router(config-if)# frame-relay intf-type dce

Specifies that the interface is a DCE switch. You can also specify the interface to support NNI and DTE connections.

Step 7

connect connection-name interface dlci l2transport
Example:

Router(config)# connect fr1 Serial5/1/0 1000 l2transport

Defines connections between Frame Relay PVCs. Using the l2transport keyword specifies that the PVC will not be a locally switched PVC, but will be tunneled over the backbone network.

The connection-name argument is a text string that you provide.

The interface argument is the interface on which a PVC connection will be defined.

The dlci argument is the DLCI number of the PVC that will be connected.

Step 8

xconnect peer-router-id vcid encapsulation mpls
Example:

Router(config-fr-pw-switching)# xconnect 10.0.0.1 123 encapsulation mpls

Creates the VC to transport the Layer 2 packets. In a DLCI-to DLCI connection type, Frame Relay over MPLS uses the xconnect command in connect submode.
The example below shows a Frame Relay over MPLS with DLCI-to-DLCI configuration.
PE1

PE2
frame-relay switching
mpls label protocol ldp
mpls ldp router-id Loopback0 force
tag-switching id
!
interface Loopback0
 ip address 13.13.13.13 255.255.255.255
!
interface POS1/1
 mtu 5000
 no ip address
 encapsulation frame-relay IETF
mls qos trust dscp
 clock source internal
 frame-relay lmi-type ansi
 frame-relay intf-type dce
!
! P router facing interface POS4/1
!
interface POS4/1
 mtu 5000
 ip address 32.0.0.1 255.0.0.0
 mpls label protocol ldp
 tag-switching ip
 mls qos trust dscp
 clock source internal
!
router ospf 100
 log-adjacency-changes
 passive-interface POS1/1
 network 13.13.13.13 0.0.0.0 area 100
 network 32.0.0.0 0.255.255.255 area 100
!
connect atom_1 POS1/1 16 l2transport
 xconnect 11.11.11.11 100 encapsulation mpls
frame-relay switching
mpls label protocol ldp
mpls ldp router-id Loopback0 force
tag-switching id
!
interface Loopback0
 ip address 11.11.11.11 255.255.255.255
!
interface POS7/1
 mtu 5000
 no ip address
 encapsulation frame-relay IETF
mls qos trust dscp
 clock source internal
 frame-relay lmi-type ansi
 frame-relay intf-type dce
!
! P router facing interface POS8/2
!
interface POS8/2
 mtu 5000
 ip address 35.0.0.1 255.0.0.0
 mpls label protocol ldp
 tag-switching ip
 mls qos trust dscp
 clock source internal
!
router ospf 100
 log-adjacency-changes
 passive-interface POS7/1
 network 11.11.11.11 0.0.0.0 area 100
 network 35.0.0.0 0.255.255.255 area 100
!
connect atom_1 POS7/1 17 l2transport
 xconnect 13.13.13.13 100 encapsulation mpls
Note It is not necessary for the DLCI of interface POS1/1 and the DLCI of interface POS7/1 to match. The DLCIs can be two separate DLCIs that you connect using the connect command.

Verifying the Configuration

Use the show mpls l2transport vc command to verify the configuration.
PE1# sh mpls l2 vc 100 detail
Local interface: PO1/1 up, line protocol up, FR DLCI 16 up
  Destination address: 11.11.11.11, VC ID: 100, VC status: up
    Tunnel label: 17, next hop point2point
    Output interface: PO4/1, imposed label stack {17 1009}
  Create time: 00:09:28, last status change time: 00:01:17
  Signaling protocol: LDP, peer 11.11.11.11:0 up
    MPLS VC labels: local 1009, remote 1009
    Group ID: local 0, remote 0
    MTU: local 5000, remote 5000
    Remote interface description: 
  Sequencing: receive disabled, send disabled
  VC statistics:
    packet totals: receive 60, send 62
    byte totals:   receive 8870, send 9648
    packet drops:  receive 0, send 0
PE2# sh mpls l2 vc 100 detail
Local interface: PO7/1 up, line protocol up, FR DLCI 16 up
  Destination address: 13.13.13.13, VC ID: 100, VC status: up
    Tunnel label: 18, next hop point2point
    Output interface: PO8/2, imposed label stack {18 1009}
  Create time: 00:03:32, last status change time: 00:01:54
  Signaling protocol: LDP, peer 13.13.13.13:0 up
    MPLS VC labels: local 1009, remote 1009
    Group ID: local 0, remote 0
    MTU: local 5000, remote 5000
    Remote interface description: 
  Sequencing: receive disabled, send disabled
  VC statistics:
    packet totals: receive 4, send 4
    byte totals:   receive 1416, send 1388
    packet drops:  receive 0, send 0
PE1# show frame-relay pvc 16
PVC Statistics for interface POS1/1 (Frame Relay DCE)
DLCI = 16, DLCI USAGE = SWITCHED(tag tunnel), PVC STATUS = ACTIVE, INTERFACE = POS1/1
  input pkts 68            output pkts 66           in bytes 11500     
  out bytes 10688          dropped pkts 0           in pkts dropped 0         
  out pkts dropped 0                out bytes dropped 0         
  in FECN pkts 0           in BECN pkts 0           out FECN pkts 0         
  out BECN pkts 0          in DE pkts 0             out DE pkts 0         
  out bcast pkts 0         out bcast bytes 0         
  switched pkts 0         
  Detailed packet drop counters:
  no out intf 0            out intf down 0          no out PVC 0         
  in PVC down 0            out PVC down 0           pkt too big 0         
  shaping Q full 0         pkt above DE 0           policing drop 0         
  pvc create time 00:16:28, last time pvc status changed 00:09:34
PE2#show frame-relay pvc 16 
PVC Statistics for interface POS7/1 (Frame Relay DCE)
DLCI = 16, DLCI USAGE = SWITCHED(tag tunnel), PVC STATUS = ACTIVE, INTERFACE = POS7/1
  input pkts 27            output pkts 28           in bytes 5676      
  out bytes 6110           dropped pkts 0           in pkts dropped 0         
  out pkts dropped 0                out bytes dropped 0         
  in FECN pkts 0           in BECN pkts 0           out FECN pkts 0         
  out BECN pkts 0          in DE pkts 0             out DE pkts 0         
  out bcast pkts 0         out bcast bytes 0         
  switched pkts 0         
  Detailed packet drop counters:
  no out intf 0            out intf down 0          no out PVC 0         
  in PVC down 0            out PVC down 0           pkt too big 0         
  shaping Q full 0         pkt above DE 0           policing drop 0         
  pvc create time 00:10:50, last time pvc status changed 00:10:21
Layer 2 Local Switching

Local switching allows you to switch Layer 2 data between two interfaces of the same type (ATM to ATM or Frame Relay to Frame Relay). The interfaces can be on the same line card or on two different cards.

This section explains how to perform Layer 2 local switching-ATM to ATM and Frame Relay DCLI local switching and includes the following procedures:

•Configuring ATM VC to VC Local Switching with AAL5 Encapsulation

•Configuring ATM VC to VC Local Switching with AAL0 Encapsulation

•Configuring ATM VP to VP Local Switching with AAL0 Encapsulation

•Configuring Frame Relay DLCI Local Switching

Layer 2 Local Switching-ATM to ATM

Layer 2 Local Switching-ATM to ATM provides Layer 2 switching capability. It allow you to switch traffic coming from a customer ATM VC/VP to a Session Terminating Service Provider ATM VC/VP. Layer 2 Local Switching-ATM to ATM has three modes:

•ATM VC to VC local switching with AAL5 encapsulation

•ATM VC to VC local switching with AAL0 Encapsulation (Cell Relay mode)

•ATM VP to VP local switching with AAL0 Encapsulation

Supported Modules

Layer 2 Local Switching-ATM to ATM is supported on FlexWAN and Enhanced FlexWAN only.

Port adapter support is shown in Table 1-3.

Table 1-3 Layer 2 Local Switching-ATM to ATM Supported Port Adapters

ATM VC to VC Local Switching with AAL5 Encapsulation

ATM VC to VC Local Switching with AAL0 Encapsulation

ATM VP to VP Local Switching with AAL0 Encapsulation

PA-A3-OC3

PA-A3-OC3

PA-A3-OC3

PA-A3-E3

PA-A3-E3

PA-A3-E3

PA-A3-T3

PA-A3-T3

PA-A3-T3

PA-A6-OC3

PA-A6-E3

PA-A6-T3

Restrictions

•ATM VC to VC local switching with AAL5 encapsulation

–Does not support QoS.

–Currently supported with supervisor engine 2 only.

•ATM VC to VC local switching with AAL0 encapsulation (Cell Relay mode)

–Does not support QoS.

–Currently supported with supervisor engine 2 only.

–Each ATM cell is transported as a single packet; cell packing is not supported.

–Configurable on permanent virtual circuits (PVCs) only.

–Both ends of the connection require the same VPI/VCI. If the VPI/VCI is not same, then the connection comes up but the packet does not switch.

•ATM VP to VP local switching with AAL0 encapsulation

–Does not support QoS.

–Currently supported with supervisor engine 2 only.

–Each ATM cell is transported as a single packet; cell packing is not supported

–Configurable on permanent virtual pipes (PVPs) only.

–Each ATM cell is transported as a single packet; cell packing is not supported.

–Both ends of the connection require the same VPI/VCI. If the VPI/VCI is not same, then the connection comes up but the packet does not switch.

Configuring ATM VC to VC Local Switching with AAL5 Encapsulation

Perform this task to configure ATM VC to VC local switching.

SUMMARY STEPS

1. enable

2. configure terminal

3. interface atmslot/port

4. pvc vpi/vci l2transport

5. encapsulation aal5

Note Repeat Steps 3 through 5 for the other interface.

6. connect connection-name atm slot/port-1 |vpi/vci] atm slot/port-2 [vpi|vci]

DETAILED STEPS
Command or Action

Purpose

Step 1

enable
Example:

Router> enable

Enables privileged EXEC mode.

•Enter your password if prompted.

Step 2

configure terminal
Example:

Router# configure terminal

Enters global configuration mode.

Step 3

interface atmslot/port
Example:

Router(config)# interface atm1/0

Specifies an ATM interface and enters interface configuration mode.

Step 4

pvc vpi/vci l2transport
Example:

Router(config-if)# pvc 1/200 l2transport

Assigns a virtual path identifier (VPI) and virtual circuit identifier (VCI). The l2transport keyword indicates that the PVC is a switched PVC instead of a terminated PVC.

You can configure ATM AAL5 on PVCs only.

Step 5

encapsulation aal5
Example:

Router(config-atm-vc)# encapsulation aal5

Specifies ATM AAL5 encapsulation for the PVC.
Step 6
connect connection-name atm slot/port-1 
|vpi/vci] atm slot/port-2 [vpi|vci]
Example:

Router(config)# connect vp2vp ATM2/0/0 100 ATM2/1/0 100
Connects the ATM interfaces.
The following example shows ATM VC to VC local switching with AAL5 Encapsulation.
Router(config)# int ATM2/0/0
Router(config-if)# pvc 100/100 l2transport
Router(config-atm-vc)# encapsulation aal5
Router(config)# int ATM2/1/0
Router(config-if)# pvc 105/105 l2transport
Router(config-atm-vc)# encapsulation aal5
Router(config)# connect vc2vc ATM2/0/0 100/100 ATM2/1/0 105/105
The show atm pvc command displays all ATM permanent virtual connections (PVCs) and traffic information.
router#show atm pvc 100/100
ATM2/0/0: VCD: 44, VPI: 100, VCI: 100
UBR, PeakRate: 149760
AAL5 L2transport, etype:0x1C, Flags: 0xC3F, VCmode: 0x0
InPkts: 0, OutPkts: 0, InBytes: 0, OutBytes: 0
InPRoc: 0, OutPRoc: 0, Broadcasts: 0
InFast: 0, OutFast: 0, InAS: 0, OutAS: 0
InPktDrops: 0,  OutPktDrops: 0
InByteDrops: 0, OutByteDrops: 0
CrcErrors: 0, SarTimeOuts: 0, OverSizedSDUs: 0, LengthViolation: 0, CPIErrors: 0
Out CLP=1 Pkts: 0
OAM cells received: 0
F5 InEndloop: 0, F5 InSegloop: 0, F5 InAIS: 0, F5 InRDI: 0
F4 InEndloop: 0, F4 InSegloop: 0, F4 InAIS: 0, F4 InRDI: 0
OAM cells sent: 0
F5 OutEndloop: 0, F5 OutSegloop: 0, F5 OutRDI: 0
F4 OutEndloop: 0, F4 OutSegloop: 0, F4 OutRDI: 0
OAM cell drops: 0
Status: UP
router#show atm pvc 105/105
ATM2/1/0: VCD: 46, VPI: 100, VCI: 100
UBR, PeakRate: 149760
AAL5 L2transport, etype:0x1C, Flags: 0xC3F, VCmode: 0x0
InPkts: 0, OutPkts: 0, InBytes: 0, OutBytes: 0
InPRoc: 0, OutPRoc: 0, Broadcasts: 0
InFast: 0, OutFast: 0, InAS: 0, OutAS: 0
InPktDrops: 0,  OutPktDrops: 0
InByteDrops: 0, OutByteDrops: 0
CrcErrors: 0, SarTimeOuts: 0, OverSizedSDUs: 0, LengthViolation: 0, CPIErrors: 0
Out CLP=1 Pkts: 0
OAM cells received: 0
F5 InEndloop: 0, F5 InSegloop: 0, F5 InAIS: 0, F5 InRDI: 0
F4 InEndloop: 0, F4 InSegloop: 0, F4 InAIS: 0, F4 InRDI: 0
OAM cells sent: 0
F5 OutEndloop: 0, F5 OutSegloop: 0, F5 OutRDI: 0
F4 OutEndloop: 0, F4 OutSegloop: 0, F4 OutRDI: 0
OAM cell drops: 0
Status: UP
Use the show connection all command to see all configured connections.
router#show connection all
ID   Name               Segment 1            Segment 2           
State      
========================================================================
36   vc2vc             ATM2/0/0 100/100     ATM2/1/0 105/105     UP 
Configuring ATM VC to VC Local Switching with AAL0 Encapsulation

Perform this task to configure ATM VC to VC local switching with AAL0 encapsulation.

SUMMARY STEPS

1. enable

2. configure terminal

3. interface atmslot/port

4. pvc vpi/vci l2transport

5. encapsulation aal0

Note Repeat Steps 3 through 5 for the other interface.

6. connect connection-name atm slot/port-1 |vpi/vci] atm slot/port-2 [vpi|vci]

DETAILED STEPS
Command or Action

Purpose

Step 1

enable
Example:

Router> enable

Enables privileged EXEC mode.

•Enter your password if prompted.

Step 2

configure terminal
Example:

Router# configure terminal

Enters global configuration mode.

Step 3

interface atmslot/port
Example:

Router(config)# interface atm1/0

Specifies an ATM interface and enters interface configuration mode.

Step 4

pvc vpi/vci l2transport
Example:

Router(config-if)# pvc 1/200 l2transport

Assigns a virtual path identifier (VPI) and virtual circuit identifier (VCI). The l2transport keyword indicates that the PVC is a switched PVC instead of a terminated PVC.

Step 5

encapsulation aal0
Example:

Router(config-atm-vc)# encapsulation aal0

Specifies ATM AAL0 encapsulation for the PVC.
Step 6
connect connection-name atm slot/port-1 
|vpi/vci] atm slot/port-2 [vpi|vci]
Example:

Router(config)# connect vp2vp ATM2/0/0 100 ATM2/1/0 100
Connects the ATM interfaces.
The following example shows ATM VC to VC local switching with AAL0 encapsulation.
Router(config)# int ATM2/0/0
Router(config-if)# pvc 100/100 l2transport
Router(config-atm-vc)# encapsulation aal0
Router(config)# int ATM2/1/0
Router(config-if)# pvc 100/100 l2transport
Router(config-atm-vc)# encapsulation aal0
Router(config)# connect vc2vc ATM2/0/0 100/100 ATM2/1/0 100/100
The show atm pvc command displays all ATM permanent virtual connections (PVCs) and traffic information.
router# show atm pvc 100/100
ATM2/0/0: VCD: 44, VPI: 100, VCI: 100
UBR, PeakRate: 149760
AAL5 L2transport, etype:0x1C, Flags: 0xC3F, VCmode: 0x0
InPkts: 0, OutPkts: 0, InBytes: 0, OutBytes: 0
InPRoc: 0, OutPRoc: 0, Broadcasts: 0
InFast: 0, OutFast: 0, InAS: 0, OutAS: 0
InPktDrops: 0,  OutPktDrops: 0
InByteDrops: 0, OutByteDrops: 0
CrcErrors: 0, SarTimeOuts: 0, OverSizedSDUs: 0, LengthViolation: 0, CPIErrors: 0
Out CLP=1 Pkts: 0
OAM cells received: 0
F5 InEndloop: 0, F5 InSegloop: 0, F5 InAIS: 0, F5 InRDI: 0
F4 InEndloop: 0, F4 InSegloop: 0, F4 InAIS: 0, F4 InRDI: 0
OAM cells sent: 0
F5 OutEndloop: 0, F5 OutSegloop: 0, F5 OutRDI: 0
F4 OutEndloop: 0, F4 OutSegloop: 0, F4 OutRDI: 0
OAM cell drops: 0
Status: UP
router# show atm pvc 100/100
ATM2/1/0: VCD: 46, VPI: 100, VCI: 100
UBR, PeakRate: 149760
AAL5 L2transport, etype:0x1C, Flags: 0xC3F, VCmode: 0x0
InPkts: 0, OutPkts: 0, InBytes: 0, OutBytes: 0
InPRoc: 0, OutPRoc: 0, Broadcasts: 0
InFast: 0, OutFast: 0, InAS: 0, OutAS: 0
InPktDrops: 0,  OutPktDrops: 0
InByteDrops: 0, OutByteDrops: 0
CrcErrors: 0, SarTimeOuts: 0, OverSizedSDUs: 0, LengthViolation: 0, CPIErrors: 0
Out CLP=1 Pkts: 0
OAM cells received: 0
F5 InEndloop: 0, F5 InSegloop: 0, F5 InAIS: 0, F5 InRDI: 0
F4 InEndloop: 0, F4 InSegloop: 0, F4 InAIS: 0, F4 InRDI: 0
OAM cells sent: 0
F5 OutEndloop: 0, F5 OutSegloop: 0, F5 OutRDI: 0
F4 OutEndloop: 0, F4 OutSegloop: 0, F4 OutRDI: 0
OAM cell drops: 0
Status: UP
Use the show connection all command to see all configured connections.
router# show connection all
ID   Name               Segment 1            Segment 2           
State      
========================================================================
36   vc2vc             ATM2/0/0 100/100     ATM2/1/0 105/105     UP 
Configuring ATM VP to VP Local Switching with AAL0 Encapsulation

Perform this task to configure ATM VP to VP local switching with AAL0 encapsulation.

SUMMARY STEPS

1. enable

2. configure terminal

3. interface atmslot/port

4. atm pvp vpi l2transport

Note Repeat Steps 3 through 4 for the other interface.

5. connect connection-name atm slot/port-1 |vpi/vci] atm slot/port-2 [vpi|vci]

DETAILED STEPS
Command or Action

Purpose

Step 1

enable
Example:

Router> enable

Enables privileged EXEC mode.

•Enter your password if prompted.

Step 2

configure terminal
Example:

Router# configure terminal

Enters global configuration mode.

Step 3

interface atmslot/port
Example:

Router(config)# interface atm1/0

Specifies an ATM interface and enters interface configuration mode.
Step 4
atm pvp vpi l2transport
Example:
Router(config-if)# atm pvp vpi 1 l2transport
Specifies that the PVP is dedicated to transporting ATM cells. The l2transport keyword indicates that the PVP is for cell relay. Once you enter this command, you enter Layer 2 transport PVP submode. This submode is for Layer 2 transport only; it is not for regular PVPs.
Step 5
connect connection-name atm slot/port-1 
|vpi/vci] atm slot/port-2 [vpi|vci]
Example:
Router(config)# connect vp2vp ATM2/0/0 100 
ATM2/1/0 100
Connects the ATM interfaces.
The following example shows ATM VP to VP local switching.
Router(config)# int ATM2/0/0
Router(config-if)# atm pvp 100 l2transport
Router(config)# int ATM2/1/0
Router(config-if)# atm pvp 100 l2transport
Router(config)# connect vp2vp ATM2/0/0 100 ATM2/1/0 100
Use the show atm vp command to verify that the interface is configured for VP mode cell relay:
router# show connection all
ID   Name               Segment 1            Segment 2           
State      
========================================================================
36   vp2vp             ATM2/0/0 100         ATM2/1/0 100         UP       
BRAS# show atm vp 100
ATM2/0/0 VPI: 100, Cell Relay,
ATM2/0/0  VPI: 100, PeakRate: 0, CesRate: 0, DataVCs: 0, CesVCs: 0, Status: ACTIVE
 VCD    VCI   Type   InPkts   OutPkts   AAL/Encap     Status
 45     3     PVC    0        0         F4 OAM        ACTIVE  46     4     PVC    0        
0         F4 OAM        ACTIVE 
TotalInPkts: 0, TotalOutPkts: 0, TotalInFast: 0, TotalOutFast: 0, TotalBroadcasts: 0
TotalInPktDrops: 0, TotalOutPktDrops: 0
ATM2/1/0 VPI: 100, Cell Relay,
ATM2/1/0  VPI: 100, PeakRate: 0, CesRate: 0, DataVCs: 0, CesVCs: 0, Status: ACTIVE
 VCD    VCI   Type   InPkts   OutPkts   AAL/Encap     Status
 47     3     PVC    0        0         F4 OAM        ACTIVE  48     4     PVC    0        
0         F4 OAM        ACTIVE 
TotalInPkts: 0, TotalOutPkts: 0, TotalInFast: 0, TotalOutFast: 0, TotalBroadcasts: 0
TotalInPktDrops: 0, TotalOutPktDrops: 0
Configuring Frame Relay DLCI Local Switching

Frame Relay DLCI local switching connects one DLCI on one interface to another DLCI on a different interface in the same Cisco 7600 series router. Perform this task to set up Frame Relay DLCI local switching.

Note You use the steps below on two DLCIs in order to connect them.

Note The frame-relay route command is no longer supported for this configuration; use the connect command.

SUMMARY STEPS

1. enable

2. configure terminal

3. frame-relay switching

4. interface serialslot/port

5. encapsulation frame-relay [cisco | ietf]

6. frame-relay intf-type dce

7. connect connection-name interface_1 dlci_1 interface_2 dlci_2

DETAILED STEPS
Command or Action

Purpose

Step 1

enable
Example:

Router> enable

Enables privileged EXEC mode.

•Enter your password if prompted.

Step 2

configure terminal
Example:

Router# configure terminal

Enters global configuration mode.
Step 3
frame-relay switching
Example:

Router# frame-relay switching
Enable permanent virtual switching (PVC) switching on a Frame Relay DCE device or a Network-to-Network Interface (NNI).
Step 4

interface serialslot/port
Example:

Router(config)# interface Serial3/1/0

Specifies a serial interface.
Step 5
encapsulation frame-relay [cisco | ietf]
Example:
Router(config)# encapsulation frame-relay 
ietf 
Specifies Frame Relay encapsulation for the interface. You can specify different types of encapsulations. You can set one interface to Cisco encapsulation and the other interface to IETF encapsulation.
Step 6

frame-relay intf-type dce
Example:

Router(config)# frame-relay intf-type dce

Specifies that the interface is a DCE switch. You can also specify the interface to support NNI and DTE connections.

Step 7

connect connection-name interface_1 dlci_1 interface_2 dlci_2
Example:

Router(config)# connect fr-route1 pos1/1 110 serial6/1/0 61

Defines connections between Frame Relay PVCs.

The connection-name argument is a text string that you provide.

The interface argument is the interface on which a PVC connection will be defined.

The dlci argument is the DLCI number of the PVC that will be connected.
The following configuration provides an example of Frame Relay DLCI local switching on the same router OSR4) between a DLCI on interface POS4/1 to a DLCI on interface POS4/2 (OSR1 and OSR3 are CEs).

Note It is not necessary for the DLCI of interface POS4/1 and the DLCI of interface POS4/2 to match. The DLCIs can be two separate DLCIs that you connect using the connect command.

Configuration on OSR1
!
interface POS4/1
 mtu 9000
 no ip address
 encapsulation frame-relay
!
interface POS4/1.1 point-to-point
 ip address 11.11.1.1 255.255.255.0
 frame-relay interface-dlci 16 
Configuration on OSR4
!
frame-relay switching
!
interface POS4/1
 mtu 9000
 no ip address
 encapsulation frame-relay
 clock source internal
 frame-relay intf-type dce
!
interface POS4/2
 mtu 9000
 no ip address
 encapsulation frame-relay
 clock source internal
 frame-relay intf-type dce
!
connect test1 POS4/1 16 POS4/2 16
!
Configuration on OSR3
!
interface POS8/2
 mtu 9000
 no ip address
 encapsulation frame-relay
!
interface POS8/2.1 point-to-point
 ip address 11.11.1.2 255.255.255.0
 frame-relay interface-dlci 16   
!
Use the ping command to verify basic connectivity.
osr1#ping
Protocol [ip]: 
Target IP address: 11.11.1.2
Repeat count [5]: 100
Datagram size [100]: 
Timeout in seconds [2]: 
Extended commands [n]: 
Sweep range of sizes [n]: 
Type escape sequence to abort.
Sending 100, 100-byte ICMP Echos to 11.11.1.2, timeout is 2 seconds:
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
Success rate is 100 percent (100/100), round-trip min/avg/max = 1/1/4 ms
osr1#
Use the show frame pvc command to view statistics for all Virtual Circuit (VC) components.
osr4#sh frame pvc 16       
PVC Statistics for interface POS4/1 (Frame Relay DCE)
DLCI = 16, DLCI USAGE = SWITCHED(fr), PVC STATUS = ACTIVE, INTERFACE = POS4/1
  input pkts 100           output pkts 100          in bytes 10400     
  out bytes 10400          dropped pkts 0           in pkts dropped 0         
  out pkts dropped 0                out bytes dropped 0         
  in FECN pkts 0           in BECN pkts 0           out FECN pkts 0         
  out BECN pkts 0          in DE pkts 0             out DE pkts 0         
  out bcast pkts 0         out bcast bytes 0         
  switched pkts 0         
  Detailed packet drop counters:
  no out intf 0            out intf down 0          no out PVC 0         
  in PVC down 0            out PVC down 0           pkt too big 0         
  shaping Q full 0         pkt above DE 0           policing drop 0         
  pvc create time 02:11:44, last time pvc status changed 02:04:23
PVC Statistics for interface POS4/2 (Frame Relay DCE)
DLCI = 16, DLCI USAGE = SWITCHED(fr), PVC STATUS = ACTIVE, INTERFACE = POS4/2
  input pkts 100           output pkts 100          in bytes 10400     
  out bytes 10400          dropped pkts 0           in pkts dropped 0         
  out pkts dropped 0                out bytes dropped 0         
  in FECN pkts 0           in BECN pkts 0           out FECN pkts 0         
  out BECN pkts 0          in DE pkts 0             out DE pkts 0         
  out bcast pkts 0         out bcast bytes 0         
  switched pkts 0         
  Detailed packet drop counters:
  no out intf 0            out intf down 0          no out PVC 0         
  in PVC down 0            out PVC down 0           pkt too big 0         
  shaping Q full 0         pkt above DE 0           policing drop 0         
  pvc create time 02:11:45, last time pvc status changed 02:07:30
osr4#
Use the show connect all command to see the connections.
osr4# sh connect all
ID   Name               Segment 1            Segment 2           State       
========================================================================
1    test1             POS4/1 16            POS4/2 16            UP 
Troubleshooting Tips

The debug frame-relay event, debug acircuit, debug mpls l2transport ipc, debug cwan atom, and debug mpls l2transport vc commands help in troubleshooting.

Enabling Other PE Devices to Transport Frame Relay Packets

You can configure an interface as a data terminal equipment (DTE) device or a data circuit-terminating equipment (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 the following table:

Keyword

Description

dce

Enables the router or access server to function as a switch connected to a router.

dte

Enables the router or access server to function as a DTE device. DTE is the default.

nni

Enables the router or access server to function as a switch connected to a switch.

Local Management Interface and Frame Relay over MPLS

Local Management Interface (LMI) is a protocol that communicates status information about permanent virtual circuits (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.

Note LMI is operational only when you enable keepalives on the interfaces (keepalive packets keep the interface active).

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 Only the DCE and NNI interface types can report LMI status.

Figure 1-2 is a sample topology that helps illustrate how LMI works.

Figure 1-2 Sample Topology

Note the following:

•CE1 and PE1 and PE2 and CE2 are Frame Relay LMI peers.

•CE1 and CE2 can be Frame Relay switches or end-user devices.

•Each Frame Relay PVC is composed of multiple segments.

•The DLCI value is local to each segment and is changed as traffic is switched from segment to segment. Two Frame Relay PVC segments exist; one is between PE1 and CE1 and the other is between PE2 and CE2.

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.

•CE1 sends an active status to PE1 if the PVC for CE1 is available. If CE1 is a switch, LMI checks that the PVC is available from CE1 to the user device attached to CE1.

•PE1 sends an active status to CE1 if the following conditions are met:

–A PVC for PE1 is available.

–PE1 has received an MPLS label from the remote PE router.

–An MPLS tunnel label exists between PE1 and the remote PE.

–CE2 reports an Active status to PE2. If CE2 is a switch, LMI checks that the PVC is available from PE1 to the end-user device attached to CE2.

For DTE/DCE configurations, the following LMI behavior exists:

The Frame Relay device accessing the network (DTE) does the polling. The network device (DCE) responds to the LMI polls. Therefore, if a problem exists on the DTE side, the DCE is not aware of the problem, because it does not poll.

For More Information About LMI

For information about LMI, including configuration instructions, see the following document:

Configuring Frame Relay, Configuring the LMI at:

/en/US/docs/ios/12_2/wan/configuration/guide/wcffrely.html#xtocid8

DE/CLP and EXP Mapping on FR/ATMoMPLS VC

The DE/CLP and EXP Mapping on FR/ATMoMPLS VC feature allows you to map the Frame Relay Discard Eligibility (DE) bit or the ATM Congestion Loss Priority (CLP) bit to the MPLS EXP value at the ingress to an MPLS AToM network and to map the MPLS EXP value to the FR-DE or ATM CLP bit at the egress of an MPLS AToM network.

The DE bit indicates that a frame has lower importance than other frames. Similarly, the ATM CLP bit indicates whether the cell may be discarded if it encounters extreme congestion as it moves through the network.

In the figure below, the PE1 tags the incoming packet with the MPLS EXP value and sends the packet to the next hop. At each hop, matching is on the EXP value. At the PE2 egress, however, the packet is no longer MPLS but IP, so matching cannot occur on the EXP value.

Internally, the OSM preserves the EXP value in the QoS group so matching on the QoS group at the PE2 egress provides the same effect as matching on the EXP value.

Figure 1-3 DE/CLP and EXP Mapping

See the following sections:

•Match on ATM CLP Bit

•Match on FR-DE Bit

•Set on ATM CLP Bit

•Set on FR-DE Bit

Match on ATM CLP Bit

Use Match on ATM CLP Bit at the ingress to an MPLS AToM network to map the ATM cell loss priority (CLP) of the packet arriving at an interface to the EXP value, and then apply the desired QoS functionality and actions (for example, traffic policing) to those packets.

Restrictions for Match on ATM CLP Bit

The following restrictions apply:

•This feature is supported on policy maps attached to ATM permanent virtual circuits (PVCs) only.

•This feature is not supported on the OSM-2OC12-ATM-MM or OSM-2OC12-ATM-MM+.

Configuring Match on ATM CLP Bit for Ingress Policy

Perform the following steps to configure Match on ATM CLP Bit for the ingress policy:
Command or Action

Purpose
Step 1
Router# enable
Enables privileged EXEC mode. Enter your password if prompted.
Step 2
Router(config)# configure terminal
Enters global configuration mode.
Step 3
Router(config)# class-map class-name 
Specifies the user-defined name of the traffic class.
Step 4
Router(config-cmap)# match atm clp
Enables packet matching on the basis of the ATM CLP bit set to 1.
Step 5
Router(config-cmap)# policy-map policy-name 
Specifies the name of the traffic policy to configure.
Step 6
Router(config-pmap)# class class-name 
Specifies the name of a predefined traffic class, which was configured with the class-map command, used to classify traffic to the traffic policy.
Step 7
Router(config-pmap-c)# set mpls experimental value
Designates the value to which the MPLS bits are set if the packets match the specified policy map.
Step 8
Router(config)# interface atm interface-number 
Enters interface configuration mode.
Step 9
Router(config-if)# pvc [name] vpi/vci [l2transport] 
Entesr ATM virtual circuit configuration mode.
Step 10
Router(config-if)# service-policy input policy-name 
Attaches a traffic policy to an interface.
The following is an example of a Match on ATM CLP Bit configuration:
Router# conf t
Enter configuration commands, one per line. End with CNTL/Z.
Router(config)#class-map CLP
Router(config-cmap)#match atm clp
Router(config-cmap)#exit
Router(config)#policy-map CLP2EXP
Router(config-pmap)#class CLP
Router(config-pmap-c)#set mpls experimental 1
Router(config-pmap-c)#exit
Router(config-pmap)#interface ATM3/0
Router(config-if)#pvc 1/100
Router(cfg-if-atm-l2trans-pvc)#service-policy input CLP2EXP
Router(cfg-if-atm-l2trans-pvc)#end
Router# 
Use the show policy-map interface command to verify the Match on ATM CLP bit as in the following example:
CFLOW_PE1# show policy-map interface a3/0
ATM3/0/0: VC 1/100 -
Service-policy input: CLP2EXP
Class-map: CLP (match-all)
200 packets, 22400 bytes
5 minute offered rate 2000 bps, drop rate 0 bps
Match: atm clp
QoS Set
mpls experimental imposition 1
Packets marked 200
Class-map: class-default (match-any)
0 packets, 0 bytes
5 minute offered rate 0 bps, drop rate 0 bps
Match: any
CFLOW_PE1#
Match on FR-DE Bit

Use Match on FR-DE Bit at the ingress to an MPLS AToM network to map the Frame Relay discard eligible (DE) bit of the packet arriving at an interface to the EXP value.

Restrictions for Match on FR-DE Bit

The following restriction applies to this feature:

•Use policy matching on the FR-DE as an input policy only.

Configuring Match on FR-DE Bit for Ingress Policy

Perform the following steps to configure Match on FR-DE Bit for the ingress policy:
Command or Action

Purpose
Step 1
Router# enable
Enables privileged EXEC mode. Enter your password if prompted.
Step 2
Router(config)# configure terminal
Enters global configuration mode.
Step 3
Router(config)# class-map class-name 
Specifies the user-defined name of the traffic class.
Step 4
Router(config-cmap)# match fr-de
Matches on packets that have the Frame Relay DE bit set to 1.
Step 5
Router(config-cmap)# policy-map policy-name 
Specifies the name of the traffic policy to configure.
Step 6
Router(config-pmap)# class class-name 
Specifies the name of a predefined traffic class, which was configured with the class-map command, used to classify traffic to the traffic policy.
Step 7
Router(config-pmap-c)# set mpls experimental value
Designates the value to which the MPLS bits are set if the packets match the specified policy map.
Step 8
Router(config)# interface slot/port 
Enters the interface.
Step 9
Router(config)# map-class frame-relay class-map-name
Creates a Frame Relay map class where class-map-name is the name of the class map.
Note In Step 10 below, you can apply the map-class policy to the main interface so that all DLCIs have the same policy or you can apply the map-class policy to each DLCI.
Step 10
Router(config-if)# service-policy input policy-name 
Attaches a traffic policy to an interface.
The following example shows how to configure Match on FR-DE Bit for the ingress policy by applying the map-class policy to the main interface:
osr3# show class-map match_fr-de
 Class Map match-all match_fr-de (id 2)
   Match fr-de 
osr3# show policy fr-de_mpls4
  Policy Map fr-de_mpls4
    Class match_fr-de
      set mpls experimental imposition 4
    Class class-default
      set mpls experimental imposition 4
osr3# show run map-class | begin fr-de_mpls4
map-class frame-relay fr-de_mpls4
 service-policy input fr-de_mpls4
!
map-class frame-relay fr-de_mpls0
 service-policy input fr-de_mpls0
!
osr3# show run int pos1/0
Building configuration...
Current configuration : 196 bytes
!
interface POS1/0
 mtu 5000
 no ip address
 encapsulation frame-relay IETF
 no keepalive
 clock source internal
 pos scramble-atm
 frame-relay intf-type dce
end
connect frompls_1 POS1/0 16 l2transport
 xconnect 11.11.11.11 2001 encapsulation mpls
 !
!
connect frompls_2 POS1/0 17 l2transport
 xconnect 11.11.11.11 2002 encapsulation mpls
 !
!
connect frompls_3 POS1/0 18 l2transport
 xconnect 11.11.11.11 2003 encapsulation mpls
 !
!
osr3# conf t
Enter configuration commands, one per line.  End with CNTL/Z.
osr3(config)#interface POS1/0
osr3(config-if)#frame-relay class fr-de_mpls4
osr3(config-if)#
osr3(config-if)#^Z
osr3# sh run int pos1/0
Building configuration...
Current configuration : 196 bytes
!
interface POS1/0
 mtu 5000
 no ip address
 encapsulation frame-relay IETF
 no keepalive
 clock source internal
 pos scramble-atm
 frame-relay class fr-de_mpls4
 frame-relay intf-type dce
end
Verify the configuration with the show policy-map interface command.
osr3# show policy-map interface pos1/0
 POS1/0: DLCI 16 -
  Service-policy input: fr-de_mpls4
    Class-map: match_fr-de (match-all)
      0 packets, 0 bytes
      5 minute offered rate 0 bps, drop rate 0 bps
      Match: fr-de 
      QoS Set
        mpls experimental imposition 4
           Packets marked 0
    Class-map: class-default (match-any)
      0 packets, 0 bytes
      5 minute offered rate 0 bps, drop rate 0 bps
      Match: any 
      QoS Set
        mpls experimental imposition 4
           Packets marked 0
 POS1/0: DLCI 1007 -
  Service-policy input: fr-de_mpls4
 --More-- 
The following example shows how to configure Match on FR-DE Bit for the ingress policy by applying the map-class policy to the different DLCIs:
osr1# show policy-map fr-de_mpls2
  Policy Map fr-de_mpls2
    Class match_fr-de
      set mpls experimental imposition 2
    Class class-default
      set mpls experimental imposition 2
osr1# show policy-map fr-de_mpls3
  Policy Map fr-de_mpls3
    Class match_fr-de
      set mpls experimental imposition 3
    Class class-default
      set mpls experimental imposition 3
osr1# show class-map match_fr-de
 Class Map match-all match_fr-de (id 1)
   Match fr-de 
osr1# show run map-class | begin fr-de_mpls
map-class frame-relay fr-de_mpls2
 service-policy input fr-de_mpls2
!
map-class frame-relay fr-de_mpls3
 service-policy input fr-de_mpls3
!
osr1# conf t
Enter configuration commands, one per line.  End with CNTL/Z.
osr1(config)# interface pos1/7
osr1(config-if)# frame-relay interface-dlci 16 switched
osr1(config-fr-dlci)# class fr-de_mpls2
osr1(config-fr-dlci)# exit                       
osr1(config-if)#
osr1(config-if)# frame-relay interface-dlci 17 switched
osr1(config-fr-dlci)# class fr-de_mpls3
osr1(config-fr-dlci)#
osr1(config-fr-dlci)# exit
osr1(config-if)#
osr1(config-if)#^Z
osr1#
osr1# show run int pos1/7
Building configuration...
Current configuration : 39671 bytes
!
interface POS1/7
 mtu 5000
 no ip address
 encapsulation frame-relay IETF
 no keepalive
 mls qos trust dscp
 clock source internal
 pos scramble-atm
 frame-relay interface-dlci 16 switched
  class fr-de_mpls2
 frame-relay interface-dlci 17 switched
  class fr-de_mpls3
 frame-relay interface-dlci 18 switched
 frame-relay interface-dlci 19 switched
...
Verify the configuration with the show policy-map interface command.
osr1# show policy interface pos1/7
 POS1/7: DLCI 16 -
  Service-policy input: fr-de_mpls2
    Class-map: match_fr-de (match-all)
      0 packets, 0 bytes
      5 minute offered rate 0 bps, drop rate 0 bps
      Match: fr-de 
      QoS Set
        mpls experimental imposition 2
           Packets marked 0
    Class-map: class-default (match-any)
      0 packets, 0 bytes
      5 minute offered rate 0 bps, drop rate 0 bps
      Match: any 
      QoS Set
        mpls experimental imposition 2
           Packets marked 0
 POS1/7: DLCI 17 -
  Service-policy input: fr-de_mpls3
    Class-map: match_fr-de (match-all)
      0 packets, 0 bytes
      5 minute offered rate 0 bps, drop rate 0 bps
      Match: fr-de 
      QoS Set
        mpls experimental imposition 3
           Packets marked 0
    Class-map: class-default (match-any)
      0 packets, 0 bytes
      5 minute offered rate 0 bps, drop rate 0 bps
      Match: any 
      QoS Set
        mpls experimental imposition 3
           Packets marked 0
osr1#
Set on ATM CLP Bit

Use Set on ATM CLP Bit at the egress of an MPLS AToM network to map the EXP value to the ATM CLP bit.

Restrictions for Set on ATM CLP Bit

The following restrictions apply to this feature:

•This feature is supported on policy maps attached to ATM permanent virtual circuits (PVCs) only.

•This feature is not supported on the OSM-2OC12-ATM-MM or OSM-2OC12-ATM-MM+

Configuring Set on ATM CLP Bit for Egress Policy

Perform the following steps to configure Set on ATM CLP Bit for the ingress policy:
Command or Action

Purpose
Step 1
Router# enable
Enables privileged EXEC mode. Enter your password if prompted.
Step 2
Router(config)# configure terminal
Enters global configuration mode.
Step 3
Router(config)# class-map class-name 
Specifies the user-defined name of the traffic class.
Step 4
Router(config-cmap)# match qos-group qos-group-value 
Identifies a specific quality of service (QoS) group value as a match criterion. The QoS group value has no mathematical significance.

Note The QoS group concept is directly derived from the incoming MPLS EXP value and is valid only with AToM. You cannot use MQC to set QoS group value.
Step 5
Router(config-cmap)# policy-map policy-name 
Specifies the name of the traffic policy to configure.
Step 6
Router(config-pmap)# class class-name 
Specifies the name of a predefined traffic class, which was configured with the class-map command, used to classify traffic to the traffic policy.
Step 7
Router(config-pmap-c)# set atm-clp
Sets the cell loss priority (CLP) bit when a policy map is configured.
Step 8
Router(config)# interface slot/port 
Enters the interface and enters interface configuration mode.
Step 9
Router(config-if)# service-policy input policy-name 
Attaches a traffic policy to an interface.
The following shows how to configure Set on ATM CLP Bit:
arthos# show policy-map qg2clp
 Policy Map qg2clp
   Class qg1
     set atm-clp
arthos# show class-map qg1
Class Map match-all qg1 (id 23)
  Match qos-group 1
arthos# show run int a9/1
interface ATM9/1
no ip address
atm clock INTERNAL
atm mtu-reject-call
mls qos trust dscp
pvc 1/100 l2transport
  encapsulation aal5
  mpls l2transport route 101.101.101.101 1000
  service-policy out qg2clp
Verify the configuration with the show policy-map interface command.
arthos# show policy interface ATM9/1
ATM9/1: VC 1/100 -
 Service-policy output: qg2clp
   Class-map: qg1 (match-all)
     1000 packets, 0 bytes
     5 minute offered rate 0 bps, drop rate 0 bps
     Match: qos-group 1
     QoS Set
       atm-clp
         Packets marked 1000
Set on FR-DE Bit

Use Set on FR-DE Bit at the egress of an MPLS AToM network to map the EXP value to the FR-DE bit.

Configuring Set on FR-DE for Egress Policy

Perform the following steps to configure Set on FR-DE Bit for the egress policy:
Command or Action

Purpose
Step 1
Router# enable
Enables privileged EXEC mode. Enter your password if prompted.
Step 2
Router(config)# configure terminal
Enters global configuration mode.
Step 3
Router(config)# class-map class-name 
Specifies the user-defined name of the traffic class.
Step 4
Router(config-cmap)# match qos-group qos-group-value 
Identifies a specific quality of service (QoS) group value as a match criterion where the range of the qos-group-value is 0-7.
Step 5
Router(config-cmap)# policy-map policy-name 
Specifies the name of the traffic policy to configure.
Step 6
Router(config-pmap)# class class-name 
Specifies the name of a predefined traffic class, which was configured with the class-map command, used to classify traffic to the traffic policy.
Step 7
Router(config-pmap-c)# set fr-de
Changes the DE bit setting in the address field of a Frame Relay frame to 1 for all traffic leaving an interface.
Step 8
Router(config)# interface slot/port 
Enters the interface and enters interface configuration mode.
Note In Step 9 below you can apply the map-class policy to main interface so that all DLCIs have the same policy or you can apply the map-class policy to each DLCI.
Step 9
Router(config-if)# service-policy output policy-name 
Attaches a traffic policy to an interface.
The following shows how to configure Set on FR-DE Bit:
arthos# show policy-map qg2de
 Policy Map qg2de
   Class qg1
     set fr-de
arthos# show class-map qg1
Class Map match-all qg1 (id 23)
  Match qos-group 1
arthos# show run int pos2/2/0
interface POS2/2/0
no ip address
encapsulation frame-relay
frame-relay interface-dlci 16 switched
   class QG2DE
Verify the configuration with the show policy-map interface command.
arthos# show policy interface POS2/2/0
POS2/2/0: DLCI 16 -
 Service-policy output: qg2de
   Class-map: qg1 (match-all)
     1000 packets, 0 bytes
     5 minute offered rate 0 bps, drop rate 0 bps
     Match: qos-group 1
     QoS Set
       fr-de
         Packets marked 1000
How to Configure QoS with AToM

The following QoS features are supported on AToM:

•Marking on CE facing card—(imposition packets) with match criteria, match-dlci, match-any, or class-default.

Note For Marking on CE facing card, match-dcli applies to the FlexWAN module only.

•Shaping on the core-facing card, with match exp, and match-any.

•Shaping on the CE-facing card - (disposition packets) with match-any.

•WRED on the core-facing card with match criteria, match-exp, or match-any

This section explains how to configure QoS with AToM and includes the following procedures:

•How to Set Experimental Bits with AToM

•Setting the Priority of Packets with EXP Bits

•Enabling Traffic Shaping

Note PFC QoS features do not apply to ATMoMPLS and FRoMPLS packets.

How to Set Experimental Bits with AToM

MPLS AToM uses the three experimental bits in a label to determine the queue of packets. You statically set the experimental bits in both the VC label and the LSP tunnel label, because the LSP tunnel label might be removed at the penultimate router. The following sections explain the transport-specific implementations of the EXP bits.

Ethernet over MPLS and EXP Bits

Note The information in this section is for OSM-based EoMPLS only. For information on PFC3BXL QoS, see http://www.cisco.com/univercd/cc/td/doc/product/core/cis7600/software/122sx/swcg/qos.htm.

OSM-based EoMPLS supports the following QoS implementations:

•VLAN interface policies

•Core-facing interface policy

You apply a VLAN interface policy to an individual VLAN. You may configure a unique policy for each individual VLAN. Within a policy, you can classify on 802.1q P bits to set the MPLS experimental bits. You can also implement a single traffic shaper that applies to all traffic within the VLAN.

Note Within a VLAN interface policy, only the shape average and set mpls experimental commands are supported. Within the shape average command, only the cir argument is valid for EoMPLS.

You apply a core-facing interface policy to the EoMPLS uplink interface. This policy applies to traffic from all VLANs. It does not distinguish between different VLANs. Within a policy, you can classify on MPLS experimental bits and configure the following features:

•Class-based traffic shaping

•Class-based weighted fair queuing (CBWFQ)

•Low latency queuing (LLQ)

•Weighted random early detection (WRED)

Note You cannot use both VLAN interface policies and core-facing interface policies at the same time. If you configure QoS for OSM-based EoMPLS, you must select either VLAN interface policies or a core-facing interface policy.

For more information on VLAN interface policies, see "Setting the Priority of Packets with the Experimental Bits" section and "Enabling Traffic Shaping" section.

For more information on core-facing policies, see "Configuring MPLS QoS" section.

For more information on the commands used to enable Quality of Service, see the following documents:

•Modular Quality of Service Command-Line Interface

•Cisco IOS Quality of Service Solutions Command Reference, Release 12.2

Setting the Priority of Packets with the Experimental Bits

Ethernet over MPLS provides Quality of Service (QoS) using the three experimental bits in a label to determine the priority of packets. To support QoS between LERs, set the experimental bits in both the VC and tunnel labels. If you do not assign values to the experimental bits, the priority bits in the 802.1q header's "tag control information" field and are written into the experimental bit fields.

Perform the following steps to set the experimental bits: