34-34
Cisco ME 3800X and 3600X Switch Software Configuration Guide
OL-23400-01
Chapter 34 Configuring MPLS, MPLS VPN, MPLS OAM, and EoMPLS
Enabling EoMPLS
Last local SSS circuit status rcvd: no fault
Last local SSS circuit status sent: not sent
Last local LDP TLV status sent: not sent
Last remote LDP TLV status rcvd: unknown (no remote binding)
MPLS VC labels: local 19, remote unassigned
Group ID: local 0, remote unknown
MTU: local 1500, remote unknown
Remote interface description:
Sequencing: receive disabled, send disabled
VC statistics:
packet totals: receive 0, send 0
byte totals: receive 0, send 0
packet drops: receive 0, send 0
Configuring L2VPN Interworking
Layer 2 transport over MPLS and IP exists for like-to-like attachment circuits, such as
Ethernet-to-Ethernet. L2VPN interworking builds on this functionality by allowing disparate attachment
circuits to be connected. An interworking function facilitates the translation between the different
Layer 2 encapsulations.
For information about L2VPN interworking, see the L2VPN Interworking feature module at this URL:
http://www.cisco.com/en/US/docs/ios/mpls/configuration/guide/mp_l2vpn_intrntwkg.html
Note that the switch does not support ATM interfaces, Point-to-Point Protocol (PPP), or frame relay as
mentioned in this document. It also does not support
Layer 2 Tunnel Protocol Version 3 (L2TPv3).
L2VPN interworking on the ME 3800X and ME 3600X switches works in either Ethernet mode (VC
type 5) or VLAN mode (VC type 4). You specify the mode by entering the interworking {ethernet |
vlan} command in pseudowire-class configuration mode. Although visible in the command-line
interface help, the ip keyword is not supported. Entering the interworking command causes the
attachment circuits to be terminated locally.
The keywords perform these functions:
•
The ethernet keyword causes Ethernet frames to be extracted from the attachment circuit and sent
over the pseudowire. Ethernet end-to-end transmission is assumed. Attachment circuit frames that
are not Ethernet are dropped.
•
The vlan keyword causes VLAN-tagged packets to be extracted and sent over the pseudowire.
Frames that are not VLAN-tagged are dropped.
Beginning in privileged EXEC mode, follow these steps to configure L2VPN VLAN interworking on a
PE router:
Step 1
configure terminal
Enter global configuration mode.
Step 2
pseudowire-class name
Create a pseudowire class with the specified name and enter
pseudowire class configuration mode.
Step 3
encapsulation mpls Specify
tunneling
encapsulation. For AToM, the
encapsulation type is mpls.