- Any Transport over MPLS
- L2VPN Interworking
- L2VPN Pseudowire Preferential Forwarding
- L2VPN Multisegment Pseudowires
- QoS Policy Support on L2VPN ATM PVPs
- MPLS Pseudowire Status Signaling
- IEEE 802.1Q Tunneling QinQ for AToM
- Configuring the Managed IPv6 Layer 2 Tunnel Protocol Network Server
- L2VPN Pseudowire Switching
- H VPLS N PE Redundancy for QinQ and MPLS Access
- Configuring Virtual Private LAN Services
- Finding Feature Information
- Prerequisites for IEEE 802.1Q Tunneling (QinQ) for AToM
- Restrictions for IEEE 802.1Q Tunneling (QinQ) for AToM
- Information About IEEE 802.1Q Tunneling (QinQ) for AToM
- How to Configure IEEE 802.1Q Tunneling (QinQ) for AToM
- Configuration Examples for IEEE 801.2 Tunneling (QinQ) for ATM
- Additional References
- Feature Information for IEEE 802.1Q Tunneling (QinQ) for AToM
IEEE 802.1Q Tunneling (QinQ) for AToM
This feature allows you to configure IEEE 802.1Q Tunneling (QinQ) for AToM. It also permits the rewriting of QinQ tags for Multiple Protocol Label Switching (MPLS) Layer 2 VPNs (L2VPNs).
- Finding Feature Information
- Prerequisites for IEEE 802.1Q Tunneling (QinQ) for AToM
- Restrictions for IEEE 802.1Q Tunneling (QinQ) for AToM
- Information About IEEE 802.1Q Tunneling (QinQ) for AToM
- How to Configure IEEE 802.1Q Tunneling (QinQ) for AToM
- Configuration Examples for IEEE 801.2 Tunneling (QinQ) for ATM
- Additional References
- Feature Information for IEEE 802.1Q Tunneling (QinQ) for AToM
Finding Feature Information
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.
Prerequisites for IEEE 802.1Q Tunneling (QinQ) for AToM
The QinQ (short for 802.1Q-in-802.1Q) tunneling and tag rewrite feature is supported on the following line cards:
- 8-port Fast Ethernet line card (ESR-HH-8FE-TX)
- 2-port half-height Gigabit Ethernet line card (ESR-HH-1GE)
- 1-port full-height Gigabit Ethernet line card (ESR-1GE)
Restrictions for IEEE 802.1Q Tunneling (QinQ) for AToM
- Up to a maximum of 447 outer-VLAN IDs and up to 4095 inner VLAN IDs can be supported by this feature.
- Only Unambiguous VLAN tagged Ethernet QinQ interfaces are supported in this release. That is, the Ethernet VLAN QinQ rewrite of both VLAN Tags capability is supported only on Ethernet subinterfaces with a QinQ encapsulation and explicit pair of VLAN IDs defined.
 Note |
