Information About Quality of Service on an EVC
EVC Quality of Service and the MQC
QoS functionality is typically applied using traffic classes, class maps, and policy-maps. For example, you can specify that traffic belonging to a particular class be grouped into specific categories, and receive a specific QoS treatment (such as classification or policing). The QoS treatment the traffic is to receive is specified in a policy-map and the policy-map is attached to an interface. The mechanism used for applying QoS in this manner is the modular QoS CLI (MQC.)
The policy-map can be attached to an interface in either the incoming (ingress) or outgoing (egress) direction with the service-policy command.
The MQC structure allows you to define a traffic class, create a traffic policy, and attach the traffic policy to an interface (in this case, an EVC).
The MQC structure consists of the following three high-level steps.
-
Define a traffic class by using the class-map command. A traffic class is used to classify traffic.
-
Create a traffic policy by using the policy-map command. (The terms traffic policy and policy-map are often synonymous.) A traffic policy (policy-map) contains a traffic class and one or more QoS features that will be applied to the traffic class. The QoS features in the traffic policy determine how to treat the classified traffic.
-
Attach the traffic policy (policy-map) to the interface by using the service-policy command.
Note |
For more information about the MQC, including information about hierarchical policy-maps and class maps, see the "Applying QoS Features Using the MQC" module. |
QoS-Aware Ethernet Flow Point (EFP)
As described in the EVC Quality of Service and the MQC , the MQC is used to apply one or more QoS features to network traffic. The last step in using the MQC is to attach the traffic policy (policy-map) to an interface (in this case, an EVC) by using the service-policy command.
With the EVC Quality of Service feature, the service-policy command can be used to attach the policy-map to an Ethernet Flow Point (EFP) in either the incoming (ingress) or outgoing (egress) direction of an EVC. This way, the EFP is considered to be "QoS-aware."
QoS Functionality and EVCs
The specific QoS functionality includes the following:
-
Packet classification (for example, based on differentiated services code point (DSCP) value and QoS group identifier)
-
Packet marking (for example, based on Class of Service (CoS) value)
-
Traffic policing (two- and three-color and multiple actions)
-
Bandwidth sharing
-
Priority queueing (in the outbound direction on the EVC only)
-
Weighted Random Early Detection (WRED)
The QoS functionality is enabled by using the appropriate commands listed in the following sections.
match Commands Supported by EVC QoS for Classifying Traffic
The table below lists some of the available match commands that can be used when classifying traffic on an EVC. The available match commands vary by Cisco IOS XE release. For more information about the commands and command syntax, see the Cisco IOS Quality of Service Solutions Command Reference.
Command |
Purpose |
||
---|---|---|---|
match access-group |
Configures the match criteria for a class map on the basis of the specified access control list (ACL). |
||
match any |
Configures the match criteria for all packets. |
||
match cos |
Matches a packet based on a Layer 2 CoS marking. |
||
match cos inner |
Matches the inner CoS of QinQ packets on a Layer 2 CoS marking. |
||
match [ip ] dscp |
Identifies a specific IP DSCP value as a match criterion. Up to eight DSCP values can be included in one match statement. |
||
match not |
Specifies the single match criterion value to use as an unsuccessful match criterion.
|
||
match [ip ] precedence |
Identifies IP precedence values as match criteria. |
||
match qos-group |
Identifies a specific QoS group value as a match criterion. |
||
match source-address mac |
Uses the source MAC address as a match criterion.
|
||
match vlan (QoS) |
Matches and classifies traffic on the basis of the VLAN identification number. |
||
match vlan inner |
Configures a class map to match the innermost VLAN ID in an 802.1q tagged frame. |
Multiple match Commands in One Traffic Class
If the traffic class contains more than one match command, you need to specify how to evaluate the match commands. You specify this by using either the match-any or match-all keyword of the class-map command. Note the following points about the match-any and match-all keywords:
-
If you specify the match-any keyword, the traffic being evaluated by the traffic class must match one of the specified criteria.
-
If you specify the match-all keyword, the traffic being evaluated by the traffic class must match all of the specified criteria.
-
If you do not specify either keyword, the traffic being evaluated by the traffic class must match all of the specified criteria (that is, the behavior of the match-all keyword is used).
Commands Used to Enable QoS Features on the EVC
The commands used to enable QoS features vary by Cisco IOS XE release. The table below lists some of the available commands and the QoS features that they enable. For complete command syntax, see the Cisco IOS Quality of Service Solutions Command Reference.
For more information about a specific QoS feature that you want to enable, see the appropriate module of the Cisco IOS Quality of Service Solutions Configuration Guide.
Command |
Purpose |
---|---|
bandwidth |
Configures a minimum bandwidth guarantee for a class. |
bandwidth remaining |
Configures an excess weight for a class. |
drop |
Discards the packets in the specified traffic class. |
fair-queue |
Enables the flow-based queueing feature within a traffic class. |
police |
Configures traffic policing. Allows specifying of multiple policing actions. |
police (percent) |
Configures traffic policing on the basis of a percentage of bandwidth available on an interface. |
police (two rates) |
Configures traffic policing using two rates, the committed information rate (CIR) and the peak information rate (PIR). |
priority |
Gives priority to a class of traffic belonging to a policy-map. |
queue-limit |
Specifies or modifies the maximum number of packets the queue can hold for a class configured in a policy-map. |
random-detect |
Enables Weighted Random Early Detection (WRED). |
random-detect cos-based |
Enables Weighted random early detection (WRED) on the basis of the class of service (CoS) value of a packet. |
random-detect dscp-based |
Specifies that Weighted random early detection (WRED) is to use the differentiated services code point (DSCP) value when it calculates the drop probability for a packet. |
random-detect discard-class |
Configures the WRED parameters for a discard-class value for a class in a policy-map. |
random-detect discard-class-based |
Configures WRED on the basis of the discard class value of a packet. |
random-detect exponential-weighting-constant |
Configures the exponential weight factor for the average queue size calculation for the queue reserved for a class. |
random-detect precedence |
Configure the WRED parameters for a particular IP Precedence for a class policy in a policy-map. |
service-policy |
Specifies the name of a traffic policy used as a matching criterion (for nesting traffic policies [hierarchical traffic policies] within one another). |
set cos |
Sets the Layer 2 CoS value of an outgoing packet. |
set cos-inner |
Marks the inner class of service field in a bridged frame. |
set discard-class |
Marks a packet with a discard-class value. |
set [ip ] dscp |
Marks a packet by setting the DSCP value in the type of service (ToS) byte. |
set mpls experimental |
Designates the value to which the Multiprotocol Label Switching (MPLS) bits are set if the packets match the specified policy-map. |
set precedence |
Sets the precedence value in the packet header. |
set qos-group |
Sets a QoS group identifier (ID) that can be used later to classify packets. |
shape |
Shapes traffic to the indicated bit rate according to the algorithm specified. |
input and output Keywords of the service-policy Command
As a general rule, the QoS features configured in the traffic policy can be applied to packets entering the interface or to packets leaving the interface. Therefore, when you use the service-policy command, you need to specify the direction of the traffic policy by using the input or output keyword.
For instance, the service-policy output policy-map1 command would apply the QoS features in the traffic policy to the interface in the output direction. All packets leaving the interface (output) are evaluated according to the criteria specified in the traffic policy named policy-map1.
Note |
For Cisco releases, queueing mechanisms are not supported in the input direction. Nonqueueing mechanisms (such as traffic policing and traffic marking) are supported in the input direction. Also, classifying traffic on the basis of the source MAC address (using the match source-address mac command) is supported in the input direction only. |