Creating Attribute-Based Qos (Easyqos) Policy - Cisco Catalyst 9500 Manual
Hide thumbs
Also See for Catalyst 9500:
- Manual (360 pages) ,
- Configuration manual (223 pages) ,
- Hardware installation manual (122 pages)
Table of Contents
Advertisement
Configuring Application Visibility and Control in a Wired Network
DETAILED STEPS
Command or Action
Step 1
configure terminal
Example:
Device# configure terminal
Step 2
interface interface-id
Example:
Device(config)# interface Gigabitethernet 1/0/1
Step 3
service-policy input policymapname
Example:
Device(config-if)# service-policy input MARKING_IN
Step 4
end
Example:
Device(config)# end
Creating Attribute-based QoS (EasyQoS) Policy
Legacy wired AVC QoS defines classes based on specific NBAR protocols using the command match protocol
nbar-protocol-name. This requires explicitly defining match statements and hence TCAM entries per relevant
protocol. The number of match statements per class is limited, and specifically that the overall number of
protocols that may be matched is limited to 255. These limitations in addition to the fact that relevant supported
protocols might change between protocol pack releases, further jeopardizes the usefulness of QoS which is
based on specific NBAR protocols.
To accommodate practically equivalent functionality, a much more useful and efficient, QoS NBAR defines
a set of attributes that each protocol is classified to (with defaults, which may be overwritten in CLI as described
further in this chapter), e.g. business-relevance and traffic-class. QoS classes and policies may be defined
based on such general NBAR attributes instead of specific protocols.
Starting with Cisco IOS XE Fuji 16.8.1a, support for defining QoS classes and policies based on such NBAR
attributes is available, with a few limitations.
A class map can be defined according to certain NBAR attributes, using match-all or match-any, and a
policy-map can be defined based on such a class-map. This policy-map can be attached to wired ports. Such
classes and policies may be intermixed with other legacy match operations (e.g. packet fields, ACLs, etc.).
Following are the limitations for defining class maps and policy maps.
Creating a Class Map
SUMMARY STEPS
1. configure terminal
2. [no] class-map {match-all | match-any }
3. match protocol attribute attribute-type attribute-value
4. end
System Management Configuration Guide, Cisco IOS XE Fuji 16.8.x (Catalyst 9500 Switches)
Creating Attribute-based QoS (EasyQoS) Policy
Purpose
Enters global configuration mode.
Enters the interface configuration mode.
Applies local policy to interface.
Returns to privileged EXEC mode. Alternatively, you can
also press Ctrl-Z to exit global configuration mode.
115
Hide quick links:
Advertisement
Table of Contents
