Cisco Cisco ME 3400EG-2CS-A Switch
Americas Headquarters:
Cisco Systems, Inc., 170 West Tasman Drive, San Jose, CA 95134-1706 USA
Cisco Systems, Inc., 170 West Tasman Drive, San Jose, CA 95134-1706 USA
Configuring ME 3400E QoS Classification for
QinQ-Based Service, Release 12.2(53)SE
QinQ-Based Service, Release 12.2(53)SE
December 15, 2009
An ME 3400E switch supports port-based 802.1Q tunneling (QinQ) on tunnel or trunk ports and
selective (VLAN-based) QinQ on trunk ports. This enhancement in Cisco IOS Release 12.2(53)SE
allows you to apply an ingress QoS classification on the customer packet that is tunneled into a
service-provider 802.1Q tag (S-tag) and on the imposed S-tag on the QinQ port.
selective (VLAN-based) QinQ on trunk ports. This enhancement in Cisco IOS Release 12.2(53)SE
allows you to apply an ingress QoS classification on the customer packet that is tunneled into a
service-provider 802.1Q tag (S-tag) and on the imposed S-tag on the QinQ port.
You can classify on the customer packet tunneled into the S-tag based on the customer VLAN-ID
(C-VLAN), the customer class of service (CoS) priority (C-CoS), the customer DSCP priority
(C-DSCP), or multifield parameters (MAC-ACL and IP-ACL) in the incoming packet. You can also
classify on the S-tag based on the service-provider VLAN (S-VLAN) or the service-provider CoS
priority (S-CoS) of the packet.
(C-VLAN), the customer class of service (CoS) priority (C-CoS), the customer DSCP priority
(C-DSCP), or multifield parameters (MAC-ACL and IP-ACL) in the incoming packet. You can also
classify on the S-tag based on the service-provider VLAN (S-VLAN) or the service-provider CoS
priority (S-CoS) of the packet.
As with any QoS classification, you create a class map by entering the class-map global configuration
command and enter class-map configuration mode, where you use the match command to define the
match criteria for the traffic. The incoming packets are compared to the class match criteria; packets
matching the criteria are part of the class and are forwarded according to the QoS specifications in the
traffic policy.
command and enter class-map configuration mode, where you use the match command to define the
match criteria for the traffic. The incoming packets are compared to the class match criteria; packets
matching the criteria are part of the class and are forwarded according to the QoS specifications in the
traffic policy.
After classification, you can apply the ingress QoS functions of policing and marking to these packets.
You create and name a policy map by using the policy-map global configuration command, naming the
traffic class associated with the traffic policy, and specifying the action to take on all traffic in the class.
You use the service-policy interface configuration command to attach the traffic policy to the port on
which QinQ is configured.
You create and name a policy map by using the policy-map global configuration command, naming the
traffic class associated with the traffic policy, and specifying the action to take on all traffic in the class.
You use the service-policy interface configuration command to attach the traffic policy to the port on
which QinQ is configured.
Note
This document covers only configuration with commands for the QoS classification enhancement for
QinQ. For all other information about QoS or tunneling, refer to the ME 3400E Software Configuration
Guide for Cisco IOS Release 12.2(52)SE:
QinQ. For all other information about QoS or tunneling, refer to the ME 3400E Software Configuration
Guide for Cisco IOS Release 12.2(52)SE: