Table Of Contents
Ethernet over MPLS for the Cisco 7600 Series Internet Routers
Protocol Tunneling with EoMPLS
Supported Standards, MIBs, and RFCs
Enabling VLAN-Based Ethernet Over MPLS
Setting the Priority of Packets with the Experimental Bits
Displaying the Traffic Policy Assigned to an Interface
Configuring Ethernet over MPLS
Configuring Quality of Service
debug mpls l2transport vlan control
debug mpls l2transport vlan distributed
Ethernet over MPLS for the Cisco 7600 Series Internet Routers
Feature History
This feature module describes the Ethernet over Multiprotocol Label Switching (MPLS) feature, which transports Layer 2 VLAN packets across an MPLS backbone. This document contains information about the benefits of Ethernet over MPLS (EoMPLS) and lists supported platforms. It also provides configuration tasks, examples and related commands.
This document includes the following sections:
•
Supported Standards, MIBs, and RFCs
Feature Overview
This feature allows you to connect two VLAN networks that are in different locations, without using expensive bridges, routers, or switches at the VLAN locations. You can enable the MPLS backbone network to accept Layer 2 VLAN traffic by configuring the label edge routers (LERs) at the both ends of the MPLS backbone.
Adding a point-to-point virtual circuit (VC) requires you to configure the two VC endpoints at the two label edge routers. Only the two LERs at the ingress/egress points of the MPLS backbone know about the VCs dedicated to transporting Layer 2 VLAN traffic. All other routers do not have table entries for the VCs dedicated to transporting layer 2 VLAN traffic.
Benefits
As Internet service providers (ISPs) begin to deploy IP/MPLS backbones, services including frame switching must be supported. The Ethernet over MPLS feature allows an ISP to transport Layer 2 VLAN frames over an MPLS backbone.
Restrictions
The following services are not supported with the Ethernet over MPLS feature:
•
•
•
•
•
•
•
mpls label range
•
–
–
•
–
–
These sections describe EoMPLS features supported:
•
Multilevel Labeling
Label edge routers (LERs) connected to the MPLS backbone perform label imposition and disposition. The imposition LER encapsulates the Layer 2 VLAN packet into an MPLS PDU to transport it across the backbone to the disposition LER. The disposition LER takes the MPLS PDU, de-encapsulates the Layer 2 VLAN packet, and delivers it to the correct interface.
When the imposition LER encapsulates a Layer 2 VLAN packet to route it across the MPLS backbone, it includes a label stack with two levels of labels:
•
•
The MPLS backbone uses the IGP labels to transport the VLAN packet from the ingress to the egress LER. The egress LSR uses the VC-based label to select the outgoing interface for the VLAN packet.
For configuration information, see the "Enabling VLAN-Based Ethernet Over MPLS" section.
Quality of Service Support
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, you set the experimental bits in both the VC and tunnel labels. The experimental bits need to be set in the VC label because the tunnel label is popped at the penultimate router.
802.1Q Tunneling with EoMPLs
802.1Q tunneling enables service providers to use a single VLAN to support customers who have multiple VLANs, while preserving customer VLAN IDs and keeping traffic in different customer VLANs segregated.
For configuration and general information on 802.1Q tunneling, refer to the Cisco 7600 Series Internet Router IOS Software Configuration Guide, Release 12.1(11b)EX.
To support 802.1Q tunneling in a topology where a Layer 2 device connects to an MPLS network through a Cisco 7600 series Internet Router or a Catalyst 6500 series switch functioning as a PE, the ingress LAN port on the PE that receives the 802.1Q-in-802.1Q encapsulated traffic is configured as a tunnel port. When this ingress 802.1Q tunnel port receives 802.1Q-in-802.1Q traffic from a CLE, it forwards the frame to the egress WAN port where an MPLS tag is added to the frame header before it is mapped to a VC and forwarded to the next MPLS PE.
By specifying the VC-type in the mpls l2transport route command as either VLAN-based or port-based, you can configure an EoMPLS tunnel to forward traffic based on either the customer VLAN or the entire Ethernet port. By default EoMPLS forwarding on the Catalyst 6500 series switch and the Cisco 7600 series Internet Router is VLAN-based. To forward 802.1Q-in-802.1Q encapsulated traffic through the MPLS core to a specific recipient on the other side of the MPLS network, configure the VC type as port-based. To forward 802.1Q-in-802.1Q encapsulated traffic from an access device to a PE router, configure the VC type as VLAN-based. For configuration information, see the "Enabling Quality of Service" section.
Protocol Tunneling with EoMPLS
Support for protocol tunneling over an EoMPLS link allows protocol data units (PDUs) (CDP, STP, and VTP) to be tunneled through an MPLS network. To support protocol tunneling in a topology where a Layer 2 device connects to an MPLS network through a Cisco 7600 series Internet Router or a Catalyst 6500 series switch functioning as a PE, the ingress LAN port on the PE that receives the Layer 2 protocol traffic is configured as a tunnel port and the Layer 2 protocol traffic is encapsulated before it is forwarded over the MPLS network.
For general overview and configuration information for protocol tunneling on the Cisco 7600 series Internet Router and the Catalyst 6500 series switch, refer to the Software Configuration Guides and Command References for these platforms at the following URLs:
http://www.cisco.com/univercd/cc/td/doc/product/core/cis7600/index.htm
http://www.cisco.com/univercd/cc/td/doc/product/lan/cat6000/index.htm
Related Documents
Refer to the following documents for more information:
•
•
•
•
•
Supported Platforms
The Ethernet over MPLS feature is supported on the Cisco 7600 Series Internet router at the edge with the following modules
•
Note
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
Note
Supported Standards, MIBs, and RFCs
Standards
This feature supports the following IETF draft documents:
•
•
MIBs
None.
RFCs
This feature supports the following RFCs:
•
Prerequisites
Before configuring Ethernet over MPLS, make sure you configure the following:
•
•
•
http://www.cisco.com/univercd/cc/td/doc/product/lan/cat6000/121_8aex/swconfig/layer2.htm
•
Configuration Tasks
Perform the following configuration tasks to enable Ethernet over MPLS:
1.
3.
4.
Enabling VLAN-Based Ethernet Over MPLS
To configure MPLS to transport Layer 2 VLAN packets between two endpoints, perform the following steps on the provider edge (PE) routers.
Note
Enabling Port-Based EoMPLS
To support 802.1Q-in-802.1Q traffic and native Ethernet traffic over EoMPLS, configure port-based EoMPLS by performing this task:
Verifying the Configuration
To verify and display the configuration of Layer 2 VLAN transport over MPLS tunnels, perform the following steps:
Step 1
Router# show ip interface briefInterface IP-Address OK? Method Status ProtocolVlan2 10.1.2.58 YES NVRAM up upVlan4 unassigned YES NVRAM up upVlan101 unassigned YES NVRAM up upGigabitEthernet6/1 172.31.255.255 YES NVRAM administratively down downGigabitEthernet6/2 unassigned YES NVRAM administratively down downGigabitEthernet6/3 172.31.255.255 YES NVRAM up upGigabitEthernet6/4 unassigned YES NVRAM administratively down downLoopback0 172.16.0.0 YES NVRAM upStep 2
Router# show mpls ldp discoveryLocal LDP Identifier:172.31.255.255:0Discovery Sources:Interfaces:GigabitEthernet6/3 (ldp): xmit/recvLDP Id: 192.168.2.10:0Targeted Hellos:172.16.0.1 -> 172.20.0.1 (ldp): active/passive, xmit/recvLDP Id: 172.20.0.1:0Step 3
Router# show mpls ldp neighborsPeer LDP Ident: 192.168.2.10:0; Local LDP Ident 172.16.0.1:0TCP connection: 192.168.2.10.646 - 172.16.0.1.11001State: Oper; Msgs sent/rcvd: 246/256; DownstreamUp time: 01:36:12LDP discovery sources:GigabitEthernet6/3Addresses bound to peer LDP Ident:172.16.0.22 172.20.0.1 192.168.2.68 172.22.0.2172.28.0.2Peer LDP Ident: 172.20.0.1:0; Local LDP Ident 172.16.0.1:0TCP connection: 172.20.0.1.11002 - 172.16.0.1.646State: Oper; Msgs sent/rcvd: 127/125; DownstreamUp time: 01:35:23LDP discovery sources:Targeted Hello 153.10.0.1 -> 153.20.0.1, active, passiveAddresses bound to peer LDP Ident:172.16.0.22 172.20.0.1 192.168.2.68 172.22.0.2172.28.0.2Step 4
•
•
•
•
•
•
Router# show mpls forwarding-tableLocal Outgoing Prefix Bytes tag Outgoing Next Hoptag tag or VC or Tunnel Id switched interface16 Untagged 10.255.254.254/32 0 Vl2 192.168.0.117 Pop tag 172.30.0.0/16 0 Gi6/3 172.16.0.118 Pop tag 172.20.0.0/16 0 Gi6/3 172.16.0.119 148 172.29.0.0/16 0 Gi6/3 172.16.0.120 77 172.20.0.1/32 6308338115 Gi6/3 172.16.0.123 Untagged EoMPLS(4) 94538 Vl4 point2point24 Untagged EoMPLS(101) 847 Vl101 point2pointStep 5
Router# show mpls l2transport vcTransport Client VC Trans Local Remote TunnelVC ID Intf State Type VC Label VC Label Label100 Vl100 UP ether 115 115 4116301 Vl301 UP vlan 316 316 4116Step 6
Router# show mpls l2transport vc detailvcid:100, type:ether , local groupid:97, remote groupid:99 (vc is up)client:Vl100 is up, destination:153.20.0.1, Peer LDP Ident:153.20.0.1:0local label:115, remote label:115, tunnel label:4116outgoing interface:PO3/2, next hop:point2pointLocal MTU:1500, Remote MTU:1500Remote interface description:Vlan100imposition:LC Programmedcurrent imposition/last disposition slot:3/32Packet totals(in/out):9463762/14760351byte totals(in/out):1348596160/1993531920vcid:301, type:vlan , local groupid:98, remote groupid:101 (vc is up)client:Vl301 is up, destination:153.20.0.1, Peer LDP Ident:153.20.0.1:0local label:316, remote label:316, tunnel label:4116outgoing interface:PO3/2, next hop:point2pointLocal MTU:1500, Remote MTU:1500Remote interface description:Vlan301imposition:LC Programmedcurrent imposition/last disposition slot:3/32Packet totals(in/out):0/0byte totals(in/out):0/0Enabling Quality of Service
The following sections detail the Modular QoS CLI commands for enabling QoS on the ingress PE router.
Note
Note
For more information on the commands used to enable Quality of Service, see the following documents:
•
•
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:
Note
Enabling Traffic Shaping
Traffic shaping limits the rate of transmission of data. Average rate shaping limits the transmission rate to the committed information rate (CIR). To add traffic shaping, issue the following commands:
If the egress MPLS tunnel is carried on an OSM WAN interface configured for fair queueing, the shape value is rounded to the nearest multiple of the link rate divided by 255. If the shape value is lower than the link rate divided by 255, it is rounded up to link rate divided by 255.
This example shows how the shape value is rounded:
Router# show pol p2Policy Map p2class any-pktshape average 2000000 8000 8000Router# show pol intVlan101service-policy input:p2class-map:any-pkt (match-all)2018169 packets, 4575195376 bytes30 second offered rate 295768000 bps, drop rate 0 bpsmatch:anyqueue size 0, queue limit 0packets input 40492, packet drops 1977677tail/random drops 0, no buffer drops 0, other drops 1977677shape:cir 2000000, Bc 8000, Be 8000(shape parameter is rounded to 2439000 due to granularity)input bytes 40847436, shape rate 1874000 bpsclass-map:class-default (match-any)0 packets, 0 bytes30 second offered rate 0 bps, drop rate 0 bpsmatch:any0 packets, 0 bytes30 second rate 0 bpsDisplaying the Traffic Policy Assigned to an Interface
To display the traffic policy attached to an interface, issue the following command:
Router# show policy-map vlan50service-policy input: badgerclass-map: blue (match-all)0 packets, 0 bytes30 second offered rate 0 bps, drop rate 0 bpsmatch: anyqueue size 0, queue limit 2packets input 0, packet drops 0tail/random drops 0, no buffer drops 0, other drops 0shape: cir 2000000, Bc 8000, Be 8000output bytes 0, shape rate 0 bpsclass-map: class-default (match-any)0 packets, 0 bytes30 second offered rate 0 bps, drop rate 0 bpsmatch: any0 packets, 0 bytes30 second rate 0 bpsConfiguration Examples
The following sections list the commands for enabling MPLS to transport Layer 2 VLAN packets between two endpoints,. Figure 1 illustrates the network configuration that the configuration commands reference.
Figure 1 Ethernet Over MPLS Configuration
Configuring Ethernet over MPLS
The commands for router 1 and router 2 configure Ethernet over MPLS to transport Layer 2 VLAN packets between two endpoints. The example includes the following assumptions:
•
•
•
–
–
–
The mpls ldp discovery targeted-hello command enables the router to respond to requests for targeted Hello messages. By default, the router ignores these requests from other routers. The argument vlan-edge-acl is an access list.
Router 1 Configuration
interface Loopback0 !Configure a loopback interface.ip address 172.22.255.255 255.255.255.255mpls label protocol ldp !Use LDP label distribution.mpls ldp router-id loopback0mpls ldp discovery targeted-hello accept from vlan-edge-aclinterface vlan1 !Configure a VLAN interface and specifympls l2transport route 192.168.255.255 55 !the VC ID for traffic over the VLAN.interface Ge-Wan61/0 !Configure interface to MPLS core.ip address 172.16.2.2 255.255.255.0no negotiation autotag-switching iprouter ospf 10 !Configure OSPF routing.passive-interface Loopback0network 172.22.255.255 0.0.0.0 area 0network 192.16.255.255 0.0.0.255 area 0ip access-list standard vlan-edge-acl !Targeted hello access listpermit 192.168.255.255Router 2 Configuration
interface Loopback0 !Configure a loopback interface.ip address 192.168.255.255 255.255.255.255mpls label protocol ldp !Use LDP label distribution.mpls ldp router-id loopback0mpls ldp discovery targeted-hello accept from vlan-edge-aclinterface vlan2 !Configure a VLAN interface and specifympls l2transport route 172.22.255.255 50 !the VC ID for traffic over the VLAN.interface Ge-Wan2/0 !Configure interface to MPLS core.ip address 172.16.7.3 255.255.255.0no negotiation autotag-switching iprouter ospf 10 !Configure OSPF routing.passive-interface Loopback0network 192.168.255.255 0.0.0.0 area 0network 172.16.255.255 0.0.0.255 area 0ip access-list standard vlan-edge-acl !Targeted hello access listpermit 172.22.255.255Configuring Port-Based EoMPLS
Figure 2 shows a topology with an asymmetric configuration where 802.1Q-in-802.1Q traffic is forwarded by means of EoMPLS over an MPLS network.
Figure 2 Asymmetric EoMPLS Configuration
In the example in Figure 2, the ingress Layer 2 port on PE1, gigabitethernet 3/1, is configured for 802.1Q tunneling and to accept VLAN 100 traffic. On PE1, VLAN interface 100 is configured for port-based EoMPLS forwarding, with the loopback address of PE2 as the destination IP address. When traffic from VLANs 10-50 arrives from CE1 on gigabitethernet 3/1 on PE1, it is encapsulated in VLAN 100 and forwarded to the egress WAN interface POS 4/1, which is configured for MPLS forwarding
PE1 Layer 2 port configuration:
interface gigabitethernet3/1switchportswitchport mode dot1qtunnelswitchport access vlan 100PE1 Interface VLAN configuration:
interface vlan 100mpls l2transport 1.1.1.1 111 vc-type etherPE1 Layer 3 WAN port configuration
interface pos 4/1ip address 170.16.1.1 255.255.255.0tag-switching ipOn PE2 the ingress Layer 3 WAN interface POS 2/1 is configured for MPLS forwarding. VLAN interface 100 is configured for port-based EoMPLS forwarding, with the loopback address of PE1 as the destination address. The egress Layer 2 port gigabitethernet 3/2 is configured for 802.1Q tunneling and to accept VLAN 100 traffic.
PE2 Layer 3 WAN configuration:
interface POS 2/1ip address 172.16.2.2 255.255.255.0tag-switching ipPE2 Interface VLAN configuration:
interface vlan 100mpls l2transport 2.2.2.2 111 vc-type etherPE2 Layer 2 port Configuration:
interface gigabitethernet 3/2switchportswitchport mode dot1qtunnelswitchport access vlan 100Configuring Quality of Service
The following example show how to configure QoS on the VLAN.
class-map bluematch cos 1 2 3!policy-map badgerclass blueset mpls experimental 1class class-defaultshape average 2000000 8000 8000!interface vlan50no ip addressno ip mroute-cacheload-interval 30mpls l2transport route 192.168.255.255 50service-policy input badgerno cdp enableCommand Reference
This section describes the following commands:
•
•
debug mpls l2transport vlan control
To enable debug messages about the control of traffic transported between Layer 2 VLAN and MPLS, use the debug mpls l2transport vlan control EXEC command. To disable the debug messages about transport control, use the no form of this command.
[no] debug mpls l2transport vlan control
Syntax Description
This command has no arguments or keywords.
Defaults
No default behavior or values.
Command History
Examples
The following example enables debug messages about the control of traffic between Layer 2 VLANs and MPLS:
Router# debug mpls l2transport vlan controlEthernet VLAN transport over MPLS, Control interactions debugging is onRouter# config tEnter configuration commands, one per line. End with CNTL/Z.Router(config)# int vlan2Router(config-if)# shutRouter(config-if)#*May 25 12:18:33: ATOM_TRANS: atom_if_state_change from Vlan2*May 25 12:18:33: ATOM_TRANS: Withdrawing all EoMPLS vcs for lgroupid 8*May 25 12:18:33: ATOM_TRANS: sending extended withdraw_bind for vcid 0to 12.0.0.1, local groupid 8*May 25 12:18:33: ATOM_TRANS: holding down local label 21*May 25 12:18:33: ATOM_TRANS: clearing imp. rewrite for vcid = 2Router(config-if)#*May 25 12:18:35: ATOM_TRANS: freeing held label 21Router(config-if)#*May 25 12:18:35: %LINK-5-CHANGED: Interface Vlan2, changed state toadministratively down*May 25 12:18:36: %LINEPROTO-5-UPDOWN: Line protocol on Interface Vlan2,changed state to downRouter(config-if)# no shutRouter(config-if)#*May 25 12:19:57: ATOM_TRANS: atom_if_state_change from Vlan2*May 25 12:19:57: ATOM_TRANS: Withdrawing all EoMPLS vcs for lgroupid 8*May 25 12:19:57: ATOM_TRANS: sending extended withdraw_bind for vcid 0to 12.0.0.1, local groupid 8Router(config-if)#*May 25 12:19:59: %LINK-3-UPDOWN: Interface Vlan2, changed state to upRouter(config-if)#*May 25 12:19:59: ATOM_TRANS: sending bind for vcid 2 to 12.0.0.1, localgroupid 8*May 25 12:19:59: ATOM_TRANS: sending request_bind for vcid 2 to12.0.0.1, local groupid 8*May 25 12:19:59: ATOM_TRANS: Stale tfib event discarded (12.0.0.1)*May 25 12:19:59: ATOM_TRANS: Stale tfib event discarded (12.0.0.1)*May 25 12:19:59: ATOM_TRANS: Stale tfib event discarded (12.0.0.1)*May 25 12:19:59: ATOM_TRANS: processing tfib event for 12.0.0.1*May 25 12:19:59: ATOM_TRANS: received BIND from 12.0.0.1:0 remote group id: 8 vc_id: 2 label: 21*May 25 12:19:59: ATOM_TRANS: Done setting imp.rewrite for vcid = 2parent dest 12.0.0.1*May 25 12:20:00: %LINEPROTO-5-UPDOWN: Line protocol on Interface Vlan2,changed state to updebug mpls l2transport vlan distributed
To enable the debug messages about label imposition and label disposition on line cards, use the debug mpls l2transport vlan distributed EXEC command. To disable the debug messages about label imposition and label disposition on line cards, use the no form of this command.
[no] debug mpls l2transport vlan distributed
Syntax Description
This command has no arguments or keywords.
Defaults
No default behavior or values.
Command History
Examples
The following example enables debug messages related to the process of label imposition/disposition:
Router# debug mpls l2transport vlan distributedEthernet VLAN transport over MPLS, Distributed switching debugging is onRouter# config tEnter configuration commands, one per line. End with CNTL/Z.Router(config)# int vlan2Router(config-if)# shutRouter(config-if)#*May 25 12:22:04: ETH_TRANS: removing label disposition info for vcid:0from all slots*May 25 12:22:04: ETH_TRANS: slot(3) Client(Vlan2)'s if_number(10)*May 25 12:22:04: ETH_TRANS: label(0) outlabel(0)*May 25 12:22:04: ETH_TRANS: clear_vc(1), vcid(2), vc label(8388611),dest(12.0.0.1)Router(config-if)#*May 25 12:22:06: %LINK-5-CHANGED: Interface Vlan2, changed state toadministratively down*May 25 12:22:07: %LINEPROTO-5-UPDOWN: Line protocol on Interface Vlan2,changed state to downRouter(config-if)# no shutRouter(config-if)#*May 25 12:22:15: %LINK-3-UPDOWN: Interface Vlan2, changed state to up*May 25 12:22:15: ETH_TRANS: disposition change dest:12.0.0.1 vcid:2,(none) -> (all) (queued)*May 25 12:22:15: ETH_TRANS: sending label (21) disposition info forvcid:2 vlan:2 to all slots*May 25 12:22:15: taginfo flag(20), ti_max_index(16), remote_label(22)*May 25 12:22:15: GigabitEthernet3/3*May 25 12:22:15: GigabitEthernet3/2*May 25 12:22:15: GigabitEthernet3/3*May 25 12:22:15: GigabitEthernet3/2*May 25 12:22:15: GigabitEthernet3/3*May 25 12:22:15: GigabitEthernet3/2*May 25 12:22:15: GigabitEthernet3/3*May 25 12:22:15: GigabitEthernet3/2*May 25 12:22:15: GigabitEthernet3/3*May 25 12:22:15: GigabitEthernet3/2*May 25 12:22:15: GigabitEthernet3/3*May 25 12:22:15: GigabitEthernet3/2*May 25 12:22:15: GigabitEthernet3/3*May 25 12:22:15: GigabitEthernet3/2*May 25 12:22:15: GigabitEthernet3/3*May 25 12:22:15: GigabitEthernet3/2*May 25 12:22:15: ETH_TRANS: output slot (3), port (3)*May 25 12:22:15: ETH_TRANS: slot(3) Client(Vlan2)'sif_number(10)*May 25 12:22:15: ETH_TRANS: label(18) outlabel(18)*May 25 12:22:15: ETH_TRANS: clear_vc(0), vcid(2), vc label(22),dest(12.0.0.1)*May 25 12:22:16: %LINEPROTO-5-UPDOWN: Line protocol on Interface Vlan2,changed state to upRouter(config-if)#mpls l2transport route
To enable routing of Layer 2 VLAN packets over a specified VC, use the mpls l2transport route interface command. To disable routing over the specified VC, use the no form of this command.
mpls l2transport route destination vc-id
no mpls l2transport route destination vc-id
Syntax Description
destination
Specifies IP address of the router to which the VC is destined.
vc-id
Assigns a VC ID to a router. The VC ID must be unique to each VC.
Defaults
No default behavior or values.
Command Modes
Interface configuration
Command History
Usage Guidelines
An MPLS Layer 2 VLAN VC runs across an MPLS cloud to connect VLAN interfaces on two PE routers.
Use this command on the VLAN interface of each PE router to route Layer 2 VLAN packets across the MPLS cloud to the VLAN interface of the other PE router. Specify the IP address of the other PE router for the destination parameter. Do not specify the IP address of the router from which you are issuing the command.
You can choose any number for the VC ID. However, the VC ID must be unique to the VC. Therefore, in large networks, it may be necessary to track the VC ID assignments to ensure that a VC ID does not get assigned twice.
Routed VCs are supported on main interfaces, not subinterfaces.
Examples
In the following example, two routers are named PE1 and PE2. The example shows how they establish a VC to transport Layer 2 VLAN packets. PE1 has IP address 172.16.0.1. PE2 has IP address 192.168.0.1. The VC ID is 50.
At PE1, you issue the following commands:
PE1_router (config)# interface vlan3PE1_router(config-if)# mpls l2transport route 172.16.0.1 50At PE2, you issue the following commands:
PE2_router (config)# interface vlan4PE2_router(config-if)# mpls l2transport route 192.168.0.1 50show mpls l2transport vc
To display the state of VCs on a router, use the show mpls l2transport vc EXEC command.
show mpls l2transport vc [summary] | [vc-id ] | [vc-id-min vc-id-max] [detail]
Syntax Description
Defaults
No default behavior or values.
Command Modes
EXEC
Command History
12.1(8a)E
This command was introduced.
12.1(11b)EX1
The vc-type output field was introduced.
Examples
The following example shows the status of the VCs on the router.
Router# show mpls l2transport vcTransport Client VC Trans Local Remote TunnelVC ID Intf State Type VC Label VC Label Label100 Vl100 UP ether 115 115 4116301 Vl301 UP vlan 316 316 4116Table 1describes the significant fields displayed in the output.
Table 1 show mpls l2transport vc Field Descriptions
The following example shows the output of the summary keyword. The first part of the example shows VC information for the interfaces on the PE router. The second part of the example shows how many VCs have been configured for destination 13.0.0.1.
Router# show mpls l2transport vc summaryMPLS interface VC summary:interface: Gi8/1, programmed imposition vcs: 1interface: Gi8/3, programmed imposition vcs: 1VC summary (active/non-active) by destination:destination: 13.0.0.1, Number of locally configured vc(s): 2The following example shows detailed information about currently routed VCs on the router interfaces:
Router# show mpls l2transport vc detailvcid:100, type:ether , local groupid:97, remote groupid:99 (vc is up)client:Vl100 is up, destination:153.20.0.1, Peer LDP Ident:153.20.0.1:0local label:115, remote label:115, tunnel label:4116outgoing interface:PO3/2, next hop:point2pointLocal MTU:1500, Remote MTU:1500Remote interface description:Vlan100imposition:LC Programmedcurrent imposition/last disposition slot:3/32Packet totals(in/out):9463762/14760351byte totals(in/out):1348596160/1993531920vcid:301, type:vlan , local groupid:98, remote groupid:101 (vc is up)client:Vl301 is up, destination:153.20.0.1, Peer LDP Ident:153.20.0.1:0local label:316, remote label:316, tunnel label:4116outgoing interface:PO3/2, next hop:point2pointLocal MTU:1500, Remote MTU:1500Remote interface description:Vlan301imposition:LC Programmedcurrent imposition/last disposition slot:3/32Packet totals(in/out):0/0byte totals(in/out):0/0Table 2describes the significant fields displayed in the output.
Table 2 show mpls l2transport vc detail Field Descriptions
