Downloads |
 Feedback
|
Table Of Contents
IEEE 802.1Q Tunneling (QinQ) for AToM
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
QinQ Tunneling Based on Inner and Outer VLAN Tags
Rewritten Inner and Outer VLAN Tags on QinQ Frames
How to Configure IEEE 802.1Q Tunneling (QinQ) for AToM
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
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
Feature Information for IEEE 802.1Q Tunneling (QinQ) for AToM
IEEE 802.1Q Tunneling (QinQ) for AToM
First Published: April 20, 2005Last Updated: May 4, 2009This 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
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 for IEEE 802.1Q Tunneling (QinQ) for AToM" section.
Use Cisco Feature Navigator to find information about platform support and Cisco software image support. To access Cisco Feature Navigator, go to http://www.cisco.com/go/cfn. An account on Cisco.com is not required.
Contents
•
Prerequisites for IEEE 802.1Q Tunneling (QinQ) for AToM
•
•
•
•
•
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:
•
•
•
Restrictions for IEEE 802.1Q Tunneling (QinQ) for AToM
The IEEE 802.1Q Tunneling (QinQ) for AToM feature has the following restrictions:
•
•
Note
Information About IEEE 802.1Q Tunneling (QinQ) for AToM
•
•
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). Figure 1 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 Figure 2. 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, Figure 3 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:
1.
2.
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.
•
•
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
SUMMARY STEPS
1.
2.
3.
4.
5.
DETAILED STEPS
Configuring Ambiguous IEEE 802.1Q Tunneling (QinQ) for AToM
SUMMARY STEPS
1.
2.
3.
4.
5.
6.
7.
8.
9.
DETAILED STEPS
Verifying the IEEE 802.1Q Tunneling (QinQ) for ATM Configuration
SUMMARY STEPS
1.
2.
DETAILED STEPS
Configuration Examples for IEEE 801.2 Tunneling (QinQ) for ATM
•
•
•
Example: Configuring Unambiguous IEEE 802.1Q Tunneling (QinQ) for ATM
Router> enableRouter# configure terminalRouter(config)# interface GigabitEthernet1/0/0.100Router(config-if)# encapsulation dot1q 100 second-dot1q 200Router(config-if)# xconnect 10.0.0.16 410 encapsulation mplsExample: 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> enableRouter# configure terminalRouter(config)# interface GigabitEthernet1/0/0.200Router(config-if)# encapsulation dot1q 200 second-dot1q 1000-2000,3000,3500-4000Router(config-if)# xconnect 10.0.0.16 420 encapsulation mplsRouter(config-if)# exitRouter(config)# interface GigabitEthernet1/0/0.201Router(config-if) encapsulation dot1q 201 second-dot1q anyRouter(config-if) xconnect 10.0.0.16 430 encapsulation mplsExample: Verifying the IEEE 802.1Q Tunneling (QinQ) for ATM: Configuration
The following is sample output of the show mpls l2transport vc command, which is used to verify the VC set up in EoMPLS QinQ mode.
router# show mpls l2transport vcLocal intf Local circuit Dest address VC ID Status------------- -------------------------- --------------- ---------- ----------Gi1/0/0.1 Eth VLAN:100/200 10.1.1.2 1 UPAdditional References
Related Documents
Cisco IOS commands
Description of commands associated with MPLS and MPLS applications
AToM and MPLS
Standards
No new or modified standards are supported by this feature, and support for existing standards has not been modified by this feature.
—
MIBs
RFCs
No new or modified RFCs are supported by this feature, and support for existing RFCs has not been modified by this feature.
—
Technical Assistance
Feature Information for IEEE 802.1Q Tunneling (QinQ) for AToM
Table 1 lists the features in this module and provides links to specific configuration information.
Use Cisco Feature Navigator to find information about platform support and software image support. Cisco Feature Navigator enables you to determine which Cisco IOS XE software images support a specific software release, feature set, or platform. To access Cisco Feature Navigator, go to http://www.cisco.com/go/cfn. An account on Cisco.com is not required.
Note
Table 1 Feature Information for IEEE 802.1Q Tunneling (QinQ) for AToM
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 section provides information about this feature:
•
•
The following commands were introduced or modified: interface, encapsulation dot1q second-dot1q, xconnect.
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 used in this document are not intended to be actual addresses. Any examples, command display output, and figures included in the document are shown for illustrative purposes only. Any use of actual IP addresses in illustrative content is unintentional and coincidental.
© 2005-2011 Cisco Systems, Inc. All rights reserved.
