The documentation set for this product strives to use bias-free language. For the purposes of this documentation set, bias-free is defined as language that does not imply discrimination based on age, disability, gender, racial identity, ethnic identity, sexual orientation, socioeconomic status, and intersectionality. Exceptions may be present in the documentation due to language that is hardcoded in the user interfaces of the product software, language used based on RFP documentation, or language that is used by a referenced third-party product. Learn more about how Cisco is using Inclusive Language.
Layer 2 Virtual Private Network (L2VPN) Interworking allows you to connect disparate attachment circuits. This feature module explains how to configure the following L2VPN Interworking features:
Your software release may not support all the features documented in this module. For the latest feature information and caveats, see the release notes for your platform and software release. To find information about the features documented in this module, and to see a list of the releases in which each feature is supported, see the Feature Information Table at the end of this document.
Use Cisco Feature Navigator to find information about platform support and Cisco software image support. To access Cisco Feature Navigator, go to www.cisco.com/go/cfn. An account on Cisco.com is not required.
Before you configure L2VPN Interworking on a router:
To enable the feature bundle, enter the hw-module slot np mode feature command in global configuration mode as follows:
Router# configure terminal Router(config)# hw-module slot slot-number np mode feature
This section lists general restrictions that apply to L2VPN Interworking. Other restrictions that are platform-specific or device-specific are listed in the following sections.
The following line cards are supported on the Cisco 7600 series router. The table below shows the line cards that are supported on the WAN (ATM, Frame Relay, or PPP) side of the interworking link. The second table below shows the line cards that are supported on the Ethernet side of the interworking link. For more details on the Cisco 7600 routers supported shared port adapters and line cards, see the Release Notes for Cisco IOS Release 12.2SR for the Cisco 7600 Series Routers.
Table 1 | Cisco 7600 Series Routers: Supported Line Cards for the WAN Side |
Interworking Type |
Core-Facing Line Cards |
Customer-Edge Line Cards |
---|---|---|
Ethernet (bridged) (ATM and Frame Relay) |
Any |
EflexWAN SIP-200 SIP-400 |
IP (routed) (ATM, Frame Relay, and PPP) |
Any |
EflexWAN SIP-200 |
Table 2 | Cisco 7600 Series Routers: Supported Line Cards for the Ethernet Side |
Interworking Type |
Ethernet over MPLS Mode |
Core-Facing Line Cards |
Customer-Edge Line Cards |
---|---|---|---|
Ethernet (bridged) |
Policy feature card (PFC) based |
Any, except optical service module (OSM) and ES40 |
Catalyst LAN SIP-600 |
Ethernet (bridged) |
Switched virtual interface (SVI) based |
EflexWAN ES20 ES+40 SIP-200 SIP-400 SIP-600 |
Catalyst LAN EflexWAN (with MPB) ES20 ES+40 SIP-200 (with MPB) SIP-400 (with MPB) SIP-600 |
Ethernet (bridged) |
Scalable (with E-MPB) |
Any, except OSM |
ES20 SIP-600 and SIP-400 with Gigabit Ethernet (GE) SPA |
IP (routed) |
PFC-based |
Catalyst LAN SIP-600 Note: PFC-based mode is not supported with routed interworking in Cisco IOS Release 12.2(33)SRD. Use SVI, Scalable, or Ethernet virtual connection (EVC) based Ethernet over MPLS (EoMPLS) instead. |
Catalyst LAN SIP-600 Note: PFC-based mode is not supported with routed interworking in Cisco IOS Release 12.2(33)SRD. Use SVI, Scalable, or EVC-based EoMPLS instead. |
IP (routed) |
SVI-based |
Any, except Catalyst LAN and OSM. |
Catalyst LAN EflexWAN (with MPB) ES20 SIP-200 (with MPB) SIP-400 (with MPB) SIP-600 |
The following restrictions apply to the Cisco 7600 series routers and L2VPN Interworking:
For more information about hardware requirements on the Cisco12000 series routers, see the Cross-Platform Release Notes for Cisco IOS Release 12.0S.
For QOS support on the Cisco 12000 series routers, see Any Transport over MPLS (AToM): Layer 2 QoS (Quality of Service) for the Cisco 12000 Series Router
The Cisco 12000 series Internet router does not support L2VPN Interworking with PPP and high-level data link control (HDLC) transport types in Cisco IOS releases earlier than Cisco IOS Release 12.0(32)S.
In Cisco IOS Release 12.0(32)S and later releases, the Cisco 12000 series Internet router supports L2VPN interworking for Frame Relay over MPLS and PPP and HDLC over MPLS only on the following shared port adapters (SPAs):
On the Cisco 12000 series Internet router, Ethernet (bridged) interworking is not supported for L2TPv3. Only IP (routed) interworking is supported.
IP (routed) interworking is not supported in an L2TPv3 pseudowire that is configured for data sequencing (using the sequencing command).
In Cisco IOS Release 12.0(32)SY and later releases, the Cisco 12000 series Internet router supports L2VPN Interworking over L2TPv3 tunnels in IP mode on ISE and Engine 5 line cards as follows:
For more information, refer to Layer 2 Tunnel Protocol Version 3.
The only frame format supported for L2TPv3 interworking on Engine 5 Ethernet SPAs is Ethernet Version 2 (also known as Ethernet II) with the Ether type 0x0800 value set as Internet Protocol Payload and (optionally) 802.1q VLAN. Ethernet packets with other Ethernet frame formats are dropped.
The Cisco Remote Ethernet Port Shutdown feature (which minimizes potential data loss after a remote link failure) is supported only on the following Engine 5 Ethernet SPAs:
For more information about this feature, refer to Any Transport over MPLS (AToM): Remote Ethernet Port Shutdown.
The table below shows the different combinations of transport types supported for L2VPN interworking on Engine 3 and Engine 5 SPA interfaces connected through an attachment circuit over MPLS or L2TPv3.
Table 3 | Engine 3 and Engine 5 Line Cards/SPAs Supported for L2VPN Interworking |
Attachment Circuit 1 (AC1) |
Attachment Circuit 2 (AC2) |
Interworking Mode |
AC1 Engine Type and Line Card/SPA |
AC2 Engine Type and Line Card/SPA |
---|---|---|---|---|
Frame Relay |
Frame Relay |
IP |
Engine 5 POS and channelized |
Engine 3 ATM line cards |
Frame Relay |
ATM |
Ethernet |
Engine 5 POS and channelized |
Engine 3 ATM line cards |
Frame Relay |
ATM |
IP |
Engine 5 POS and channelized |
Engine 3 ATM line cards |
Frame Relay |
Ethernet |
Ethernet |
Engine 5 POS and channelized |
Engine 5 Gigabit Ethernet |
Frame Relay |
Ethernet |
IP |
Engine 5 POS and channelized |
Engine 5 Gigabit Ethernet |
Frame Relay |
VLAN |
Ethernet |
Engine 5 POS and channelized |
Engine 5 Gigabit Ethernet |
Frame Relay |
VLAN |
IP |
Engine 5 POS and channelized |
Engine 5 Gigabit Ethernet |
Ethernet |
Ethernet |
Ethernet |
Engine 5 Gigabit Ethernet |
Engine 5 Gigabit Ethernet |
Ethernet |
Ethernet |
IP |
Engine 5 Gigabit Ethernet |
Engine 5 Gigabit Ethernet |
Ethernet |
VLAN |
Ethernet |
Engine 5 Gigabit Ethernet |
Engine 5 Gigabit Ethernet |
Ethernet |
VLAN |
IP |
Engine 5 Gigabit Ethernet |
Engine 5 Gigabit Ethernet |
ATM |
Ethernet |
Ethernet |
Engine 3 ATM line cards |
Engine 5 Gigabit Ethernet |
ATM |
Ethernet |
IP |
Engine 3 ATM line cards |
Engine 5 Gigabit Ethernet |
On the Cisco 12000 series Engine 3 line card, Network Layer Protocol ID (NLPID) encapsulation is not supported in routed mode; and neither NLPID nor AAL5MUX is supported in bridged mode.
In an L2VPN Interworking configuration, after you configure L2TPv3 tunnel encapsulation for a pseudowire using the encapsulation l2tpv3command, you cannot enter the interworking ethernet command.
Ethernet packets with other Ethernet frame formats are dropped.
The following restrictions apply to ATM AAL5 Interworking:
Everything else is dropped.
The following restrictions apply to Ethernet/VLAN interworking:
(If you enable the L2VPN Interworking: VLAN Enable/Disable Option for AToM feature with the interworking vlan command, VLAN ID is included as part of the Ethernet frame. See the VLAN Interworking for more information. )
The following restrictions apply to the L2VPN Interworking: VLAN Enable/Disable Option for AToM feature, which allows the VLAN ID to be included as part of the Ethernet frame:
For example, both PE1 and PE2 use Ethernet interfaces, and VLAN interworking is specified on PE1 only. PE2 is not configured with an interworking type and cannot autosense the interworking type. The result is an incompatible state where the VC remains in the down state.
On the other hand, if PE1 uses an Ethernet interface and VLAN interworking is enabled (which will enforce VLAN as the VC type), and PE2 uses a VLAN interface and interworking is not enabled (which causes PE2 to use Ethernet as its default VC type), PE2 can autosense and negotiate the interworking type and select VLAN as the VC type.
The table below shows the AC types, interworking options, and VC types after negotiation.
Table 4 | Negotiating Ethernet and VLAN Interworking Types |
PE1 AC Type |
Interworking Option |
PE2 AC Type |
Interworking Option |
VC Type after Negotiation |
---|---|---|---|---|
Ethernet |
none |
Ethernet |
none |
Ethernet |
Vlan |
none |
Ethernet |
none |
Ethernet |
Ethernet |
none |
Vlan |
none |
Ethernet |
Vlan |
none |
Vlan |
none |
Ethernet |
Ethernet |
Vlan |
Ethernet |
none |
Incompatible |
Vlan |
Vlan |
Ethernet |
none |
Incompatible |
Ethernet |
Vlan |
Vlan |
none |
Vlan |
Vlan |
Vlan |
Vlan |
none |
Vlan |
Ethernet |
none |
Ethernet |
Vlan |
Incompatible |
Vlan |
none |
Ethernet |
Vlan |
Vlan |
Ethernet |
none |
Vlan |
Vlan |
Incompatible |
Vlan |
none |
Vlan |
Vlan |
Vlan |
Ethernet |
Vlan |
Ethernet |
Vlan |
Vlan |
Vlan |
Vlan |
Ethernet |
Vlan |
Vlan |
Ethernet |
Vlan |
Vlan |
Vlan |
Vlan |
Vlan |
Vlan |
Vlan |
Vlan |
Vlan |
The following restrictions apply to Frame Relay interworking:
All other translations are dropped.
The following restrictions apply to PPP interworking:
Layer 2 transport over MPLS and IP already exists for like-to-like attachment circuits, such as Ethernet-to-Ethernet or PPP-to-PPP. 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. The figure below is an example of Layer 2 interworking, where ATM and Frame Relay packets travel over the MPLS cloud.
Figure 1 | ATM to Frame Relay Interworking Example |
The L2VPN Interworking feature supports Ethernet, 802.1Q (VLAN), Frame Relay, ATM AAL5, and PPP attachment circuits over MPLS and L2TPv3. The features and restrictions for like-to-like functionality also apply to L2VPN Interworking.
L2VPN Interworking works in either Ethernet ("bridged") mode, IP ("routed"), or Ethernet VLAN mode. You specify the mode by issuing the interworking {ethernet | ip |vlan} command in pseudowire-class configuration mode.
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. In the case of VLAN, the VLAN tag is removed, leaving an untagged Ethernet frame.
Ethernet Interworking is also called bridged interworking. Ethernet frames are bridged across the pseudowire. The CE routers could be natively bridging Ethernet or could be routing using a bridged encapsulation model, such as Bridge Virtual Interface (BVI) or RBE. The PE routers operate in Ethernet like-to-like mode.
This mode is used to offer the following services:
The ip keyword causes IP packets to be extracted from the attachment circuit and sent over the pseudowire. Attachment circuit frames that do not contain IPv4 packets are dropped.
IP Interworking is also called routed interworking. The CE routers encapsulate IP on the link between the CE and PE routers. A new VC type is used to signal the IP pseudowire in MPLS and L2TPv3. Translation between the Layer 2 and IP encapsulations across the pseudowire is required. Special consideration needs to be given to address resolution and routing protocol operation, because these are handled differently on different Layer 2 encapsulations.
This mode is used to provide IP connectivity between sites, regardless of the Layer 2 connectivity to these sites. It is different from a Layer 3 VPN because it is point-to-point in nature and the service provider does not maintain any customer routing information.
Address resolution is encapsulation dependent:
Therefore, address resolution must be terminated on the PE router. End-to-end address resolution is not supported. Routing protocols operate differently over broadcast and point-to-point media. For Ethernet, the CE routers must either use static routing or configure the routing protocols to treat the Ethernet side as a point-to-point network.
The vlan keyword allows the VLAN ID to be included as part of the Ethernet frame. In Cisco IOS Release 12.2(52)SE, you can configure Catalyst 3750 Metro switches to use Ethernet VLAN for Ethernet (bridged) interworking. You can specify the Ethernet VLAN (type 4) by issuing the interworking vlan command in pseudowire-class configuration mode. This allows the VLAN ID to be included as part of the Ethernet frame. In releases previous to Cisco IOS Release 12.2(52)SE, the only way to achieve VLAN encapsulation is to ensure the CE router is connected to the PE router through an Ethernet VLAN interface/subinterface.
The supported L2VPN Interworking features are listed in the table below.
Table 5 | L2VPN Interworking Supported Features |
Feature |
MPLS or L2TPv3 Support |
IP or Ethernet Support |
---|---|---|
Ethernet/VLAN to ATM AAL5 |
MPLS L2TPv3 (12000 series only) |
IP Ethernet |
Ethernet/VLAN to Frame Relay |
MPLS L2TPv3 |
IP Ethernet |
Ethernet/VLAN to PPP |
MPLS |
IP |
Ethernet to VLAN |
MPLS L2TPv3 |
IP Ethernet1 |
L2VPN Interworking: VLAN Enable/Disable Option for AToM |
MPLS |
Ethernet VLAN |
Frame Relay to ATM AAL5 |
MPLS L2TPv3 (12000 series only) |
IP |
Frame Relay to Ethernet or VLAN |
MPLS L2TPv3 |
IP Ethernet |
Frame Relay to PPP |
MPLS L2TPv3 |
IP |
Note : On the Cisco 12000 series Internet router:
|
If the PE router needs to perform address resolution with the local CE router for PPP, you can configure the remote CE router's IP address on the PE router. Issue the ppp ipcp address proxy command with the remote CE router's IP address on the PE router's xconnect PPP interface. The following example shows a sample configuration:
pseudowire-class ip-interworking encapsulation mpls interworking ip interface Serial2/0 encapsulation ppp xconnect 10.0.0.2 200 pw-class ip-interworking ppp ipcp address proxy 10.65.32.14
You can also configure the remote CE router's IP address on the local CE router with the peer default ip address command if the local CE router performs address resolution.
L2VPN Interworking allows you to connect disparate attachment circuits. Configuring the L2VPN Interworking feature requires that you add the interworking command to the list of commands that make up the pseudowire. The steps for configuring the pseudowire for L2VPN Interworking are included in this section. You use the interworkingcommand as part of the overall AToM or L2TPv3 configuration. For specific instructions on configuring AToM or L2TPv3, see the following documents:
To verify the L2VPN Interworking configuration, you can use the following commands.
Step 1 | enable Enables privileged EXEC mode. Enter your password if prompted. |
||||
Step 2 | show l2tun session all (L2TPv3 only) For L2TPv3, you can verify the L2VPN Interworking configuration using the show l2tun session all command on the PE routers. In the following example, the interworking type is shown in bold.
|
||||
Step 3 | show arp You can issue the show arp command between the CE routers to ensure that data is being sent: Example:
Router# show arp
Protocol Address Age (min) Hardware Addr Type Interface
Internet 10.1.1.5 134 0005.0032.0854 ARPA FastEthernet0/0
Internet 10.1.1.7 - 0005.0032.0000 ARPA FastEthernet0/0
|
||||
Step 4 | ping You can issue the ping command between the CE routers to ensure that data is being sent: Example:
Router# ping 10.1.1.5
Type escape sequence to abort.
Sending 5, 100-byte ICMP Echos to 10.1.1.5, timeout is 2 seconds:
!!!!!
Success rate is 100 percent (5/5), round-trip min/avg/max = 1/2/4 ms
|
||||
Step 5 | show l2tun session interworking (L2TPv3 only) For L2TPv3, you can verify that the interworking type is correctly set using the show l2tun session interworking command. Enter the command on the PE routers that are performing the interworking translation.
Command Output for Raw Ethernet Translation Example:
Router# show l2tun session interworking
Session Information Total tunnels 1 sessions 1
LocID TunID Peer-address Type IWrk Username, Intf/Vcid, Circuit
15736 35411 10.9.9.9 ETH - 123, Fa1/1/0 Command Output for Ethernet VLAN Translation Example:
Router# show l2tun session interworking
Session Information Total tunnels 1 sessions 1
LocID TunID Peer-address Type IWrk Username, Intf/Vcid, Circuit
26570 46882 10.8.8.8 VLAN ETH 123, Fa2/0.1:10
|
||||
Step 6 | show mpls l2transport vc detail (AToM only) You can verify the AToM configuration by using the show mpls l2transport vc detail command. In the following example, the interworking type is shown in bold.
|
You can specify the Ethernet VLAN (type 4) by issuing the interworking vlan command in pseudowire-class configuration mode. This allows the VLAN ID to be included as part of the Ethernet frame. In releases previous to Cisco IOS Release 12.2(52)SE and Cisco IOS Release 12.2(33)SRE, the only way to achieve VLAN encapsulation is to ensure the CE router is connected to the PE router through an Ethernet link.
For complete instructions on configuring AToM, see Any Transport over MPLS.
Command or Action | Purpose | |
---|---|---|
|
Example: Router> enable |
Enables privileged EXEC mode. |
|
Example: Router# configure terminal |
Enters global configuration mode. |
|
Example: Router(config)# pseudowire-class class1 |
Establishes a pseudowire class with a name that you specify and enters pseudowire class configuration mode. |
|
Example: Router(config-pw)# encapsulation mpls |
Specifies the tunneling encapsulation, which is either mpls or l2tpv3. |
|
Example: Router(config-pw)# interworking vlan |
Specifies the type of pseudowire and the type of traffic that can flow across it. |
|
Example: Router(config-pw)# end |
Exits pseudowire class configuration mode and enters privileged EXEC mode. |
|
Example: Router# show mpls l2transport vc detail |
Displays information about AToM VCs. |
When the pseudowire on an interface is different from the VC type, the interworking type is displayed in the show mpls l2transport vc detail command output. In the following example, the pseudowire is configured on an Ethernet port and VLAN interworking is configured in the pseudowire class. The relevant output is shown in bold:
PE1# show mpls l2 vc 34 detail Local interface: Et0/1 up, line protocol up, Ethernet up MPLS VC type is Ethernet, interworking type is Eth VLAN Destination address: 10.1.1.2, VC ID: 34, VC status: down Output interface: if-?(0), imposed label stack {} Preferred path: not configured Default path: no route No adjacency Create time: 00:00:13, last status change time: 00:00:13 Signaling protocol: LDP, peer unknown Targeted Hello: 10.1.1.1(LDP Id) -> 10.1.1.2 Status TLV support (local/remote) : enabled/None (no remote binding) LDP route watch : enabled Label/status state machine : local standby, AC-ready, LnuRnd Last local dataplane status rcvd: No fault Last local SSS circuit status rcvd: No fault Last local SSS circuit status sent: Not sent Last local LDP TLV status sent: None Last remote LDP TLV status rcvd: None (no remote binding) Last remote LDP ADJ status rcvd: None (no remote binding) MPLS VC labels: local 2003, 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, seq error 0, send 0
The following example shows the configuration of Ethernet to VLAN over L2TPv3:
PE1 |
PE2 |
---|---|
ip cef ! l2tp-class interworking-class authentication hostname PE1 password 0 lab ! pseudowire-class inter-ether-vlan encapsulation l2tpv3 interworking ethernet protocol l2tpv3 interworking-class ip local interface Loopback0 ! interface Loopback0 ip address 10.8.8.8 255.255.255.255 ! interface FastEthernet1/0 xconnect 10.9.9.9 1 pw-class inter-ether-vlan |
ip cef ! l2tp-class interworking-class authentication hostname PE2 password 0 lab ! pseudowire-class inter-ether-vlan encapsulation l2tpv3 interworking ethernet protocol l2tpv3 interworking-class ip local interface Loopback0 ! interface Loopback0 ip address 10.9.9.9 255.255.255.255 ! interface FastEthernet0/0 no ip address ! interface FastEthernet0/0.3 encapsulation dot1Q 10 xconnect 10.8.8.8 1 pw-class inter-ether-vlan |
The following example shows the configuration of Ethernet to VLAN over AToM:
PE1 |
PE2 |
---|---|
ip cef ! mpls label protocol ldp mpls ldp router-id Loopback0 force ! pseudowire-class atom-eth-iw encapsulation mpls interworking ethernet ! interface Loopback0 ip address 10.8.8.8 255.255.255.255 ! interface FastEthernet1/0.1 encapsulation dot1q 100 xconnect 10.9.9.9 123 pw-class atom-eth-iw |
ip cef ! mpls label protocol ldp mpls ldp router-id Loopback0 force ! pseudowire-class atom encapsulation mpls ! interface Loopback0 ip address 10.9.9.9 255.255.255.255 ! interface FastEthernet0/0 no ip address ! interface FastEthernet1/0 xconnect 10.9.9.9 123 pw-class atom |
The following example shows the configuration of Frame Relay to VLAN over L2TPv3:
PE1 |
PE2 |
---|---|
configure terminal ip cef frame-relay switching ! ! interface loopback 0 ip address 10.8.8.8 255.255.255.255 no shutdown ! pseudowire-class ip encapsulation l2tpv3 interworking ip ip local interface loopback0 ! interface POS1/0 encapsulation frame-relay clock source internal logging event dlci-status-change no shutdown no fair-queue ! connect fr-vlan POS1/0 206 l2transport xconnect 10.9.9.9 6 pw-class ip ! router ospf 10 network 10.0.0.2 0.0.0.0 area 0 network 10.8.8.8 0.0.0.0 area 0 |
configure terminal ip routing ip cef frame-relay switching ! interface loopback 0 ip address 10.9.9.9 255.255.255.255 no shutdown ! pseudowire-class ip encapsulation l2tpv3 interworking ip ip local interface loopback0 ! interface FastEthernet1/0/1 speed 10 no shutdown ! interface FastEthernet1/0/1.6 encapsulation dot1Q 6 xconnect 10.8.8.8 6 pw-class ip no shutdown ! router ospf 10 network 10.0.0.2 0.0.0.0 area 0 network 10.9.9.9 0.0.0.0 area 0 |
The following example shows the configuration of Frame Relay to VLAN over AToM:
PE1 |
PE2 |
---|---|
configure terminal ip cef frame-relay switching ! mpls label protocol ldp mpls ldp router-id loopback0 mpls ip ! pseudowire-class atom encapsulation mpls interworking ip ! interface loopback 0 ip address 10.8.8.8 255.255.255.255 no shutdown ! connect fr-vlan POS1/0 206 l2transport xconnect 10.9.9.9 6 pw-class atom |
configure terminal ip routing ip cef frame-relay switching ! mpls label protocol ldp mpls ldp router-id loopback0 mpls ip ! pseudowire-class atom encapsulation mpls interworking ip ! interface loopback 0 ip address 10.9.9.9 255.255.255.255 no shutdown ! interface FastEthernet1/0/1.6 encapsulation dot1Q 6 xconnect 10.8.8.8 6 pw-class atom no shutdown |
Note |
Frame Relay to ATM AAL5 is available only with AToM in IP mode. |
The following example shows the configuration of Frame Relay to ATM AAL5 over AToM:
PE1 |
PE2 |
---|---|
ip cef frame-relay switching mpls ip mpls label protocol ldp mpls ldp router-id loopback0 force pseudowire-class fratmip encapsulation mpls interworking ip interface Loopback0 ip address 10.33.33.33 255.255.255.255 interface serial 2/0 encapsulation frame-relay ietf frame-relay intf-type dce connect fr-eth serial 2/0 100 l2transport xconnect 10.22.22.22 333 pw-class fratmip interface POS1/0 ip address 10.1.7.3 255.255.255.0 crc 32 clock source internal mpls ip mpls label protocol ldp router ospf 10 passive-interface Loopback0 network 10.33.33.33 0.0.0.0 area 10 network 10.1.7.0 0.0.0.255 area 10 |
ip cef mpls ip mpls label protocol ldp mpls ldp router-id loopback0 force pseudowire-class fratmip encapsulation mpls interworking ip interface Loopback0 ip address 10.22.22.22 255.255.255.255 interface ATM 2/0 pvc 0/203 l2transport encapsulation aa5snap xconnect 10.33.33.33 333 pw-class fratmip interface POS1/0 ip address 10.1.1.2 255.255.255.0 crc 32 clock source internal mpls ip mpls label protocol ldp router ospf 10 passive-interface Loopback0 network 10.22.22.22 0.0.0.0 area 10 network 10.1.1.0 0.0.0.255 area 10 |
The following example shows the configuration of VLAN to ATM AAL5 over AToM:
PE1 |
PE2 |
---|---|
ip cef ! mpls ip mpls label protocol ldp mpls ldp router-id Loopback0 ! pseudowire-class inter-ether encapsulation mpls interworking ethernet ! interface Loopback0 ip address 10.8.8.8 255.255.255.255 ! interface ATM1/0.1 point-to-point pvc 0/100 l2transport encapsulation aal5snap xconnect 10.9.9.9 123 pw-class inter-ether ! interface FastEthernet1/0 xconnect 10.9.9.9 1 pw-class inter-ether ! router ospf 10 log-adjacency-changes network 10.8.8.8 0.0.0.0 area 0 network 10.1.1.1 0.0.0.0 area 0 |
ip cef ! mpls ip mpls label protocol ldp mpls ldp router-id Loopback0 ! pseudowire-class inter-ether encapsulation mpls interworking ethernet ! interface Loopback0 ip address 10.9.9.9 255.255.255.255 ! interface FastEthernet0/0 no ip address ! interface FastEthernet0/0.1 encapsulation dot1Q 10 xconnect 10.8.8.8 123 pw-class inter-ether ! router ospf 10 log-adjacency-changes network 10.9.9.9 0.0.0.0 area 0 network 10.1.1.2 0.0.0.0 area 0 |
The following example shows the configuration of Frame Relay to PPP over L2TPv3:
PE1 |
PE2 |
---|---|
ip cef ip routing ! ! ! pseudowire-class ppp-fr encapsulation l2tpv3 interworking ip ip local interface Loopback0 ! interface Loopback0 ip address 10.1.1.1 255.255.255.255 ! interface FastEthernet1/0/0 ip address 10.16.1.1 255.255.255.0 ! interface Serial3/0/0 no ip address encapsulation ppp ppp authentication chap ! ip route 10.0.0.0 255.0.0.0 10.16.1.2 ! xconnect 10.2.2.2 1 pw-class ppp-fr ppp ipcp address proxy 10.65.32.14 |
ip cef ip routing ! frame-relay switching ! pseudowire-class ppp-fr encapsulation l2tpv3 interworking ip ip local interface Loopback0 ! interface Loopback0 ip address 10.2.2.2 255.255.255.255 ! interface FastEthernet1/0/0 ip address 10.16.2.1 255.255.255.0 ! interface Serial3/0/0 no ip address encapsulation frame-relay frame-relay intf-type dce ! ip route 10.0.0.0 255.0.0.0 10.16.2.2 ! connect ppp-fr Serial3/0/0 100 l2transport xconnect 10.1.1.1 100 pw-class ppp-fr |
The following example shows the configuration of Frame Relay to PPP over AToM:
PE1 |
PE2 |
---|---|
ip cef ip routing mpls label protocol ldp mpls ldp router-id loopback0 force ! ! ! pseudowire-class ppp-fr encapsulation mpls interworking ip ip local interface Loopback0 ! interface Loopback0 ip address 10.1.1.1 255.255.255.255 ! interface FastEthernet1/0/0 ip address 10.16.1.1 255.255.255.0 mpls ip label protocol ldp ! interface Serial3/0/0 no ip address encapsulation ppp ppp authentication chap xconnect 10.2.2.2 1 pw-class ppp-fr ppp ipcp address proxy 10.65.32.14 ! ip route 10.0.0.0 255.0.0.0 10.16.1.2 |
ip cef ip routing mpls label protocol ldp mpls ldp router-id loopback0 force ! frame-relay switching ! pseudowire-class ppp-fr encapsulation mpls interworking ip ip local interface Loopback0 ! interface Loopback0 ip address 10.2.2.2 255.255.255.255 ! interface FastEthernet1/0/0 ip address 10.16.2.1 255.255.255.0 mpls ip mpls label protocol ldp ! interface Serial3/0/0 no ip address encapsulation frame-relay frame-relay intf-type dce ! ip route 10.0.0.0 255.0.0.0 10.16.2.2 ! connect ppp-fr Serial3/0/0 100 l2transport xconnect 10.1.1.1 100 pw-class ppp-fr |
The following example shows the configuration of Ethernet VLAN to PPP over AToM:
PE1 |
PE2 |
---|---|
configure terminal mpls label protocol ldp mpls ldp router-id Loopback0 mpls ip ! pseudowire-class ppp-ether encapsulation mpls interworking ip ! interface Loopback0 ip address 10.8.8.8 255.255.255.255 no shutdown ! interface POS2/0/1 no ip address encapsulation ppp no peer default ip address ppp ipcp address proxy 10.10.10.1 xconnect 10.9.9.9 300 pw-class ppp-ether no shutdown |
configure terminal mpls label protocol ldp mpls ldp router-id Loopback0 mpls ip ! pseudowire-class ppp-ether encapsulation mpls interworking ip ! interface Loopback0 ip address 10.9.9.9 255.255.255.255 no shutdown ! interface vlan300 mtu 4470 no ip address xconnect 10.8.8.8 300 pw-class ppp-ether no shutdown ! interface GigabitEthernet6/2 switchport switchport trunk encapsulation dot1q switchport trunk allowed vlan 300 switchport mode trunk no shutdown |
The following sections provide references related to the L2VPN Interworking feature.
Related Topic |
Document Title |
---|---|
Layer 2 Tunnel Protocol Version 3 |
Layer 2 Tunnel Protocol Version 3 |
Any Transport over MPLS |
Any Transport over MPLS |
Cisco 12000 series routers hardware support |
http://www.cisco.com/univercd/cc/td/doc/product/core/cis12000/linecard/lc_spa/spa_swcs/1232sy/index.htm http://www.cisco.com/en/US/products/sw/iosswrel/ps1829/prod_release_notes_list.html Cross-Platform Release Notes for Cisco IOS Release 12.0S. |
Cisco 7600 series routers hardware support |
Release Notes for Cisco IOS Release 12.2SR for the Cisco 7600 Series Routers |
Cisco 3270 series routers hardware support |
Standards |
Title |
---|---|
draft-ietf-l2tpext-l2tp-base-03.txt |
Layer Two Tunneling Protocol (Version 3) 'L2TPv3' |
draft-martini-l2circuit-trans-mpls-09.txt |
Transport of Layer 2 Frames Over MPLS |
draft-ietf-pwe3-frame-relay-03.txt. |
Encapsulation Methods for Transport of Frame Relay over MPLS Networks |
draft-martini-l2circuit-encap-mpls-04.txt. |
Encapsulation Methods for Transport of Layer 2 Frames Over IP and MPLS Networks |
draft-ietf-pwe3-ethernet-encap-08.txt. |
Encapsulation Methods for Transport of Ethernet over MPLS Networks |
draft-ietf-pwe3-hdlc-ppp-encap-mpls-03.txt. |
Encapsulation Methods for Transport of PPP/HDLC over MPLS Networks |
draft-ietf-ppvpn-l2vpn-00.txt. |
An Architecture for L2VPNs |
MIBs |
MIBs Link |
---|---|
No new or modified MIBs are supported by this feature, and support for existing MIBs has not been modified by this feature. |
To locate and download MIBs for selected platforms, Cisco IOS releases, and feature sets, use Cisco MIB Locator found at the following URL: |
RFCs |
Title |
---|---|
No new or modified RFCs are supported by this feature, and support for existing RFCs has not been modified by this feature. |
-- |
Description |
Link |
---|---|
The Cisco Support website provides extensive online resources, including documentation and tools for troubleshooting and resolving technical issues with Cisco products and technologies. To receive security and technical information about your products, you can subscribe to various services, such as the Product Alert Tool (accessed from Field Notices), the Cisco Technical Services Newsletter, and Really Simple Syndication (RSS) Feeds. Access to most tools on the Cisco Support website requires a Cisco.com user ID and password. |
The following table provides release information about the feature or features described in this module. This table lists only the software release that introduced support for a given feature in a given software release train. Unless noted otherwise, subsequent releases of that software release train also support that feature.
Use Cisco Feature Navigator to find information about platform support and Cisco software image support. To access Cisco Feature Navigator, go to www.cisco.com/go/cfn. An account on Cisco.com is not required.
Table 6 | Feature Information for L2VPN Interworking |
Feature Name |
Releases |
Feature Information |
---|---|---|
L2VPN Interworking |
12.0(26)S 12.0(30)S 12.0(32)S 12.0(32)SY 12.2(33)SRA 12.4(11)T 12.2(33)SXH 12.2(33)SRD 12.2(52)SE 12.2(33)SRE |
This feature allows disparate attachment circuits to be connected. An interworking function facilitates the translation between the different Layer 2 encapsulations. This feature was introduced in Cisco IOS Release 12.0(26)S. In Cisco IOS Release 12.0(30)S, support was added for Cisco 12000 series Internet routers. In Cisco IOS Release 12.0(32)S, support was added on Engine 5 line cards (SIP-401, SIP-501, SIP-600, and SIP-601) in Cisco 12000 series routers for the following four transport types:
On the Cisco 12000 series Internet router, support was added for IP Services Engine (ISE) and Engine 5 line cards that are configured for L2TPv3 tunneling (see Layer 2 Tunnel Protocol Version 3 ). In Cisco IOS Release 12.2(33)SRA, support was added for the Cisco 7600 series routers. In Cisco IOS Release 12.4(11)T, support was added for the following transport types:
This feature was integrated into Cisco IOS Release 12.2(33)SXH. In Cisco IOS Release 12.2(33)SRD, support for routed and bridged interworking on SIP-400 was added for the Cisco 7600 series routers. In Cisco IOS Release 12.2(52)SE, the L2VPN Interworking: VLAN Enable/Disable Option for AToM feature was added for the Cisco 3750 Metro switch. In Cisco IOS Release 12.2(33)SRE, the L2VPN Interworking: VLAN Enable/Disable Option for AToM feature was added for the Cisco 7600 series router. The following commands were introduced or modified: interworking |
Cisco and the Cisco Logo are trademarks of Cisco Systems, Inc. and/or its affiliates in the U.S. and other countries. A listing of Cisco's trademarks can be found at www.cisco.com/go/trademarks. Third party trademarks mentioned are the property of their respective owners. The use of the word partner does not imply a partnership relationship between Cisco and any other company. (1005R)
Any Internet Protocol (IP) addresses and phone numbers used in this document are not intended to be actual addresses and phone numbers. Any examples, command display output, network topology diagrams, and other figures included in the document are shown for illustrative purposes only. Any use of actual IP addresses or phone numbers in illustrative content is unintentional and coincidental.