Cisco IOS XE Multiprotocol Label Switching Configuration Guide, Release 2 - IEEE 802.1Q Tunneling (QinQ) for AToM [Cisco IOS XE Software]

Table Of Contents

IEEE 802.1Q Tunneling (QinQ) for AToM

Finding Feature Information

Contents

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

Ethernet VLAN QinQ 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

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

Additional References

Related Documents

Standards

MIBs

RFCs

Technical Assistance

Feature Information for IEEE 802.1Q Tunneling (QinQ) for AToM

IEEE 802.1Q Tunneling (QinQ) for AToM

First Published: April 20, 2005

Last Updated: May 4, 2009

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

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 IOS XE 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

•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

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

The IEEE 802.1Q Tunneling (QinQ) for AToM feature has the following restrictions:

•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

To configure the IEEE 802.1Q Tunneling (QinQ) for AToM feature, you should understand the following concepts:

•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). 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

The IEEE 802.1Q Tunneling (QinQ) for AToM can be further explained as follows:

•QinQ Tunneling Based on Inner and Outer VLAN Tags

•Rewritten Inner and Outer VLAN Tags on QinQ Frames

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. Strips off the MPLS labels.

2. 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 (optional)

•Configuring Ambiguous IEEE 802.1Q Tunneling (QinQ) for AToM (optional)

•Verifying the IEEE 802.1Q Tunneling (QinQ) for ATM Configuration (optional)

Configuring Unambiguous IEEE 802.1Q Tunneling (QinQ) for AToM

To configure unambiguous IEEE 802.1Q tunneling (QinQ) for AToM, complete the following steps:

SUMMARY STEPS

1. enable

2. configure terminal

3. interface gigabitethernet slot/subslot/port.[subinterface]

4. encapsulation dot1q vlan-id second-dot1q {any | vlan-id[,vlan-id[-vlan-id]]}

5. xconnect peer-router-id vcid encapsulation mpls

DETAILED STEPS

Command or Action

Purpose

Step 1

enable
Example:

Router> enable

Enables privileged EXEC mode.

•Enter your password if prompted.

Step 2

configure terminal
Example:

Router# configure terminal

Enters global configuration mode.

Step 3

interface gigabitethernet slot/subslot/port.[subinterface]
Example:

Router(config)# interface GigabitEthernet1/0/0.100

Specifies the Gigabit Ethernet interface and enters interface configuration mode.

Step 4

encapsulation dot1q vlan-id second-dot1q {any | vlan-id[,vlan-id[-vlan-id]]}
Example:

Router(config-if)# encapsulation dot1q 100 second-dot1q 200

Defines the matching criteria to map Q-in-Q ingress frames on an interface to the appropriate service instance.

Step 5

xconnect peer-router-id vcid encapsulation mpls
Example:

Router(config-if)# xconnect 10.0.0.16 410 encapsulation mpls

Creates the VC to transport the Layer 2 packets.

Configuring Ambiguous IEEE 802.1Q Tunneling (QinQ) for AToM

To configure ambiguous IEEE 802.1Q tunneling (QinQ) for AToM, complete the following steps:

SUMMARY STEPS

1. enable

2. configure terminal

3. interface gigabitethernet slot/subslot/port.[subinterface]

4. encapsulation dot1q vlan-id second-dot1q {any | vlan-id[,vlan-id[-vlan-id]]}

5. xconnect peer-router-id vcid encapsulation mpls

6. exit

7. interface gigabitethernet slot/subslot/port.[subinterface]

8. encapsulation dot1q vlan-id second-dot1q {any | vlan-id[,vlan-id[-vlan-id]]}

9. xconnect peer-router-id vcid encapsulation mpls

DETAILED STEPS
Command or Action

Purpose

Step 1

enable
Example:

Router> enable

Enables privileged EXEC mode.

•Enter your password if prompted.

Step 2

configure terminal
Example:

Router# configure terminal

Enters global configuration mode.
Step 3
interface gigabitethernet slot/subslot/port.[subinterface]
Example:
Router(config)# interface 
GigabitEthernet1/0/0.200
Specifies the Gigabit Ethernet subinterface and enters interface configuration mode.
Step 4

encapsulation dot1q vlan-id second-dot1q {any | vlan-id[,vlan-id[-vlan-id]]}
Example:

Router(config-if)# encapsulation dot1q 200 second-dot1q 1000-2000,3000,3500-4000

Defines the matching criteria to map Q-in-Q ingress frames on an interface to the appropriate service instance.

Step 5

xconnect peer-router-id vcid encapsulation mpls
Example:

