Cisco Systems ASA5515K9, ASA 5500 Configuring the Service Rule

54-13
Cisco ASA 5500 Series Configuration Guide using the CLI
Chapter54 Configuring QoS
Configuring QoS
Restrictions
•For hierarchical priority queuing, for encrypted VPN traffic, you can only match traffic based on the
DSCP or precedence setting; you cannot match a tunnel group.
•For hierarchical priority queuing, IPsec-over-TCP traffic is not supported.
Detailed Steps
Configuring the Service Rule
To configure traffic shaping and optional hiearchical priority queuing, perform the following steps.
Restrictions
•Traffic shaping is not supported on the multi-processor models.
•For traffic shaping, you can only use the class-default class map, which is automatically created by
the ASA, and which matches all traffic.
•You cannot configure traffic shaping and standard priority queuing for the same interface; only
hierarchical priority queuing is allowed. See the “How QoS Features Interact” section on page 54-4
for information about valid QoS configurations.
•You cannot configure traffic shaping in the global policy.
Command Purpose
Step1 class-map priority_map_name
Example:
hostname(config)# class-map
priority_traffic
For hierarchical priority queuing, creates a class map to identify
the traffic for which you want to perform priority queuing.
Step2 match parameter
Example:
hostname(config-cmap)# match access-list
priority
Specifies the traffic in the class map. See the “Identifying Traffic
(Layer 3/4 Class Maps)” section on page 32-12 for more
information. For encrypted VPN traffic, you can only match
traffic based on the DSCP or precedence setting; you cannot
match a tunnel group.
Step3 policy-map priority_map_name
Example:
hostname(config)# policy-map
priority-sub-policy
Creates a policy map.
Step4 class priority_map_name
Example:
hostname(config-pmap)# class
priority-sub-map
Specifies the class map you created in Step 1.
Step5 priority
Example:
hostname(config-pmap-c)# priority
Applies the priority queuing action to a class map.
Note This policy has not yet been activated. You must activate
it as part of the shaping policy. See the “Configuring the
Service Rule” section on page54-13.