Configuring An Egress Hierarchical Qos Policy - Cisco Catalyst 3750 Software Configuration Manual

Chapter 26 Configuring QoS
•
•
•
•
•
•
•
•
•
•

Configuring an Egress Hierarchical QoS Policy

These sections describe how to configure an egress hierarchical QoS policy to create a service policy
that is attached to an ES port.
For background information, see the
Classification Based on Traffic Classes and Traffic Policies" section on page
and Marking" section on page
section on page
Guidelines" section on page
Depending on your network configuration and QoS solution, you must perform one or more of these
tasks if you want classify, policy, mark, queue, or schedule outbound traffic:
•
•
•
78-15870-01
To configure a class map that matches an 802.1Q tunneling pair (instead of matching a single
VLAN), you must configure the class-map global configuration command with the match-all
keyword. You must enter the match vlan command before the match vlan inner command.
You cannot have match vlan {vlan-id | inner vlan-id} and match {cos cos-list | ip dscp dscp-list |
ip precedence ip-precedence-list | mpls experimental exp-list} class-map configuration commands
in the same class map.
You cannot mix VLAN-level and class-level matches within a class map.
When port trust policies are used with 802.1Q tunneling, all ports sharing the same tunnel VLAN
must be configured with the same trust policy.
Only one policy map per port is supported. You can attach one ingress service-policy per port and
one egress service-policy per ES port.
On an ES port, there is no limit to the number of egress policers.
You can define a class policy to use either tail drop through the queue-limit policy-map class
configuration command or to use WRED packet drop through the random-detect policy-map class
configuration command. You cannot use the queue-limit and random-detect commands in the same
class policy, but they can be used in two class policies in the same policy map.
You cannot use bandwidth, queue-limit, random-detect, and shape policy-map class
configuration commands with the priority policy-map class configuration command in the same
class within the same policy map. However, you can use these commands in different classes in the
same policy map. Within a policy map, you can give priority status to only one class.
You must configure the bandwidth or the shape policy-map class configuration command before
you configure either the queue-limit or the random-detect policy-map class configuration
command in a class policy. You must configure the bandwidth or the shape command in the same
policy map as the queue-limit or the random-detect command if the policy is not using the default
traffic class. If the policy is using the default traffic class, you do not need to specify the bandwidth
and shape commands in the policy map.
A policy map can have all the class bandwidths specified in either kbps or in percentages, but not a
mix of both. You cannot specify bandwidth in kbps in a child policy (configured through the
service-policy policy-map class configuration command) and then specify bandwidth as a
percentage in the parent policy.
26-26. For configuration guidelines, see the
26-76.
Classifying Egress Traffic by Using Class Maps, page 26-78
Configuring an Egress Two-Rate Traffic Policer, page 26-80
Configuring Class-Based Packet Marking in an Egress Traffic Policy, page 26-84
"Hierarchical Levels" section on page
26-24, and the "Queueing and Scheduling of Hierarchical Queues"
Catalyst 3750 Metro Switch Software Configuration Guide
Configuring Hierarchical QoS
26-20, the
26-23, the "Egress Policing
"Hierarchical QoS Configuration
(required)
(optional)
(optional)
"Egress
26-77