Ambiguous inner VLAN IDs are not supported in this release. |
Information About IEEE 802.1Q Tunneling (QinQ) for AToM
- Ethernet VLAN QinQ AToM
- QinQ Tunneling Based on Inner and Outer VLAN Tags
- Rewritten Inner and Outer VLAN Tags on QinQ Frames
Ethernet VLAN QinQ AToM
In Metro Ethernet deployment, in which CE routers and PE routers are connected through an Ethernet switched access network, packets that arrive at PE routers can contain up to two IEEE 802.1q VLAN tags (one inner VLAN tag which identifies the customer; and another outer VLAN tag which denotes the customer's service provider). This technique of allowing multiple VLAN tagging on the same Ethernet packet and creating a stack of VLAN IDs is known as QinQ (short for 802.1Q-in-802.1Q). The figure below shows how different edge devices can do L2 switching on the different levels of the VLAN stack.
| Figure 1 | Ethernet VLAN QinQ |
When the outer VLAN tag is the service-delimiting VLAN tag, QinQ packets are processed similar to the ones with one VLAN tag (case previously named Ethernet VLAN Q-in-Q modified, which is already supported in the 12.2(31) SB release). However, when a customer must use a combination of the outer and inner VLAN tags to delimit service for customers, the edge device should be able to choose a unique pseudowire based on a combination of the inner and outer VLAN IDs on the packet shown in the figure below. The customer may want to be able to rewrite both the inner and the outer VLAN IDs on the traffic egress side.
| Figure 2 | Ethernet VLAN QinQ Header |
QinQ Tunneling Based on Inner and Outer VLAN Tags
When handling incoming QinQ Ethernet traffic, the edge router allows a customer to choose a unique pseudowire endpoint to switch the traffic based on the combination of inner and outer VLAN IDs. For example, the figure below shows how a unique pseudowire is selected depending upon the combination of inner (customer edge) and outer (service provider) VLAN IDs. Thus, traffic for different customers can be kept separate.
| Figure 3 | QinQ Connection |
Rewritten Inner and Outer VLAN Tags on QinQ Frames
When managing incoming AToM Ethernet QinQ traffic, the edge router does the following tasks:
- Strips off the MPLS labels.
- Allows the customer to rewrite both the inner and outer VLAN IDs before sending the packets to the egress QinQ interface. Note this capability is provided only for AToM like-to-like Ethernet QinQ traffic.
The QinQ AToM feature is a like-to-like interworking case over AToM. This feature requires changes to the microcode to allow it to overwrite two layers of VLAN tags on Ethernet QinQ traffic, transported across AToM pseudowires.
- On the ingress side--The packets preserve their L2 header with the two VLAN tags, and it is sent across the pseudowire with VC type of 4.
- On the egress side--The MPLS label is stripped, and up to two levels of VLAN tags are rewritten per the configuration.
Only Unambiguous VLAN tagged Ethernet QinQ interfaces are supported in this release. The Ethernet VLAN Q-in-Q rewrite of both VLAN Tags capability is supported only on Ethernet subinterfaces with a QinQ encapsulation and explicit pair of VLAN IDs defined.
How to Configure IEEE 802.1Q Tunneling (QinQ) for AToM
This section explains how to configure IEEE 802.1Q Tunneling (QinQ) for AToM and includes the following procedures. While all of the procedures are listed as optional, you must choose one of the first two listed.
- Configuring Unambiguous IEEE 802.1Q Tunneling (QinQ) for AToM
- Configuring Ambiguous IEEE 802.1Q Tunneling (QinQ) for AToM
- Verifying the IEEE 802.1Q Tunneling (QinQ) for ATM Configuration
Configuring Unambiguous IEEE 802.1Q Tunneling (QinQ) for AToM
DETAILED STEPS
Configuring Ambiguous IEEE 802.1Q Tunneling (QinQ) for AToM
DETAILED STEPS
Verifying the IEEE 802.1Q Tunneling (QinQ) for ATM Configuration
DETAILED STEPS
Configuration Examples for IEEE 801.2 Tunneling (QinQ) for ATM
- Example Configuring Unambiguous IEEE 802.1Q Tunneling (QinQ) for ATM
- Example Configuring Ambiguous IEEE 802.1Q Tunneling (QinQ) for ATM
- Example Verifying the IEEE 802.1Q Tunneling (QinQ) for ATM Configuration
Example Configuring Unambiguous IEEE 802.1Q Tunneling (QinQ) for ATM
Router> enable Router# configure terminal Router(config)# interface GigabitEthernet1/0/0.100 Router(config-if)# encapsulation dot1q 100 second-dot1q 200 Router(config-if)# xconnect 10.0.0.16 410 encapsulation mpls
Example Configuring Ambiguous IEEE 802.1Q Tunneling (QinQ) for ATM
The following is an example of an ambiguous IEEE 802.1Q Tunneling (QinQ) for ATM configuration.
Router> enable Router# configure terminal Router(config)# interface GigabitEthernet1/0/0.200 Router(config-if)# encapsulation dot1q 200 second-dot1q 1000-2000,3000,3500-4000 Router(config-if)# xconnect 10.0.0.16 420 encapsulation mpls Router(config-if)# exit Router(config)# interface GigabitEthernet1/0/0.201 Router(config-if) encapsulation dot1q 201 second-dot1q any Router(config-if) xconnect 10.0.0.16 430 encapsulation mpls
Example Verifying the IEEE 802.1Q Tunneling (QinQ) for ATM Configuration
The following is sample output of the show mpls l2transport vc command, which is usedto verify the VC set up in EoMPLS QinQ mode.
router# show mpls l2transport vc
Local intf Local circuit Dest address VC ID Status
------------- -------------------------- --------------- ---------- ----------
Gi1/0/0.1 Eth VLAN:100/200 10.1.1.2 1 UP
Additional References
Related Documents
| Related Topic |
Document Title |
|---|---|
| Cisco IOS commands |
|
| Description of commands associated with MPLS and MPLS applications |
Cisco IOS Multiprotocol Label Switching Command Reference |
| AToM and MPLS |
Any Transport over MPLS |
Standards
| Standards |
Title |
|---|---|
| No new or modified standards are supported by this feature, and support for existing standards has not been modified by this feature. |
-- |
MIBs
| 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 software releases, and feature sets, use Cisco MIB Locator found at the following URL: |
RFCs
| RFCs |
Title |
|---|---|
| No new or modified RFCs are supported by this feature, and support for existing RFCs has not been modified by this feature. |
-- |
Technical Assistance
| Description |
Link |
|---|---|
| The Cisco Support and Documentation website provides online resources to download documentation, software, and tools. Use these resources to install and configure the software and to troubleshoot and resolve technical issues with Cisco products and technologies. Access to most tools on the Cisco Support and Documentation website requires a Cisco.com user ID and password. |
Feature Information for IEEE 802.1Q Tunneling (QinQ) for AToM
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 1 | Feature Information for IEEE 802.1Q Tunneling (QinQ) for AToM |
| Feature Name |
Releases |
Feature Information |
|---|---|---|
| IEEE 802.1Q Tunneling (QinQ) for AToM |
Cisco IOS XE Release 2.4 |
This feature allows you to configure IEEE 802.1Q Tunneling (QinQ) for AToM. It also permits the rewriting of QinQ tags for Multiple Protocol Label Switching (MPLS) layer 2 VPNs (L2VPNs). In Cisco IOS XE Release 2.4, this feature was introduced on the Cisco ASR 1000 Series Aggregation Services Routers. The following commands were introduced or modified: interface , encapsulation dot1q second-dot1q , xconnect . |
Cisco and the Cisco logo are trademarks or registered trademarks of Cisco and/or its affiliates in the U.S. and other countries. To view a list of Cisco trademarks, go to this URL: 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. (1110R)
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.
Feedback