Table Of Contents
IEEE 802.1Q-in-Q VLAN Tag Termination
Information About IEEE 802.1Q-in-Q VLAN Tag Termination
IEEE 802.1Q-in-Q VLAN Tag Termination on Subinterfaces
Unambiguous and Ambiguous Subinterfaces
How to Configure IEEE 802.1Q-in-Q VLAN Tag Termination
Configuring the Interfaces for IEEE 802.1Q-in-Q VLAN Tag Termination
Verifying the IEEE 802.1Q-in-Q VLAN Tag Termination
Configuration Examples for IEEE 802.1Q-in-Q VLAN Tag Termination
Configuring any Keyword on Subinterfaces for IEEE 802.1Q-in-Q VLAN Tag Termination: Example
Feature Information for IEEE 802.1Q-in-Q VLAN Tag Termination
IEEE 802.1Q-in-Q VLAN Tag Termination
First Published: 2004Last Updated: July 31, 2009Encapsulating IEEE 802.1Q VLAN tags within 802.1Q enables service providers to use a single VLAN to support customers who have multiple VLANs. The IEEE 802.1Q-in-Q VLAN Tag Termination feature on the subinterface level preserves VLAN IDs and keeps traffic in different customer VLANs segregated.
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-in-Q VLAN Tag Termination" 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
•
Information About IEEE 802.1Q-in-Q VLAN Tag Termination
•
How to Configure IEEE 802.1Q-in-Q VLAN Tag Termination
•
Configuration Examples for IEEE 802.1Q-in-Q VLAN Tag Termination
•
Feature Information for IEEE 802.1Q-in-Q VLAN Tag Termination
Information About IEEE 802.1Q-in-Q VLAN Tag Termination
This section lists the concepts that the user should understand in order to perform the tasks in the "How to Configure IEEE 802.1Q-in-Q VLAN Tag Termination" section. The following concepts are described in this section:
•
IEEE 802.1Q-in-Q VLAN Tag Termination on Subinterfaces
•
Unambiguous and Ambiguous Subinterfaces
IEEE 802.1Q-in-Q VLAN Tag Termination on Subinterfaces
IEEE 802.1Q-in-Q VLAN Tag Termination simply adds another layer of IEEE 802.1Q tag (called "metro tag" or "PE-VLAN") to the 802.1Q tagged packets that enter the network. The purpose is to expand the VLAN space by tagging the tagged packets, thus producing a "double-tagged" frame. The expanded VLAN space allows the service provider to provide certain services, such as Internet access on specific VLANs for specific customers, and yet still allows the service provider to provide other types of services for their other customers on other VLANs.
Generally the service provider's customers require a range of VLANs to handle multiple applications. Service providers can allow their customers to use this feature to safely assign their own VLAN IDs on subinterfaces because these subinterface VLAN IDs are encapsulated within a service-provider designated VLAN ID for that customer. Therefore there is no overlap of VLAN IDs among customers, nor does traffic from different customers become mixed. The double-tagged frame is "terminated" or assigned on a subinterface with an expanded encapsulation dot1q command that specifies the two VLAN ID tags (outer VLAN ID and inner VLAN ID) terminated on the subinterface (see Figure 1).
IEEE 802.1Q-in-Q VLAN Tag Termination is generally supported on whichever Cisco IOS XE features or protocols are supported on the subinterface. The only restriction is whether you assign ambiguous or unambiguous subinterfaces for the inner VLAN ID. See the "Unambiguous and Ambiguous Subinterfaces" section.
The primary benefit for the service provider is reduced number of VLANs supported for the same number of customers. Other benefits of this feature include:
•
PPPoE scalability. By expanding the available VLAN space from 4096 to approximately 16.8 million (4096 times 4096), the number of PPPoE sessions that can be terminated on a given interface is multiplied.
•
When deploying Gigabyte Ethernet DSL Access Multiplexer (DSLAM) in wholesale model, you can assign the inner VLAN ID to represent the end-customer virtual circuit (VC) and assign the outer VLAN ID to represent the service provider ID.
Whereas switches require IEEE 802.1Q tunnels on interfaces to carry double-tagged traffic, routers need only encapsulate Q-in-Q VLAN tags within another level of 802.1Q tags in order for the packets to arrive at the correct destination.
Figure 1 Untagged, 802.1Q-Tagged, and Double-Tagged Ethernet Frames
Unambiguous and Ambiguous Subinterfaces
The encapsulation dot1q command is used to configure Q-in-Q termination on a subinterface. The command accepts an Outer VLAN ID and one or more Inner VLAN IDs. The outer VLAN ID always has a specific value, while inner VLAN ID can either be a specific value or a range of values.
A subinterface that is configured with a single Inner VLAN ID is called an unambiguous Q-in-Q subinterface. In the following example, Q-in-Q traffic with an Outer VLAN ID of 101 and an Inner VLAN ID of 1001 is mapped to the Gigabit Ethernet 1/1/0.100 subinterface:
Router(config)# interface gigabitEehernet1/1/0.100Router(config-subif)# encapsulation dot1q 101 second-dot1q 1001A subinterface that is configured with multiple Inner VLAN IDs is called an ambiguous Q-in-Q subinterface. By allowing multiple Inner VLAN IDs to be grouped together, ambiguous Q-in-Q subinterfaces allow for a smaller configuration, improved memory usage and better scalability.
In the following example, Q-in-Q traffic with an Outer VLAN ID of 101 and Inner VLAN IDs anywhere in the 2001-2100 and 3001-3100 range is mapped to the Gigabit Ethernet 1/1/0.101 subinterface:
Router(config)# interface gigabitethernet1/1/0.101Router(config-subif)# encapsulation dot1q 101 second-dot1q 2001-2100,3001-3100Ambiguous subinterfaces can also use the any keyword to specify the inner VLAN ID.
See the "Configuration Examples for IEEE 802.1Q-in-Q VLAN Tag Termination" section for an example of how VLAN IDs are assigned to subinterfaces, and for a detailed example of how the any keyword is used on ambiguous subinterfaces.
Only PPPoE is supported on ambiguous subinterfaces. Standard IP routing is not supported on ambiguous subinterfaces.
How to Configure IEEE 802.1Q-in-Q VLAN Tag Termination
•
Configuring the Interfaces for IEEE 802.1Q-in-Q VLAN Tag Termination (required)
•
Verifying the IEEE 802.1Q-in-Q VLAN Tag Termination (optional)
Configuring the Interfaces for IEEE 802.1Q-in-Q VLAN Tag Termination
Perform this task to configure the main interface used for the Q-in-Q double tagging and to configure the subinterfaces. An optional step in this task shows you how to configure the EtherType field to be 0x9100 for the outer VLAN tag, if that is required. After the subinterface is defined, the 802.1Q encapsulation is configured to use the double tagging.
SUMMARY STEPS
1.
enable
2.
configure terminal
3.
interface type number
4.
dot1q tunneling ethertype ethertype
5.
interface type number.subinterface-number
6.
encapsulation dot1q vlan-id second-dot1q {any | vlan-id | vlan-id-vlan-id[,vlan-id-vlan-id]}
7.
pppoe enable [group group-name] [max-sessions max-sessions-number]
8.
exit
9.
Repeat Step 5 to configure another subinterface.
10.
Repeat Step 6 and Step 7 to specify the VLAN tags to be terminated on the subinterface and to enable PPPoE sessions on the subinterface.
11.
end
DETAILED STEPS
Verifying the IEEE 802.1Q-in-Q VLAN Tag Termination
Perform this optional task to verify the configuration of the IEEE 802.1Q-in-Q VLAN Tag Termination feature.
SUMMARY STEPS
1.
enable
2.
show running-config
3.
show vlans dot1q [internal | interface-type interface-number.subinterface-number [detail] | second-dot1q [inner-id | any]] [detail]]
DETAILED STEPS
Step 1
enable
Enables privileged EXEC mode. Enter your password if prompted.
Router> enableStep 2
show running-config
Use this command to show the currently running configuration on the device. You can use delimiting characters to display only the relevant parts of the configuration.
Router# show running-configStep 3
show vlans dot1q [internal | interface-type interface-number.subinterface-number [detail] | [second-dot1q [inner-id | any]] [detail]]
Use this command to show the statistics for all the 802.1Q VLAN IDs. In this example, only the outer VLAN ID is displayed.
Router# show vlans dot1qTotal statistics for 802.1Q VLAN 1:441 packets, 85825 bytes input1028 packets, 69082 bytes outputTotal statistics for 802.1Q VLAN 101:5173 packets, 510384 bytes input3042 packets, 369567 bytes outputTotal statistics for 802.1Q VLAN 201:1012 packets, 119254 bytes input1018 packets, 120393 bytes outputTotal statistics for 802.1Q VLAN 301:3163 packets, 265272 bytes input1011 packets, 120750 bytes outputTotal statistics for 802.1Q VLAN 401:1012 packets, 119254 bytes input1010 packets, 119108 bytes output
Configuration Examples for IEEE 802.1Q-in-Q VLAN Tag Termination
•
Configuring any Keyword on Subinterfaces for IEEE 802.1Q-in-Q VLAN Tag Termination: Example
Configuring any Keyword on Subinterfaces for IEEE 802.1Q-in-Q VLAN Tag Termination: Example
Some ambiguous subinterfaces can use the any keyword for the inner VLAN ID specification. The any keyword represents any inner VLAN ID that is not explicitly configured on any other interface. In the following example, seven subinterfaces are configured with various outer and inner VLAN IDs.
Note
The any keyword can be configured on only one subinterface of a specified physical interface and outer VLAN ID.
interface GigabitEthernet1/0/0.1encapsulation dot1q 100 second-dot1q 100interface GigabitEthernet1/0/0.2encapsulation dot1q 100 second-dot1q 200interface GigabitEthernet1/0/0.3encapsulation dot1q 100 second-dot1q 300-400,500-600interface GigabitEthernet1/0/0.4encapsulation dot1q 100 second-dot1q anyinterface GigabitEthernet1/0/0.5encapsulation dot1q 200 second-dot1q 50interface GigabitEthernet1/0/0.6encapsulation dot1q 200 second-dot1q 1000-2000,3000-4000interface GigabitEthernet1/0/0.7encapsulation dot1q 200 second-dot1q anyTable 1 shows which subinterfaces are mapped to different values of the outer and inner VLAN ID on Q-in-Q frames that come in on Gigabit Ethernet interface 1/0/0.
A new subinterface is now configured:
interface GigabitEthernet1/0/0.8encapsulation dot1q 200 second-dot1q 200-600,900-999Table 2 shows the changes made to the table for the outer VLAN ID of 200. Notice that subinterface 1/0/0.7 configured with the any keyword now has new inner VLAN ID mappings.
Additional References
The following sections provide references related to the IEEE 802.1Q-in-Q VLAN Tag Termination feature.
Related Documents
Standards
MIBs
RFCs
RFCs TitleNo new or modified RFCs are supported by this feature, and support for existing standards has not been modified by this feature.
—
Technical Assistance
Feature Information for IEEE 802.1Q-in-Q VLAN Tag Termination
Table 3 lists the release history for this feature.
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 3 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.
CCDE, CCENT, CCSI, Cisco Eos, Cisco HealthPresence, Cisco IronPort, the Cisco logo, Cisco Lumin, Cisco Nexus, Cisco Nurse Connect, Cisco Pulse, Cisco StackPower, Cisco StadiumVision, Cisco TelePresence, Cisco Unified Computing System, Cisco WebEx, DCE, Flip Channels, Flip for Good, Flip Mino, Flipshare (Design), Flip Ultra, Flip Video, Flip Video (Design), Instant Broadband, and Welcome to the Human Network are trademarks; Changing the Way We Work, Live, Play, and Learn, Cisco Capital, Cisco Capital (Design), Cisco:Financed (Stylized), Cisco Store, and Flip Gift Card are service marks; and Access Registrar, Aironet, AllTouch, 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, Continuum, EtherFast, EtherSwitch, Event Center, Explorer, Fast Step, Follow Me Browsing, FormShare, GainMaker, GigaDrive, HomeLink, iLYNX, Internet Quotient, IOS, iPhone, iQuick Study, IronPort, the IronPort logo, Laser Link, LightStream, Linksys, MediaTone, MeetingPlace, MeetingPlace Chime Sound, MGX, Networkers, Networking Academy, Network Registrar, PCNow, PIX, PowerKEY, PowerPanels, PowerTV, PowerTV (Design), PowerVu, Prisma, ProConnect, ROSA, 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. (0908R)
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, and 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.
© 2004-2009 Cisco Systems, Inc. All rights reserved.

