Restrictions for L2VPN Local Switching—Frame Relay-Ethernet/VLAN
The following functions are not supported:
- Frame Relay-to-Ethernet IP-Mode local switching
- Frame Relay-to-Ethernet VLAN-Mode local switching
- Frame Relay Multilink Frame Relay (MFR)
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.
L2VPN Local Switching—Frame Relay-Ethernet/VLAN feature allows you to switch Frame Relay and Ethernet frames between two interfaces on the same device.
The following functions are not supported:
The L2VPN Local Switching—Frame Relay-Ethernet/VLAN feature switches a Frame Relay frame to an Ethernet VLAN/QinQ frame over the same provider edge (PE) device. Only Ethernet (bridged) interworking mode is supported to switch packets between Frame Relay link and Ethernet VLAN/QinQ. In a bridged interworking mode, the MAC header is considered as the payload of Frame Relay frames.
The L2VPN Local Switching—Frame Relay-Ethernet/VLAN supports the following functions:
The Frame Relay-Ethernet bridge mode local switching in data-link connection identifier (DLCI) mode.
Port interface and subinterface Ethernet attachment circuit (AC) type with single tag or double tags (Q-in-Q).
Cisco and IETF Frame Relay encapsulation.
The Frame Relay-Ethernet local switching topology is illustrated in the figure below.
Frame Relay-Ethernet port-bridged interworking provides interoperability between a Frame Relay attachment virtual circuit (VC) and an Ethernet attachment VC connected to the same provider edge (PE) device. The bridged encapsulation is used that corresponds to the bridged (Ethernet) interworking mechanism.
Based on RFC 2427, Multiprotocol Interconnect over Frame Relay, the interworking is done at the PE connected to the Frame Relay attachment VC as shown in the figure below.
The processing of Frame Relay-Ethernet port local switching is described as follows:
Frame Relay to Ethernet VLAN/QinQ bridged interworking provides interoperability between a Frame Relay attachment virtual circuit (VC) and an Ethernet VLAN attachment VC connected to the same provider edge (PE) device. The bridged encapsulation is used that corresponds to the bridged (Ethernet) interworking mechanism.
Based on RFC 2427, Multiprotocol Interconnect over Frame Relay, the interworking function is implemented on the PE connected to the Frame Relay attachment VC as shown in the figure below.
The process of Frame Relay to VLAN/QinQ bridged interworking is described as follows:
Command or Action | Purpose | |
---|---|---|
Step 1 |
enable Example:
|
Enables privileged EXEC mode.
|
Step 2 |
configure terminal Example:
|
Enters global configuration mode. |
Step 3 |
interface type number Example:
|
Specifies the interface type and number and enters interface configuration mode. |
Step 4 |
no ip address Example:
|
Disables IP processing. |
Step 5 |
exit Example:
|
Exits interface configuration mode and returns to global configuration mode. |
Step 6 |
interface type number Example:
|
Specifies the subinterface type and number and enters subinterface configuration mode. |
Step 7 |
encapsulation frame-relay Example:
|
Enables Frame Relay encapsulation. |
Step 8 |
frame-relay interface-dlci dlci switched Example:
|
Indicates that a Frame Relay data-link connection identifier (DLCI) is switched. The range is from 16 to 1007. |
Step 9 |
exit Example:
|
Exits subinterface configuration mode and returns to global configuration mode. |
Step 10 |
connect connection-name type number dlci interworking ethernet Example:
|
Creates Layer 2 data connections between two ports on the same device. |
Step 11 |
end Example:
|
Exits global configuration mode and returns to privileged EXEC mode. |
Command or Action | Purpose | |
---|---|---|
Step 1 |
enable Example:
|
Enables privileged EXEC mode.
|
Step 2 |
configure terminal Example:
|
Enters global configuration mode. |
Step 3 |
interface type number Example:
|
Specifies a subinterface type and number and enters subinterface configuration mode. |
Step 4 |
encapsulation dot1q vlan-id second-dot1q second vlan-id Example:
|
Specifies QinQ as the encapsulation method. |
Step 5 |
exit Example:
|
Exits subinterface configuration mode and returns to global configuration mode. |
Step 6 |
interface type number Example:
|
Specifies a subinterface type and number and enters subinterface configuration mode. |
Step 7 |
encapsulation frame-relay Example:
|
Enables Frame Relay encapsulation. |
Step 8 |
frame-relay interface-dlci dlci switched Example:
|
Indicates that a Frame Relay data-link connection identifier (DLCI) is switched. |
Step 9 |
exit Example:
|
Exits subinterface configuration mode and returns to global configuration mode. |
Step 10 |
connect connection-name type number dlci interworking ethernet Example:
|
Creates Layer 2 data connections between two ports on the same device. |
Step 11 |
end Example:
|
Exits global configuration mode and returns to privileged EXEC mode. |
The following example shows how to configure the Frame Relay-Ethernet port mode bridged interworking:
PE configuration:
interface GigabitEthernet0/0/1
no ip address
end
interface Serial0/1/2:0
no ip address
encapsulation frame-relay
no keepalive
frame-relay interface-dlci 60 switched
end
connect FR-ETHQinQ Serial0/1/2:0 60 GigabitEthernet0/0/1 interworking ethernet
CE configuration: Frame-Relay-CE
bridge irb
bridge 16 protocol ieee
bridge 16 route ip
interface Serial2/0:0
no ip address
encapsulation frame-relay IETF
no keepalive
interface Serial2/0:0.1 point-to-point
frame-relay interface-dlci 60
bridge-group 60
interface BVI16
ip address 172.16.1.0 255.255.0.0
Ethernet-CE interface GigabitEthernet0/0/1
ip address 172.16.2.1 255.255.0.0
The following example shows how to configure Frame Relay-Ethernet VLAN 802.1Q bridged interworking:
PE configuration:
interface GigabitEthernet0/0/1.10
encapsulation dot1Q 10
end
interface Serial0/1/2:0
no ip address
encapsulation frame-relay
no keepalive
frame-relay interface-dlci 58 switched
end
connect FR-ETH1Q Serial0/1/2:0 58 GigabitEthernet0/0/1.10 interworking Ethernet
CE configuration: Frame Relay-CE
bridge irb
bridge 16 protocol ieee
bridge 16 route ip
interface Serial2/0:0
no ip address
encapsulation frame-relay IETF
no keepalive
interface Serial2/0:0.1 point-to-point
frame-relay interface-dlci 58
bridge-group 16
interface BVI16
ip address 172.18.1.2 255.255.0.0
Ethernet-CE
interface GigabitEthernet0/0/1.10
encapsulation dot1Q 10
ip address 172.17.2.1 255.255.0.0
The following example shows how to configure Frame Relay-VLAN QinQ bridged interworking:
PE configuration:
interface GigabitEthernet0/0/1.11
encapsulation dot1Q 11 second-dot1q 100
end
interface Serial0/1/2:0
no ip address
encapsulation frame-relay
no keepalive
frame-relay interface-dlci 100 switched
end
connect FR-ETHQinQ Serial0/1/2:0 100 GigabitEthernet0/0/1.11 interworking ethernet
CE configuration: Frame-Relay-CE
bridge irb
bridge 16 protocol ieee
bridge 16 route ip
interface Serial2/0:0
no ip address
encapsulation frame-relay IETF
no keepalive
interface Serial2/0:0.1 point-to-point
frame-relay interface-dlci 100
bridge-group 16
interface BVI16
ip address 172.18.1.3 255.255.0.0
Ethernet-CE
interface GigabitEthernet0/0/1.10
encapsulation dot1Q 10 sec 10
ip address 172.19.1.1 255.255.0.0
Related Topic |
Document Title |
---|---|
Cisco IOS commands |
|
WAN commands |
RFC |
Title |
---|---|
RFC 2427 |
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.
Feature Name |
Releases |
Feature Information |
---|---|---|
L2VPN Local Switching—Frame Relay-Ethernet/VLAN |
The L2VPN Local Switching—Frame Relay-Ethernet/VLAN feature allows you to switch Frame Relay and Ethernet frames between two interfaces on the same device. |