Router(config-if)# xconnect 10.0.0.16 420 encapsulation mpls

Creates the VC to transport the Layer 2 packets.

Step 6

exit
Example:

Router(config-if)# exit

Exits interface configuration mode.

Step 7

interface gigabitethernet slot/subslot/port.[subinterface]
Example:

Router(config)# interface GigabitEthernet1/0/0.201

Specifies the next Gigabit Ethernet interface and enters interface configuration mode.

Step 8

encapsulation dot1q vlan-id second-dot1q {any | vlan-id[,vlan-id[-vlan-id]]}
Example:

Router(config-if)# encapsulation dot1q 201 second-dot1q any

Defines the matching criteria to map Q-in-Q ingress frames on an interface to the appropriate service instance.

Step 9

xconnect peer-router-id vcid encapsulation mpls
Example:

Router(config-if)# xconnect 10.0.0.16 430 encapsulation mpls

Creates the VC to transport the Layer 2 packets.
Verifying the IEEE 802.1Q Tunneling (QinQ) for ATM Configuration

To verify the IEEE 802.1Q tunneling (QinQ) for AToM, complete the following steps.

SUMMARY STEPS

1. enable

2. show mpls l2transport vc

DETAILED STEPS

Command or Action

Purpose

Step 1

enable
Example:

Router> enable

Enables privileged EXEC mode.

•Enter your password if prompted.

Step 2

show mpls l2transport vc
Example:

Router# show mpls l2transport vc

Displays information about Any Transport over MPLS (AToM) virtual circuits (VCs) and static pseudowires that have been enabled to route Layer 2 packets on a router.

Configuration Examples for IEEE 801.2 Tunneling (QinQ) for ATM

This section contains the following configuration examples:

•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: Example

The following is an example of an unambiguous IEEE 802.1Q Tunneling (QinQ) for ATM configuration.
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 
Configuring Ambiguous IEEE 802.1Q Tunneling (QinQ) for ATM: Example

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
Verifying the IEEE 802.1Q Tunneling (QinQ) for ATM: Configuration: Example

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 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

The following sections provide references related to the IEEE 802.1Q Tunneling (QinQ) for ATM feature.

Related Documents

Related Topic

Document Title

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 IOS XE software releases, and feature sets, use Cisco MIB Locator found at the following URL:

http://www.cisco.com/go/mibs

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 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.

http://www.cisco.com/techsupport

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 lists only the Cisco IOS XE software release that introduced support for a given feature in a given Cisco IOS XE software release train. Unless noted otherwise, subsequent releases of that Cisco IOS XE software release train also support that feature.

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 section provides information about this feature:

•Information About IEEE 802.1Q Tunneling (QinQ) for AToM

•How to Configure IEEE 802.1Q Tunneling (QinQ) for AToM

The following commands were introduced or modified: interface, encapsulation dot1q second-dot1q, xconnect.

CCDE, CCSI, CCENT, Cisco Eos, Cisco HealthPresence, the Cisco logo, Cisco Lumin, Cisco Nexus, Cisco Nurse Connect, Cisco Stackpower, Cisco StadiumVision, Cisco TelePresence, Cisco WebEx, DCE, and Welcome to the Human Network are trademarks; Changing the Way We Work, Live, Play, and Learn and Cisco Store are service marks; and Access Registrar, Aironet, AsyncOS, Bringing the Meeting To You, Catalyst, CCDA, CCDP, CCIE, CCIP, CCNA, CCNP, CCSP, CCVP, Cisco, the Cisco Certified Internetwork Expert logo, Cisco IOS, Cisco Press, Cisco Systems, Cisco Systems Capital, the Cisco Systems logo, Cisco Unity, Collaboration Without Limitation, EtherFast, EtherSwitch, Event Center, Fast Step, Follow Me Browsing, FormShare, GigaDrive, HomeLink, Internet Quotient, IOS, iPhone, iQuick Study, IronPort, the IronPort logo, LightStream, Linksys, MediaTone, MeetingPlace, MeetingPlace Chime Sound, MGX, Networkers, Networking Academy, Network Registrar, PCNow, PIX, PowerPanels, ProConnect, ScriptShare, SenderBase, SMARTnet, Spectrum Expert, StackWise, The Fastest Way to Increase Your Internet Quotient, TransPath, WebEx, and the WebEx logo are registered trademarks of Cisco Systems, Inc. and/or its affiliates in the United States and certain other countries.

All other trademarks mentioned in this document or website 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. (0903R)

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-2009 Cisco Systems, Inc. All rights reserved.