-
OSM Configuration Note, 12.2SX
-
Preface
-
Product Overview
-
Basic Configurations
-
Configuring the OC-3c/STM-1, OC-12c/STM-4, and OC-48c/STM-16 SONET/SDH Optical Services Modules
-
Configuring 4-Port Gigabit Ethernet WAN Optical Services Modules
-
Configuring the Channelized OC-12/T3 SONET/SDH Optical Services Modules
-
Configuring the Channelized OC-12/T1 Optical Services Modules
-
Configuring the Channelized 12-port CT3/T1 Optical Services Modules
-
Configuring QoS on the Optical Services Module
-
Configuring Destination Sensitive Services on the Optical Services Modules
-
Configuring the OC-12 ATM Optical Services Modules
-
Configuring Multiprotocol Label Switching on the Optical Services Modules
-
Table Of Contents
Configuring 4-Port Gigabit Ethernet WAN Optical Services Modules
Saving your Configuration Before Upgrading from an OSM-4GE-WAN-GBIC to an OSM-2+4GE-WAN+
Gigabit Ethernet WAN Port Configuration
Configuring Strict Priority Low Latency Queuing (LLQ) Support on the OSM-2+4GE-WAN+
QinQ Translation—Double Tag to Single Tag Translation
QinQ Transparent Tunneling—Double Tag to Double Tag Translation
Out-of-Range and Unspecified In-Range Packets
Per VLAN Load Balancing for Advanced QinQ Service Mapping
Configuring Advanced QinQ Service Mapping
Enabling IEEE 802.1Q-in-802.1Q Translation on a Gigabit Ethernet WAN Interface
Enabling IEEE 802.1Q-in-802.1Q Translation on a QinQ Link Bundle
Configuring the Service Provider Edge Router
Configuring QinQ Translation—Double Tag to Single Tag Translation
Configuring QinQ Transparent Tunneling—Double Tag to Double Tag Translation
Configuring a Policy Map to Use the Inner COS Bits
Disabling IEEE 802.1Q-in-802.1Q Mapping and Translation
Configuration Examples for Advanced QinQ Service Mapping
QinQ Translation Configuration Example—Two-Tag to One-Tag Translation
QinQ Transparent Tunneling Configuration Example
QinQ Translation Using Port-Channel Interfaces Example
Configuring 4-Port Gigabit Ethernet WAN Optical Services Modules
This chapter provides an overview of the features supported on the 4-port Gigabit Ethernet WAN Optical Services Modules (OSM-2+4GE-WAN+ and OSM-4GE-WAN-GBIC) supported on Cisco Catalyst 6500 series switches and Cisco 7600 series routers.
This chapter consists of these sections:
•
Saving your Configuration Before Upgrading from an OSM-4GE-WAN-GBIC to an OSM-2+4GE-WAN+
•
•
Supported Features
The following Layer 3 features are supported on the Gigabit Ethernet WAN optical services modules (OSMs):
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
Note
The Layer 2 Gigabit Ethernet ports on the OSMs are configured from the supervisor engine of the Cisco Catalyst 6500 series switch or the Cisco 7600 series router. For feature support and configuration information for the OSM Layer 2 Gigabit Ethernet ports, refer to the links in the "Layer 2 Software Features" section on page 1-5.
Saving your Configuration Before Upgrading from an OSM-4GE-WAN-GBIC to an OSM-2+4GE-WAN+
When you upgrade from OSM-4GE-WAN-GBIC to an OSM-2+4GE-WAN+, the existing configuration will not be saved and applied to the new OSM-2+4GE-WAN+.
To save your configuration when upgrading from an OSM-4GE-WAN-GBIC to an OSM-2+4GE-WAN+, perform this task:
Step 1
Step 2
Step 3
Step 4
Warning
Gigabit Ethernet WAN Port Configuration
The four Gigabit Ethernet WAN ports on the 4-port Gigabit Ethernet WAN OSMs are controlled by Cisco IOS software and support all standard Cisco IOS features. For configuration information for standard Cisco IOS features and routing protocols supported on the GE-WAN ports, refer to the appropriate Cisco IOS configuration guide and command reference publications at this URL:
http://www.cisco.com/univercd/cc/td/doc/product/software/ios121/121cgcr/index.htm
Basic Interface Configuration
After you verify that the 4-port Gigabit Ethernet WAN OSM is installed correctly, use the configure command to configure the Gigabit Ethernet WAN interfaces.
The following procedure is for creating a basic configuration—enabling an interface and specifying IP routing. You might also need to enter other configuration subcommands, depending on the requirements for your system configuration.
Note
Note
To configure the Gigabit Ethernet WAN interfaces, perform this task:
Step 1
Router# show versionStep 2
Router# show interfaceStep 3
Router# configure terminalStep 4
Router(config)# ip routingStep 5
Router(config)# interface ge-wan 3/0Step 6
Router(config-if)# ip address 10.1.2.3 255.255.255.255By default, a GE-WAN interface is configured for automatic negotiation of link parameters, such as duplex, speed, and flow control. To disable flow control and to force the interface for 1000/full-duplex mode, turn off automatic negotiation with the command:
Router(config-if)# no negotiation auto
Note
Tip
Step 7
Router(config-if)# no shutdownThe no shutdown command passes an enable command to the Gigabit Ethernet module. It also causes the module to configure itself based on the most recent configuration commands received by the module.
Step 8
Router# copy running-config startup-configWhen the configuration is stored, an OK message appears.
Configuring Strict Priority Low Latency Queuing (LLQ) Support on the OSM-2+4GE-WAN+
Starting with Cisco IOS Release 12.2(18)SXE, the Low Latency Queuing feature is changed for the OSM-2+4GE-WAN+ Optical Services Module. With this change, priority queue policing is supported on the module. Using Hiearchical Queuing Framework (HQF), the police command is combined with strict priority in a class on the OSM.
Note
If a second priority police class is included in the policy, police must be configured first.To configure strict priority LLQ support, perform the following tasks, starting in global configuration mode:
Examples
The following example shows a typical configuration and verification for the OSM-2+4GE-WAN+ OSM.
!Policy Map childClass dscp-efprioritypolice cir 1000000 bc 31250 be 31250 conform-action transmit exceed-action dropClass dscp-af21bandwidth remaining 35 (%)Class dscp-af31bandwidth remaining 30 (%)Class class-defaultbandwidth remaining 25 (%)!Policy Map parentClass vlan-2bandwidth 5000 (kbps)shape average 6000000 24000 24000service-policy child!interface ge-wan7/1no ip addressnegotiation automls qos trust dscpservice-policy output parentend!interface ge-wan7/1.2encapsulation dot1Q 2ip address 10.10.10.1 255.255.255.0mls qos trust dscpno cdp enableendThe following show command verifies the configuration:
Router#show policy interface ge-wan7/1
GE-WAN7/1
Service-policy output: parent
Class-map: vlan-2 (match-all)
0 packets, 0 bytes
5 minute offered rate 0 bps, drop rate 0 bps
Match: vlan 2
Queueing
queue limit 1250 (packets)
(queue depth/total drops/no-buffer drops) 0/0/0
(pkts queued/bytes queued) 0/0
bandwidth 5000 kbps
shape (average) cir 6000000, bc 24000, be 24000
target shape rate 6000000
(shape parameter is rounded to 5952000 bps due to granularity)
Service-policy : child
Class-map: dscp-ef (match-all)
0 packets, 0 bytes
5 minute offered rate 0 bps, drop rate 0 bps
Match: ip dscp ef
Priority: b/w exceed drops: 0
police:
cir 1000000 bps, bc 31250 bytes
(Police cir is rounded to 983040 bps due to granularity)
Class-map: dscp-af21 (match-all)
0 packets, 0 bytes
5 minute offered rate 0 bps, drop rate 0 bps
Match: ip dscp af21
Queueing
queue limit 350 (packets)
(queue depth/total drops/no-buffer drops) 0/0/0
(pkts queued/bytes queued) 0/0
bandwidth remaining 35% (1400 kbps)
(bandwidth parameter is rounded to 1392 kbps due to granularity)
Class-map: dscp-af31 (match-all)
0 packets, 0 bytes
5 minute offered rate 0 bps, drop rate 0 bps
Match: ip dscp af31
Queueing
queue limit 300 (packets)
(queue depth/total drops/no-buffer drops) 0/0/0
(pkts queued/bytes queued) 0/0
bandwidth remaining 30% (1200 kbps)
(bandwidth parameter is rounded to 1196 kbps due to granularity)
Class-map: class-default (match-any)
0 packets, 0 bytes
5 minute offered rate 0 bps, drop rate 0 bps
Match: any
Queueing
queue limit 250 (packets)
(queue depth/total drops/no-buffer drops) 0/0/0
(pkts queued/bytes queued) 0/0
bandwidth remaining 25% (1000 kbps)
Class-map: class-default (match-any)
0 packets, 0 bytes
5 minute offered rate 0 bps, drop rate 0 bps
Match: any
queue limit 248750 (packets)
(queue depth/total drops/no-buffer drops) 0/0/0
(pkts queued/bytes queued) 0/0Router#Quality of Services
The Gigabit Ethernet WAN modules support the following QoS implementations:
•
•
•
•
•
•
•
•
For QoS configuration information and examples for the WAN OSM ports, see the "Configuring QoS on the OSMs" section on page 9-2.
See Chapter 10, "Configuring Destination Sensitive Services on the Optical Services Modules" for configuration information.
Advanced QinQ Service Mapping
The IEEE 802.1Q VLAN specification provides for a trunking option that tags packets with two VLAN tags:
•
•
This type of double-tagged tunnel is referred to as IEEE 802.1Q-in-802.1Q (Q-in-Q) tunneling.
Standard QinQ tunneling, however, is limited. Although double-tagged VLANs can identify different customers, they cannot easily distinguish different service flows for the same customer. You can use separate VLANs for each service flow, but IEEE 802.1Q VLANs are limited to a maximum of 1,024 VLANs. Extended VLANs have a maximum of 4,096 per router, but even this larger number could be exhausted if many customers are using multiple services.
The Advanced QinQ Service Mapping feature solves these problems by enabling the Gigabit Ethernet WAN (GE-WAN) interfaces on the OSM-2+4GE-WAN+ Optical Services Module (OSM) to act as a QinQ access gateway. The access gateway enhances QinQ tunneling by using the combination of inner and outer VLAN tags as a unique identifier for a particular customer's service flows. This allows the interface to perform the following:
•
–
–
•
•
In Cisco IOS Release 12.2(18)SXE and later releases, you can also combine multiple GE-WAN interfaces into a virtual QinQ link bundle (also known as a port-channel). This simplifies configuration and allows the system to automatically load balance the traffic moving across the physical interfaces.
See the following sections for more details on the QinQ translation process and on using QinQ link bundles.
QinQ Translation—Double Tag to Single Tag Translation
In a double-tag-to-single-tag translation, the Advanced QinQ Service Mapping feature replaces both the inner customer edge (CE) VLAN tag and the outer provider edge (PE) VLAN tag with a single trunk VLAN tag. The following shows the format of both the incoming original packet and the outgoing translated packet.
0x8100
0x8100
0x8100
1 The CE VLAN tag might not be present if the customer did not tag this packet with a VLAN ID before transmitting it to the service provider. The PE VLAN tag should always be present.
When the interface receives a packet, the following occurs:
•
If the packet includes a PE VLAN tag, but no mapping has been configured for this particular CE VLAN tag, or if the incoming packet does not contain any inner CE VLAN tag, the interface drops the packet (unless a subinterface has been configured for out-of-range packets).
•
•
–
–
–
•
QinQ Transparent Tunneling—Double Tag to Double Tag Translation
When you configure the Advanced QinQ Service Mapping feature for double-tag-to-double-tag conversion, the Gigabit Ethernet WAN interface replaces the outer PE VLAN tag with the trunk VLAN tag. The inner CE VLAN tag remains unchanged. The following shows the format of both the incoming original packet and the outgoing translated packet:
0x8100
0x8100
0x8100
0x8100
1 The CE VLAN tag might not be present if the customer did not tag this packet with a VLAN ID before transmitting it to the service provider, in which case this becomes a single-tag to single-tag translation.
When the interface receives a packet, the following occurs:
•
If the packet includes a PE VLAN tag, but no mapping has been configured for this particular CE VLAN tag, or if the incoming packet does not contain any inner CE VLAN tag, the interface drops the packet (unless a subinterface has been configured for out-of-range packets).
•
•
–
–
–
•
Out-of-Range and Unspecified In-Range Packets
Each PE VLAN supports a maximum of 32 CE VLANs, which must be in a contiguous block that starts on a number divisible by 32 (for example: 0, 32, 64, and so on). When you specify the first CE VLAN ID for a PE VLAN (using the bridge-domain command), the Cisco IOS software automatically associates the corresponding block of 32 IDs with that PE VLAN. Any other CE VLANs are considered out-of-range for that particular PE VLAN.
For example, specifying a CE VLAN ID of 131 automatically associates the CE VLAN IDs from 128 to 159 with that particular PE VLAN. Any CE VLANs that are outside of that block (from 1 to 127 and from 160 to 4094) are considered out-of-range. In addition, if a packet arrives without a CE VLAN tag, it is also considered to be out-of-range.
The default behavior is to drop all out-of-range packets that are received on an interface that has been configured for QinQ translation. You can change this behavior by configuring a subinterface to match out-of-range packets.
The QinQ access gateway interface also drops any packets with a CE VLAN that is in-range (within the block of 32 VLAN IDs) but not explicitly mapped on a subinterface. This behavior cannot be changed. For example, if you specify a CE VLAN of 32 and no other CE VLANs for a particular PE VLAN, the interface drops packets for that PE VLAN that have CE VLANs from 33 and 63.
Per VLAN Load Balancing for Advanced QinQ Service Mapping
In Cisco IOS Release 12.2(18)SXE and later releases, you can combine multiple GE-WAN interfaces into a QinQ link bundle, which is a virtual interface that you configure in the same way as the physical GE-WAN interfaces. Using QinQ link bundles has the following advantages:
•
•
•
•
Note
•
•
•
•
Configuring Advanced QinQ Service Mapping
This section describes the following configuration tasks that are needed to enable and configure the Advanced QinQ Service Mapping feature:
•
•
•
•
•
•
•
Enabling IEEE 802.1Q-in-802.1Q Translation on a Gigabit Ethernet WAN Interface
To use the Advanced QinQ Service Mapping feature, you must first enable IEEE 802.1Q-in-802.1Q translation on the Gigabit Ethernet WAN interface that is connected to the provider edge router through the Metro Ethernet network. You can also optionally configure the interface as trusted, if you want to preserve the IEEE 802.1P bits (P bits) that are in the IEEE 802.1Q header of incoming packets.
To enable IEEE 802.1Q-in-802.1Q translation on a Gigabit Ethernet WAN interface, and optionally configure the interface as trusted, use the following procedure.
Prerequisites
•
•
•
•
Note
Restrictions
•
•
•
•
•
•
•
•
For example, if interface 1 assigns VLAN ID 200 to an MPLS-based feature (such as MPLS VPN, AToM, or VPLS), you cannot use VLAN 200 as a PE VLAN on either interface 1 or 2. However, you still can use VLAN 200 on interface 3 or 4, because those interfaces are a separate interface pair.
•
•
The router, by default, allocates internal VLANs starting with 1006 and ascending sequentially. We recommend that you change this behavior with the vlan internal allocation policy descending global configuration command, so that the router allocates internal VLANs starting with 4094 and descending sequentially.
Note
Tip
•
SUMMARY STEPS
1.
2.
3.
4.
5.
6.
7.
8.
9.
Tip
DETAILED STEPS
Step 1
enable
Example:Router> enable
Router#
Enables privileged EXEC mode. Enter your password if prompted.
Step 2
configure terminal
Example:Router# configure terminal
Router(config)#
Enters global configuration mode.
Step 3
vlan internal allocation policy descending
Example:Router(config)# vlan internal allocation policy descending
Router(config)#
(Optional) Allocates internal VLANs starting with 4094 and descending sequentially. We recommend this configuration to avoid conflicts with the PE VLAN ID assignment.
Note
Step 4
interface ge-wan slot/port
Example:Router(config)# interface ge-wan 5/1
Router(config-if)#
Enters interface configuration mode for the specified Gigabit Ethernet WAN interface on the OSM-2+4GE-WAN+ Gigabit Ethernet WAN port.
Step 5
no ip address
Example:Router(config-if)# no ip address
Router(config-if)#
(Optional) Removes the IP address that might be configured on the interface. This step is required if the interface has been configured previously with an IP address.
Step 6
mode dot1q-in-dot1q access-gateway
Example:Router(config-if)# mode dot1q-in-dot1q access-gateway
Router(config-if)#
Enables IEEE 802.1Q-in-802.1Q translation on the interface, enabling the Advanced QinQ Service Mapping feature.
Step 7
description string
Example:Router(config-if)# description Connected to ISP ABC Port SJ-2
Router(config-if)#
(Optional) Provides a description of this interface. The string parameter can be any arbitrary text that describes the interface, its neighbor, its purpose, or any other information that might be useful for maintaining and troubleshooting problems with this interface and configuration.
Step 8
no shutdown
Example:Router(config-if)# no shutdown
Router(config-if)#
Activates the interface and enables it to pass traffic.
Note
Step 9
end
Example:Router(config-if)# end
Router#
Exits interface configuration mode and returns to privileged EXEC mode.
Examples
The following example shows a sample configuration for a Gigabit Ethernet WAN interface:
!interface GE-WAN3/4description connected to SJ QinQ Tunnelno ip addresslogging event link-statusnegotiation automode dot1q-in-dot1q access-gatewayEnabling IEEE 802.1Q-in-802.1Q Translation on a QinQ Link Bundle
To use the Advanced QinQ Service Mapping feature on a QinQ link bundle, you must create a virtual port-channel interface and enable IEEE 802.1Q-in-802.1Q translation on that interface. You then must assign Gigabit Ethernet WAN interfaces to the port-channel group. To perform these tasks, use the following procedure.
Prerequisites
•
•
•
Restrictions
•
•
•
•
•
•
•
•
SUMMARY STEPS
1.
2.
3.
4.
5.
6.
7.
8.
9.
10.
11.
12.
13.
Tip
DETAILED STEPS
Step 1
enable
Example:Router> enable
Router#
Enables privileged EXEC mode. Enter your password if prompted.
Step 2
configure terminal
Example:Router# configure terminal
Router(config)#
Enters global configuration mode.
Step 3
vlan internal allocation policy descending
Example:Router(config)# vlan internal allocation policy descending
Router(config)#
(Optional) Allocates internal VLANs starting with 4094 and descending sequentially. We recommend this configuration to avoid conflicts with the assignment of IDs for the PE VLANs.
Note
Step 4
interface port-channel number
Example:Router(config)# interface port-channel 5
Router(config-if)#
Creates a virtual port-channel interface and enters interface configuration mode. The valid range for number is from 1 to 256.
Step 5
no ip address
Example:Router(config-if)# no ip address
Router(config-if)#
(Optional) Removes the IP address that might be configured on the interface. This step is required if the interface has been configured previously with an IP address.
Step 6
mode dot1q-in-dot1q access-gateway
Example:Router(config-if)# mode dot1q-in-dot1q access-gateway
Router(config-if)#
Enables IEEE 802.1Q-in-802.1Q translation on the interface, enabling the Advanced QinQ Service Mapping feature.
Note
Step 7
description string
Example:Router(config-if)# description QinQ Link Bundle connected to LA-10/1
Router(config-if)#
(Optional) Provides a description of this interface. The string parameter can be any arbitrary text that describes the interface, its neighbor, its purpose, or any other information that might be useful for maintaining and troubleshooting problems with this interface and configuration.
Step 8
no shutdown
Example:Router(config-if)# no shutdown
Router(config-if)#
Activates the interface and enables it to pass traffic.
Step 9
interface ge-wan slot/port
Example:Router(config)# interface ge-wan 5/1
Router(config-if)#
Enters interface configuration mode for either the specified Gigabit Ethernet WAN interface on the OSM-2+4GE-WAN+ Gigabit Ethernet WAN port.
Step 10
no ip address
Example:Router(config-if)# no ip address
Router(config-if)#
(Optional) Removes the IP address that might be configured on the interface. This step is required if the interface has been configured previously with an IP address.
Step 11
channel-group number mode on
Example:Router(config-if)# channel-group 5 mode on
Router(config-if)#
Adds this physical interface to the specified channel group. The number should be the same as that specified for the port-channel interface in Step 4.
Note
Step 12
no shutdown
Example:Router(config-if)# no shutdown
Router(config-if)#
Activates the interface and enables it to pass traffic.
Note
Step 13
end
Example:Router(config-if)# end
Router#
Exits interface configuration mode and returns to privileged EXEC mode.
Note
Examples
The following example shows a sample configuration for a port-channel interface that has two GE-WAN physical interfaces as part of its channel group:
!interface Port-channel3no ip addresslogging event link-statusspeed nonegotiatemode dot1q-in-dot1q access-gateway!interface GE-WAN2/1no ip addresslogging event link-statusnegotiation autochannel-group 3 mode on!interface GE-WAN2/3no ip addresslogging event link-statusnegotiation autochannel-group 3 mode onThe following sample configuration shows the error message that appears if you attempt to enable QinQ translation on a port-channel interface that contains one or more invalid interfaces:
Router# configure terminalRouter(config)# interface port-channel 307600-2(config-if)# mode dot1q-in-dot1q access-gateway% 'mode dot1q-in-dot1q access-gateway' is not supported on Port-channel30% Port-channel30 contains 2 Layer 2 Gigabit Ethernet interface(s)Router(config-if)#To display the status of the port-channel interface, as well as the members of its channel group, use the show interface command. For example, this command would show the following output for the configuration listed above.
Router# show interface Port-channel 3Port-channel1 is up, line protocol is up (connected)Hardware is EtherChannel, address is 0007.8508.474a (bia 000d.edb5.7d7b)MTU 1500 bytes, BW 2000000 Kbit, DLY 10 usec,reliability 255/255, txload 1/255, rxload 1/255Encapsulation ARPA, loopback not setFull-duplex, Auto-speedinput flow-control is off, output flow-control is unsupportedMembers in this channel: GE2/1 Pseudo GE2/3 PseudoARP type: ARPA, ARP Timeout 04:00:00Last input never, output never, output hang neverLast clearing of "show interface" counters neverInput queue: 0/75/0/0 (size/max/drops/flushes); Total output drops: 0Queueing strategy: fifoOutput queue: 0/40 (size/max)5 minute input rate 0 bits/sec, 0 packets/sec5 minute output rate 0 bits/sec, 0 packets/sec0 packets input, 0 bytes, 0 no bufferReceived 0 broadcasts (0 IP multicast)0 runts, 0 giants, 0 throttles0 input errors, 0 CRC, 0 frame, 0 overrun, 0 ignored0 watchdog, 0 multicast, 0 pause input0 input packets with dribble condition detected0 packets output, 0 bytes, 0 underruns0 output errors, 0 collisions, 0 interface resets0 babbles, 0 late collision, 0 deferred0 lost carrier, 0 no carrier, 0 PAUSE output0 output buffer failures, 0 output buffers swapped outRouter#To display the inner, outer, and trunk VLANs that are used in a QinQ translation, use the show cwan qinq command. The following examples show the resulting output for the port-channel interface using the show cwan qinq command alone and with each of the following optional keywords:
•
•
•
Caution
Router#show cwan qinq
Bridge-domain Interface Egress-if Inner-start Total Active
3 Po1 GE3/1 0 1 1
Sub-Interface Trunk-vlan Inner-vlan Service State
Po1.2 2 4 dot1q up/up
Router#show cwan qinq configured
Port-channel1 has total 2 bridge-domain vlan(s)
Po1 - GE-WAN3/1 has 1 bridge-domain vlan(s) egress configured
13
Po1 - GE-WAN3/2 has 1 bridge-domain vlan(s) egress configured
3
Router#show cwan qinq detail
Port-channel1 has total 2 bridge-domain vlan(s)
Po1 - GE-WAN3/1 has 1 bridge-domain vlan(s) detail
Bridge-domain Inner Configured Active
------------- ------ ---------- ------
13 active 1 1
Po1 - GE-WAN3/2 has 1 bridge-domain vlan(s) detail
Bridge-domain Inner Configured Active
------------- ------ ---------- ------
3 active 1 1
Router#show cwan qinq list
Port-channel1 has total 2 bridge-domain vlan(s)
Po1 - GE-WAN3/1 has 1 bridge-domain vlan(s) egress active
13
Po1 - GE-WAN3/2 has 1 bridge-domain vlan(s) egress active
3
The related show cwan qinq load-balance commands also apply to port-channel interfaces only.
Router#show cwan qinq load-balance
Port-channel1 has total 2 bridge-domain vlan(s)
Po1 - GE-WAN3/1 has 1 bridge-domain vlan(s)
Po1 - GE-WAN3/2 has 1 bridge-domain vlan(s)
Router#show cwan qinq load-balance detailPort-channel1 has total 2 bridge-domain vlan(s)Po1 - GE-WAN3/1 has 1 bridge-domain vlan(s) detailBridge-domain Inner Configured Active------------- ------ ---------- ------13 active 1 1Po1 - GE-WAN3/2 has 1 bridge-domain vlan(s) detailBridge-domain Inner Configured Active------------- ------ ---------- ------3 active 1 1
The following related show commands can be applied to both port-channel and physical interfaces:
Router#show cwan qinq bridge-domain
GE-WAN3/1, group 1, total_rate_active 1
13
GE-WAN3/2, group 1, total_rate_active 1
3
Port-channel1, group 1, total_rate_active 2
Router#show cwan qinq interface
Interface Status Egress op PE CE TRNK Input packets/ Output packets/
Input bytes Output bytes
---------------- --------- ------ -- ---- ---- ---- -------------------- ----------------
Po1.2 up/up GE3/2 1 3 4 2 0 0
0 0
Po1.12 up/up GE3/1 1 13 14 12 0 0
0 0
Note
Configuring the Service Provider Edge Router
This section describes the procedure to configure the Gigabit Ethernet interface on the service provider edge router that is connected to the Gigabit Ethernet WAN interface that is acting as the IEEE 802.1Q-in-802.1Q (QinQ) access gateway.
Prerequisites
•
SUMMARY STEPS
1.
2.
3.
4.
5.
6.
7.
8.
9.
10.
11.
12.
13.
DETAILED STEPS
Step 1
enable
Example:Router> enable
Router#
Enables privileged EXEC mode. Enter your password if prompted.
Step 2
configure terminal
Example:Router# configure terminal
Router(config)#
Enters global configuration mode.
Step 3
vlan vlan-id
Example:Router(config)# vlan 22
Router(config)#
Add the VLAN ID to be used as the provider edge (PE) VLAN to the router's VLAN database (if not already entered). The valid range for vlan-id is either 1 to 1023, or from 1 to 4094, depending on the Cisco IOS software image being used on the router or switch.
Step 4
interface GigabitEthernet slot/port
Example:Router(config)# interface GigabitEthernet3/1
Router(config-if)#
Enters interface configuration mode for the specified Gigabit Ethernet interface.
Step 5
no ip address
Example:Router(config-if)# no ip address
Router(config-if)#
Removes the IP address that might be configured on the interface.
Step 6
mls qos trust [cos | dscp | ip-precedence]
Example:Router(config-if)# mls qos trust dscp
Router(config-if)#
(Optional) Specifies which quality of service (QoS) bits in incoming frames can be trusted.
•
•
•
Note
Step 7
switchport
Example:Router(config-if)# switchport
Router(config-if)#
Configures the interface for Layer 2 switching.
Step 8
switchport trunk encapsulation dot1q
Example:Router(config-if)# switchport trunk encapsulation dot1q
Router(config-if)#
Configures the trunk link to use IEEE 802.1Q encapsulation.
Step 9
switch trunk allowed vlan {vlan-list | vlan-range}
Example:Router(config-if)# switch trunk allowed vlan 3001-4000
Router(config-if)#
(Optional) Configures the list of provider edge (PE) VLANs allowed on the trunk. All VLANs are allowed by default. You can either specify a list of individual VLAN IDs separated by commas, or you can specify a range of VLAN IDs separated by a hyphen.
Step 10
switchport mode trunk
Example:Router(config-if)# switchport mode trunk
Router(config-if)#
Puts the interface into permanent trunking mode.
Step 11
description string
Example:Router(config-if)# description Connected to Metro interface SJ-3
Router(config-if)#
(Optional) Provides a description of this interface. The string parameter can be any arbitrary text that describes the interface, its neighbor, its purpose, or any other information that might be useful for maintaining and troubleshooting problems with this interface and configuration.
Step 12
no shutdown
Example:Router(config-if)# no shutdown
Router(config-if)#
Activates the interface and enables it to pass traffic.
Note
Step 13
end
Example:Router(config-if)# end
Router#
Exits interface configuration mode and returns to privileged EXEC mode.
Examples
The following example shows a sample configuration for a Gigabit Ethernet interface that is connected to the Gigabit Ethernet WAN port that is providing IEEE 802.1Q-in-802.1Q translation. VLAN ID 3001 is being used as the PE VLAN.
vlan 3001...!interface GigabitEthernet3/1description connected to Metro SJ-3 (QinQ tunnel)no ip addresslogging event link-statusswitchportswitchport trunk encapsulation dot1qswitchport trunk allowed vlan 3001-4000switchport mode trunkConfiguring QinQ Translation—Double Tag to Single Tag Translation
When you configure the Advanced QinQ Service Mapping feature for QinQ translation, also known as double-tag-to-single-tag translation, the outgoing interface replaces both the inner customer edge (CE) VLAN tag and the outer provider edge (PE) VLAN tag with a Trunk VLAN tag. Use the following procedure to configure a subinterface for double-tag-to-single-tag translation.
Note
Prerequisites
•
Restrictions
•
•
•
•
SUMMARY STEPS
1.
2.
3.
4.
5.
or
bridge-domain vlan-id dot1q-tunnel out-range6.
7.
8.
9.
DETAILED STEPS
Step 1
enable
Example:Router> enable
Router#
Enables privileged EXEC mode. Enter your password if prompted.
Step 2
configure terminal
Example:Router# configure terminal
Router(config)#
Enters global configuration mode.
Step 3
interface {ge-wan slot/port.subinterface | port-channel number.subinterface}
Example:Router(config)# interface ge-wan 5/1.64
Router(config-subif)#
Enters subinterface mode for the specified subinterface.
Step 4
encapsulation dot1q trunk-vlan-id
Example:Router(config-subif)# encapsulation dot1q 2
Router(config-subif)#
Configures the subinterface to use the specified IEEE 802.1Q trunk VLAN on outgoing packets:
•
Step 5
bridge-domain vlan-id dot1q inner-vlan-id
or
bridge-domain vlan-id dot1q-tunnel out-range
Example:Router(config-subif)# bridge-domain 2 dot1q 64
Router(config-subif)#
or
Router(config-subif)# bridge-domain 2 dot1q-tunnel out-range
Router(config-subif)#
Creates a table map for the specified outer (provider) VLAN ID to the specified inner (customer) VLAN ID, specifying that these VLAN tags should be replaced by the trunk VLAN tag when the packet is output.
•
•
•
Note
Note
Step 6
mls qos trust [cos | dscp | ip-precedence]
Example:Router(config-subif)# mls qos trust dscp
Router(config-subif)#
(Optional) Specifies which quality of service (QoS) bits in incoming frames can be trusted.
•
•
•
Note
Step 7
service policy input policy-name
Example:Router(config-subif)# service policy input policy-in1
Router(config-subif)#
(Supported only on physical GE-WAN interfaces, not port-channel interfaces) Specifies a policy map that should be used on incoming packets when they are received on the Gigabit Ethernet WAN interface.
Step 8
service policy output policy-name
Example:Router(config-subif)# service policy output cos-xlat1
Router(config-subif)#
Specifies a policy map that should be used on outgoing packets before they leave the Gigabit Ethernet WAN interface.
Note
Note
Step 9
end
Example:Router(config)# end
Router#
Exits global configuration mode and returns to privileged EXEC mode.
Examples
The following shows a typical configuration that creates two double-tag-to-single-tag mappings on a subinterface. The first subinterface configuration creates a specific PE/CE mapping, and the second subinterface configuration creates an out-of-range configuration:
interface GE-WAN 3/3no ip addressmode dot1q-indot1q access-gateway...!interface GE-WAN3/3.42encapsulation dot1Q 2bridge-domain 133 dot1q 42mls qos trust dscpend...!interface GE-WAN3/3.5032encapsulation dot1Q 31bridge-domain 133 dot1q-tunnel out-rangemls qos trust dscpendThese QinQ mappings operate as follows:
•
•
This configuration performs the following mapping on packets that have a PE VLAN ID of 133:
Configuring QinQ Transparent Tunneling—Double Tag to Double Tag Translation
When you configure the Advanced QinQ Service Mapping feature for QinQ transparent tunneling, as known as double-tag-to-double-tag translation, the Gigabit Ethernet WAN interface replaces the outer (provider edge or PE) VLAN tag with the trunk VLAN tag. The inner CE VLAN tag (if present) remains unchanged. Use the following procedure to configure a subinterface for double-tag-to-double-tag translation.
Note
Prerequisites
•
Restrictions
•
•
•
•
•
SUMMARY STEPS
1.
2.
3.
4.
5.
6.
7.
8.
9.
DETAILED STEPS
Step 1
enable
Example:Router> enable
Router#
Enables privileged EXEC mode. Enter your password if prompted.
Step 2
configure terminal
Example:Router# configure terminal
Router(config)#
Enters global configuration mode.
Step 3
interface {ge-wan slot/port.subinterface | port-channel number.subinterface}
Example:Router(config)# interface ge-wan 5/1.64
Router(config-subif)#
Enters subinterface mode for the specified subinterface.
Step 4
encapsulation dot1q trunk-vlan-id
Example:Router(config-subif)# encapsulation dot1q 2
Router(config-subif)#
Configures the subinterface to use the specified IEEE 802.1Q trunk VLAN on outgoing packets:
•
Step 5
bridge-domain vlan-id dot1q-tunnel {inner-vlan-id | out-range}
Example:Router(config-subif)# bridge-domain 2 dot1q 64
Router(config-subif)#
or
Router(config-subif)# bridge-domain 2 dot1q out-range
Router(config-subif)#
Creates a table map for the specified outer (provider) VLAN ID to the specified inner (customer) VLAN ID, specifying that the outer VLAN tag should be replaced by the trunk VLAN tag when the packet is output (leaving the inner tag unchanged):
•
•
•
Note
Note
Step 6
mls qos trust [cos | dscp | ip-precedence]
Example:Router(config-subif)# mls qos trust dscp
Router(config-subif)#
(Optional) Specifies which quality of service (QoS) bits in incoming frames can be trusted.
•
•
•
Note
Step 7
service policy input policy-name
Example:Router(config-subif)# service policy input policy-in1
Router(config-subif)#
(Supported only on physical GE-WAN interfaces, not port-channel interfaces) Specifies a policy map that should be used on incoming packets when they are received on the Gigabit Ethernet WAN interface.
Step 8
service policy output policy-name
Example:Router(config-subif)# service policy output cos-xlat1
Router(config-subif)#
Specifies a policy map that should be used on outgoing packets before they leave the Gigabit Ethernet WAN interface.
Note
Step 9
end
Example:Router(config)# end
Router#
Exits global configuration mode and returns to privileged EXEC mode.
Examples
The following shows a typical configuration that creates two double-tag-to-double-tag mappings on a subinterface. The first subinterface configuration creates a specific PE/CE mapping, and the second subinterface configuration creates an out-of-range configuration:
!interface GE-WAN1/1.98encapsulation dot1Q 12bridge-domain 65 dot1q-tunnel 98mls qos trust dscpend...!interface GE-WAN1/1.5096encapsulation dot1Q 31bridge-domain 65 dot1q-tunnel out-rangemls qos trust dscpendThese QinQ mappings operate as follows:
•
•
This configuration performs the following mapping on packets that have a PE VLAN ID of 65:
Configuring a Policy Map to Use the Inner COS Bits
By default, the IEEE 802.1Q-to-IEEE 802.1Q translation sets the IEEE 802.1P bits (P bits) in the IEEE 802.1Q header of the outgoing packet's trunk VLAN tag by copying the P bits from the outer PE VLAN tag. To change this behavior, create a policy map with a class map that contains the set cos cos-inner command. The system then copies the P bits from the inner CE VLAN tag to the trunk VLAN tag that is put on the outgoing packet.
Prerequisites
•
–
–
Restrictions
•
•
•
SUMMARY STEPS
1.
2.
3.
4.
5.
6.
7.
8.
DETAILED STEPS
Examples
The following example shows a typical policy map configuration using the set cos cos-inner command:
!policy-map pmap1class class-defaultshape average 4000000set cos cos-innerDisabling IEEE 802.1Q-in-802.1Q Mapping and Translation
To disable the mapping and translation of IEEE 802.1Q-in-802.1Q double-tagged packets on the Gigabit Ethernet interface or on one of its subinterfaces, use one of the following procedures:
•
•
Disabling All IEEE 802.1Q-to-802.1Q Translation on An Interface
To disable all IEEE 802.1Q-to-802.1Q translation on a Gigabit Ethernet WAN interface or a port-channel interface, use the following procedure. This procedure also removes all subinterfaces and their configurations from the interface, which then allows the associated VLANs to be used for other purposes or on other cards.
Tip
Note
Note
.Prerequisites
If you have previously attached a service policy that contains a set cos cos-inner command to the interface, you must first remove that service policy before you can use the no mode dot1q-in-dot1q access-gateway command.
SUMMARY STEPS
1.
2.
3.
4.
5.
6.
DETAILED STEPS
Disabling IEEE 802.1Q-to-802.1Q Translation on One Subinterface
Use the following procedure to disable IEEE 802.1Q-to-802.1Q translation on an individual subinterface. You can either completely delete the subinterface, or you can remove just the bridge-domain configuration on the subinterface, depending on whether you want to use the subinterface to continue passing other traffic. Both methods release the CE and PE VLANs being used on the subinterface.
Prerequisites
If you have previously attached a service policy that contains a set cos cos-inner command to the interface, you must first remove that service policy before you can use the no bridge-domain command.
SUMMARY STEPS
1.
2.
3.
or
4.
5.
6.
DETAILED STEPS
Step 1
enable
Example:Router> enable
Router#
Enables privileged EXEC mode. Enter your password if prompted.
Step 2
configure terminal
Example:Router# configure terminal
Router(config)#
Enters global configuration mode.
Step 3
no interface {ge-wan slot/port.subinterface | port-channel number.subinterface}
Example:Router(config)# no interface ge-wan 5/1.64
Router(config-subif)#
Completely removes the subinterface and its configuration. All traffic passing through this interface stops.
Note
or
Step 4
interface {ge-wan slot/port.subinterface | port-channel number.subinterface}
Example:Router(config)# interface ge-wan 5/1.64
Router(config-subif)#
Enters subinterface mode for the specified subinterface.
Step 5
no bridge-domain vlan-id dot1q {inner-vlan-id | out-range}
Example:Router(config-subif)# no bridge-domain 2 dot1q 64
Router(config-subif)#
Removes the table mapping for this subinterface, disabling the IEEE 802.1Q-to-IEEE802.1Q translation for this particular combination of VLANs. Traffic continues to pass, depending on the remaining configuration of the subinterface.
Step 6
end
Example:Router(config-subif)# end
Router#
Exits subinterface configuration mode and returns to privileged EXEC mode.
Configuration Examples for Advanced QinQ Service Mapping
This section provides the following sample configurations:
•
•
•
QinQ Translation Configuration Example—Two-Tag to One-Tag Translation
The following excerpt from a configuration file shows the configuration for a simple QinQ translation, in which incoming packets are received with inner customer edge (CE) and outer provider edge (PE) VLAN tags. The packets are then output, using the configured policy map, with a single trunk VLAN tag.
This configuration configures Gigabit Ethernet WAN interface 4/1 as the QinQ access gateway, and shows two PE-to-CE mappings:
•
Subinterface 47 is configured to match any packets that arrive with a PE VLAN ID of 2 and an out-of-range CE VLAN ID (between 47 and 63). Note that the set cos cos-inner command has no effect on out-of-range packets, even when using a policy map that includes this command.
•
!vlan internal allocation policy descending!vlan 1-1240!policy-map pmap1class class-defaultshape average 4000000set cos cos-innerpolicy-map pmap2class class-defaultshape average 8000000 32000 32000set cos cos-innerpolicy-map pmap3class class-defaultshape average 20000000 80000 80000set cos cos-innerpolicy-map pmap4class class-defaultshape average 2000000 16000 16000!!interface GigabitEthernet4/1description connected to SP GE1/3no ip addresslogging event link-statusswitchportswitchport trunk encapsulation dot1qswitchport mode trunk!interface GigabitEthernet4/2no ip addressshutdown!!--This is the QinQ Access Gateway interfaceinterface GE-WAN4/1description connected to PE-4 GigabitEthernet0/3no ip addresslogging event link-statusnegotiation automode dot1q-in-dot1q access-gateway!--This command configures the interface as trusted, which!--is required to be able to use the original packet's 802.1P CoS bits.mls qos trust dscp!--First set of PE/CE mappings!interface GE-WAN4/1.32encapsulation dot1Q 32!--note that this bridge-domain command automatically configures the!--CE VLAN range for this PE VLAN to be from 32 to 63bridge-domain 2 dot1q 32mls qos trust dscpservice-policy output pmap3!interface GE-WAN4/1.33encapsulation dot1Q 33bridge-domain 2 dot1q 33mls qos trust dscpservice-policy output pmap2!interface GE-WAN4/1.34encapsulation dot1Q 34bridge-domain 2 dot1q 34mls qos trust dscpservice-policy output pmap1!interface GE-WAN4/1.35encapsulation dot1Q 35bridge-domain 2 dot1q 35mls qos trust dscpservice-policy output pmap2!interface GE-WAN4/1.36encapsulation dot1Q 36bridge-domain 2 dot1q 36mls qos trust dscpservice-policy output pmap3!interface GE-WAN4/1.37encapsulation dot1Q 37bridge-domain 2 dot1q 37mls qos trust dscpservice-policy output pmap1!interface GE-WAN4/1.38encapsulation dot1Q 38bridge-domain 2 dot1q 38mls qos trust dscpservice-policy output pmap1!interface GE-WAN4/1.39encapsulation dot1Q 39bridge-domain 2 dot1q 39mls qos trust dscpservice-policy output pmap2!interface GE-WAN4/1.40encapsulation dot1Q 40bridge-domain 2 dot1q 40mls qos trust dscpservice-policy output pmap3!interface GE-WAN4/1.41encapsulation dot1Q 41bridge-domain 2 dot1q 41mls qos trust dscpservice-policy output pmap2!interface GE-WAN4/1.42encapsulation dot1Q 42bridge-domain 2 dot1q 42mls qos trust dscpservice-policy output pmap1!interface GE-WAN4/1.43encapsulation dot1Q 43bridge-domain 2 dot1q 43mls qos trust dscpservice-policy output pmap2!interface GE-WAN4/1.44encapsulation dot1Q 44bridge-domain 2 dot1q 44mls qos trust dscpservice-policy output pmap3!interface GE-WAN4/1.45encapsulation dot1Q 45bridge-domain 2 dot1q 45mls qos trust dscpservice-policy output pmap3!interface GE-WAN4/1.46encapsulation dot1Q 46bridge-domain 2 dot1q 46mls qos trust dscpservice-policy output pmap1!interface GE-WAN4/1.47description out-of-range configuration for CE VLANs 47 to 63encapsulation dot1Q 47bridge-domain 2 dot1q-tunnel out-rangemls qos trust dscp!-- Although this policy map includes the set cos cos-inner command,!-- this command is not used for out-of-range packetsservice-policy output pmap4!--Second set of PE/CE mappings!interface GE-WAN4/1.1237encapsulation dot1Q 1237!--note that this bridge-domain command automatically configures the!--CE VLAN range for this PE VLAN to be from 1216 to 1247bridge-domain 45 dot1q 1237no mls qos trustservice-policy output pmap4!interface GE-WAN4/1.1238encapsulation dot1Q 1238bridge-domain 45 dot1q 1238no mls qos trustservice-policy output pmap4!interface GE-WAN4/1.1239encapsulation dot1Q 1239bridge-domain 45 dot1q 1239no mls qos trustservice-policy output pmap4!interface GE-WAN4/1.1240encapsulation dot1Q 1240bridge-domain 45 dot1q 1240no mls qos trustservice-policy output pmap4...QinQ Transparent Tunneling Configuration Example
The following excerpt from a configuration file shows a typical configuration for a simple QinQ transparent tunneling configuration, in which incoming packets are received with inner customer edge (CE) and outer provider edge (PE) VLAN tags. The packets are then output, using the configured policy map, with a new trunk VLAN tag and the original inner CE VLAN tag. This configuration is called two-tag to one-tag translation.
This configuration configures Gigabit Ethernet WAN interface 4/1 as the QinQ access gateway, and creates a PE/CE mapping with the following characteristics:
•
•
•
•
!vlan internal allocation policy descending!vlan 1-4094...!--This is an IP LAN interfaceinterface GigabitEthernet4/1description QinQ tunnel to Catalyst 3550 Gigabit Ethernet 0/6no ip addressswitchportswitchport trunk encapsulation dot1qswitchport trunk allowed vlan 340switchport mode trunk!!interface GigabitEthernet4/2no ip addressshutdown!!--This is the QinQ Access Gateway interfaceinterface GE-WAN4/1description connected to GSR Gigabit Ethernet 4/1no ip addresslogging event link-statusno negotiation automode dot1q-in-dot1q access-gatewaymls qos trust dscp!interface GE-WAN4/1.15201encapsulation dot1Q 180!--note that this bridge-domain command automatically configures the!--CE VLAN range for this PE VLAN to be from 2048 to 2079bridge-domain 152 dot1q-tunnel 2048mls qos trust dscp!interface GE-WAN4/1.15203encapsulation dot1Q 182bridge-domain 152 dot1q-tunnel 2049mls qos trust dscp!interface GE-WAN4/1.15204encapsulation dot1Q 183bridge-domain 152 dot1q-tunnel 2050mls qos trust dscp!interface GE-WAN4/1.15205encapsulation dot1Q 184bridge-domain 152 dot1q-tunnel 2051mls qos trust dscp!interface GE-WAN4/1.15206encapsulation dot1Q 185bridge-domain 152 dot1q-tunnel 2052mls qos trust dscp!interface GE-WAN4/1.15207encapsulation dot1Q 186bridge-domain 152 dot1q-tunnel 2053mls qos trust dscp!interface GE-WAN4/1.15208encapsulation dot1Q 187bridge-domain 152 dot1q-tunnel 2054mls qos trust dscp!interface GE-WAN4/1.15209encapsulation dot1Q 188bridge-domain 152 dot1q-tunnel 2055mls qos trust dscp!interface GE-WAN4/1.15210encapsulation dot1Q 189bridge-domain 152 dot1q-tunnel 2056mls qos trust dscp!interface GE-WAN4/1.15211encapsulation dot1Q 190bridge-domain 152 dot1q-tunnel 2057mls qos trust dscp!interface GE-WAN4/1.15212encapsulation dot1Q 191bridge-domain 152 dot1q-tunnel 2058mls qos trust dscp!interface GE-WAN4/1.15213encapsulation dot1Q 192bridge-domain 152 dot1q-tunnel 2059mls qos trust dscp!interface GE-WAN4/1.15214encapsulation dot1Q 193bridge-domain 152 dot1q-tunnel 2060mls qos trust dscp!interface GE-WAN4/1.15215encapsulation dot1Q 194bridge-domain 152 dot1q-tunnel 2061mls qos trust dscp!interface GE-WAN4/1.15216encapsulation dot1Q 195bridge-domain 152 dot1q-tunnel 2062mls qos trust dscp!interface GE-WAN4/1.15217encapsulation dot1Q 196bridge-domain 152 dot1q-tunnel 2063mls qos trust dscp!interface GE-WAN4/1.15218encapsulation dot1Q 197bridge-domain 152 dot1q-tunnel 2064mls qos trust dscp!interface GE-WAN4/1.15219encapsulation dot1Q 198bridge-domain 152 dot1q-tunnel 2065mls qos trust dscp!interface GE-WAN4/1.15220encapsulation dot1Q 199bridge-domain 152 dot1q-tunnel 2066mls qos trust dscp!interface GE-WAN4/1.15221encapsulation dot1Q 200bridge-domain 152 dot1q-tunnel 2067mls qos trust dscp!interface GE-WAN4/1.15222encapsulation dot1Q 201bridge-domain 152 dot1q-tunnel 2068mls qos trust dscp!interface GE-WAN4/1.15223encapsulation dot1Q 202bridge-domain 152 dot1q-tunnel 2069mls qos trust dscp!interface GE-WAN4/1.15224encapsulation dot1Q 203bridge-domain 152 dot1q-tunnel 2070mls qos trust dscp!interface GE-WAN4/1.15225encapsulation dot1Q 204bridge-domain 152 dot1q-tunnel 2071mls qos trust dscp!interface GE-WAN4/1.15226encapsulation dot1Q 205bridge-domain 152 dot1q-tunnel 2072mls qos trust dscp!interface GE-WAN4/1.15227encapsulation dot1Q 206bridge-domain 152 dot1q-tunnel 2073mls qos trust dscp!interface GE-WAN4/1.15228encapsulation dot1Q 207bridge-domain 152 dot1q-tunnel 2074mls qos trust dscp!interface GE-WAN4/1.15229encapsulation dot1Q 208bridge-domain 152 dot1q-tunnel 2075mls qos trust dscp!interface GE-WAN4/1.15230encapsulation dot1Q 209bridge-domain 152 dot1q-tunnel 2076mls qos trust dscp!interface GE-WAN4/1.15231encapsulation dot1Q 210bridge-domain 152 dot1q-tunnel 2077mls qos trust dscp!interface GE-WAN4/1.15232encapsulation dot1Q 211bridge-domain 152 dot1q-tunnel 2078mls qos trust dscp!! This creates an out-of-range configuration that matches CE VLANs! that are out of the configured CE VLAN range of 2048 to 2079interface GE-WAN4/1.15233encapsulation dot1Q 212bridge-domain 152 dot1q-tunnel out-rangeno mls qos trust!...QinQ Translation Using Port-Channel Interfaces Example
The following shows a sample configuration of a QinQ link bundle that contains two GE-WAN physical interfaces. Note that the bridge-domain commands are configured on the subinterfaces of the port-channel virtual interface.
vlan internal allocation policy ascending!vlan 1, 100-1000, 2976-3008!policy-map pmap4class class-defaultset cos cos-innerpolicy-map pmap1class class-defaultshape average 4000000set cos cos-innerpolicy-map pmap2class class-defaultshape average 8000000 32000 32000policy-map pmap3class class-defaultshape average 20000000 80000 80000!!interface Port-channel1no ip addresslogging event link-statusmode dot1q-in-dot1q access-gateway!interface Port-channel1.101encapsulation dot1Q 101bridge-domain 101 dot1q 101service-policy output pmap1!interface Port-channel1.102encapsulation dot1Q 102bridge-domain 102 dot1q 102service-policy output pmap2!interface Port-channel1.103encapsulation dot1Q 103bridge-domain 103 dot1q 103!interface Port-channel1.104encapsulation dot1Q 104bridge-domain 104 dot1q 104!interface Port-channel1.201encapsulation dot1Q 201bridge-domain 201 dot1q 201!!! GigabitEthernet interfaces are not used for QinQ! link bundling, but can be used for! other purposesinterface GigabitEthernet4/1no ip addressshutdown!interface GigabitEthernet4/2no ip addressshutdown!interface GE-WAN4/1no ip addresslogging event link-statusnegotiation automls qos trust dscpchannel-group 1 mode on!interface GE-WAN4/2no ip addresslogging event link-statusnegotiation automls qos trust dscpchannel-group 1 mode on!interface GE-WAN4/3no ip addressshutdown!interface GE-WAN4/4no ip addressshutdown...
