Table Of Contents
MQC QoS on the Cisco CMTS Routers
Finding Feature Information
Contents
Prerequisites for MQC QoS
Restrictions for MQC QoS
Information About MQC QoS
Classifying Traffic
Configuring QoS Policy Actions and Rules
Attaching Service Policies to an Interface
How to Configure MQC QoS on the Cisco CMTS Routers
Configuring Qos Features Using MQC
Configuring QoS Traffic Classes
Configuring Traffic Policies
Defining QoS Actions in a Policy Map
Set Actions
Police Actions
Queuing Actions
Attaching Service Policies
Configuring Output Rate
Configuration Examples for MQC QoS
Configuring the Traffic Class: Example
Configuring the Traffic Policy: Example
Attaching the Service Policy: Example
Verifying QoS Policy: Example
Additional References
Related Documents
Standards
MIBs
RFCs
Technical Assistance
Feature Information for MQC QoS on the Cisco CMTS Routers
MQC QoS on the Cisco CMTS Routers
First Published: December 18, 2008
Last Updated: November 23, 2009
The Modular Quality of Service Command-Line Interface (MQC) is designed to simplify the configuration of Quality of Service (QoS) on the Cisco CMTS routers by defining a common command syntax and resulting set of QoS behaviors across platforms.
Finding Feature Information
Your software release may not support all the features documented in this module. For the latest feature information and caveats, see the release notes for your platform and software release. To find information about the features documented in this module, and to see a list of the releases in which each feature is supported, see the "Feature Information for MQC QoS on the Cisco CMTS Routers" section.
Use Cisco Feature Navigator to find information about platform support and Cisco IOS, Catalyst OS, and Cisco IOS XE software image support. To access Cisco Feature Navigator, go to http://www.cisco.com/go/cfn. An account on Cisco.com is not required.
Contents
•
Prerequisites for MQC QoS
•Restrictions for MQC QoS
•Information About MQC QoS
•How to Configure MQC QoS on the Cisco CMTS Routers
•Configuration Examples for MQC QoS
•Additional References
•Feature Information for MQC QoS on the Cisco CMTS Routers
Prerequisites for MQC QoS
Table 1 shows the Cisco Cable Modem Termination System (CMTS) hardware compatibility prerequisites for this feature.
Table 1 MQC QoS Support Hardware Compatibility Matrix
CMTS Platform
|
Processor Engine
|
Cable Interface Cards
|
WAN Interface Cards
|
Cisco uBR10012 Universal Broadband Router
|
Cisco IOS Release 12.2(33)SCB
•PRE2
•PRE4
|
Cisco IOS Release 12.2(33)SCB
•Cisco uBR10-MC5X20S/U/H
|
Cisco IOS Release 12.2(33)SCB
•Cisco 10000 Series SIP-600 and Cisco 5-Port Gigabit Ethernet SPA or Cisco 1-Port 10-Gigabit Ethernet SPA
•Cisco Half-Height Gigabit Ethernet (HHGE)
|
.
Note The combination of PRE4 and Cisco Half-Height Gigabit Ethernet (HHGE) is not supported in the same chassis.
Restrictions for MQC QoS
•The sum of all priority traffic running on a given port must be less than or equal to 90 percent of the port bandwidth.
Information About MQC QoS
Quality of Service (QoS) is supported on WAN interfaces using the standard MQC. The MQC CLI structure allows you to create traffic policies and attach these policies to interfaces. A traffic policy contains a traffic class and QoS features. A traffic class is used to select traffic, while the QoS features in the traffic policy determine how to treat the classified traffic.
Classifying Traffic
The Cisco uBR10012 Universal Broadband Router must differentiate traffic before it can apply appropriate QoS actions to the traffic. You can use an MQC CLI element called a class map to define traffic classification rules or criteria.
Class maps organize data packets into specific categories called classes that can receive user-defined QoS policies. The traffic class defines the classification rules for packets received on an interface.
Configuring QoS Policy Actions and Rules
After classifying the traffic, the Cisco uBR10012 Universal Broadband Router must be configured to handle the traffic that meets the matching criteria. The MQC CLI element policy map is used to create QoS policies and configure QoS actions and rules to apply to packets that match a particular traffic class.
A policy map associates a traffic class with one or more QoS actions. While configuring a policy map, you can specify a class map name and configure the actions you want the router to take on the matching traffic. However, before creating class policies in a policy map, the class classification criteria must be configured in a class map.
Whenever you modify a class policy of a policy map, class-based weighted fair queuing (CBWFQ) is notified and new classes are installed as part of the policy map in the CBWFQ system.
Attaching Service Policies to an Interface
After creating and configuring a traffic policy, you should attach the policy to an interface. A policy can be applied to packets in either direction, inbound or outbound. An interface can have different service policies for incoming and outgoing packets.
How to Configure MQC QoS on the Cisco CMTS Routers
Note MQC support is applicable only to WAN interfaces as DOCSIS has its own QoS mechanism. However, DOCSIS QoS extends limited MQC support for cable interfaces to limit peer-to-peer (P2P) traffic.
This section describes the following required and optional procedures:
•Configuring Qos Features Using MQC (required)
•Configuring QoS Traffic Classes (required)
•Configuring Traffic Policies (required)
•Defining QoS Actions in a Policy Map (required)
•Attaching Service Policies (required)
•Configuring Output Rate (optional)
Configuring Qos Features Using MQC
To configure QoS features using the Modular QoS CLI , complete the following basic steps:
Step 1 Define a traffic class using the class-map command.
Step 2 Create a traffic policy by associating the traffic class with QoS features using the policy-map command.
Step 3 Attach the traffic policy to the interface using the service-policy command and specify whether the policy has to be applied to inbound or outbound traffic.
Each of the above-mentioned steps is accomplished using a user interface command. Specifically, the three steps are accomplished through the use of three abstractions, class map, policy map, and service policy.
Note Service policies are applied to Gigabit Ethernet, Ten Gigabit Ethernet, 802.1Q VLAN subinterfaces, and tunnel interfaces. Tunnel interfaces are virtual interfaces without queues, and service policies applied to tunnels cannot contain queuing actions. The Cisco uBR10012 Universal Broadband Router does not support per-subinterface queues for VLAN subinterfaces. However, the VLANs share the main interface queues.
For more information about MQC, refer to the "Configuring the Modular Quality of Service Command-Line Interface" chapter of the Cisco IOS Quality of Service Solutions Configuration Guide, Release 12.2 document.
Note Though MQC is not broadly supported on cable interfaces as most subscriber queue configuration is controlled by parameters in the cable modem configuration file, a subset of MQC is supported on cable interfaces. This allows multiple service operators (MSOs) to classify P2P traffic based on type of service (ToS) bits and send it to a shaped queue. The P2P traffic control feature can configure shape and queue-limit actions on the P2P traffic control policy map. The type of service P2P is supported only on legacy cable interfaces and not on Wideband or modular cable (MC) interfaces.
Configuring QoS Traffic Classes
The class map command is used to create a traffic class. A traffic class contains three major elements: a name, a series of match commands, and, if more than one match command exists in the traffic class, an instruction on how to evaluate these match commands.
The match commands are used to specify various criteria for classifying packets. Packets are checked to determine whether they match the criteria specified in the match commands; if a packet matches the specified criteria, that packet is considered a member of the class and is forwarded according to the QoS specifications set in the traffic policy. Packets that fail to meet any of the matching criteria are classified as members of the default traffic class.
For more information about the default traffic class, refer to the "Configuring the Modular Quality of Service Command-Line Interface" chapter of the Cisco IOS Quality of Service Solutions Configuration Guide, Release 12.2 document.
SUMMARY STEPS
1. enable
2. configure terminal
3. class-map [match-all | match-any] class-name
4. match type
DETAILED STEPS
| |
Command or Action
|
Purpose
|
Step 1
|
enable
Example:
Router> enable
|
Enables privileged EXEC mode.
•Enter your password if prompted.
|
Step 2
|
configure terminal
Example:
Router# configure terminal
|
Enters global configuration mode.
|
Step 3
|
class-map [match-all | match-any] class-name
Example:
Router(config)# class-map class1
|
Creates a class to be used with a class map, and enters class-map configuration mode. The class map is used for matching packets to the specified class.
•match-all—(Optional) Specifies that all match criteria in the class map must be matched, using a logical AND of all matching statements defined under the class. This is the default.
•match-any—(Optional) Specifies that one or more match criteria must match, using a logical OR of all matching statements defined under the class.
•class-name—User-defined name of the class.
|
Step 4
|
match type
Example:
Router(config-cmap)# match access-group 101
|
Specifies the matching criterion to be applied to the traffic, where type represents one of the forms of the match command.
Table 2 lists the match options supported on the class-map command.
|
Table 2 Match Options Supported on the MQC QoS
Command
|
Purpose
|
match access-group {number | name}
|
Specifies that the packet must be permitted by the specified access control list (ACL).
•number—ACL identifier applied to an interface. Valid values are from 1 to 2699.
•name—Packet with the indicated name must be permitted by the access list. The name can be a maximum of 40 alphanumeric characters.
|
match-all
|
Specifies that the packet must match all of the matching criteria defined for a class map.
|
match-any
|
Specifies that the packet must match at least one of the matching criteria defined for a class map.
|
match not criteria
|
Specifies that the packet must not match this particular matching criterion value.
•criteria—Match criterion value that should be an unsuccessful match criteria. All other values of the specified match criterion are considered successful match criteria.
|
match input-interface name
|
Specifies that the packet input interface must match the interface name.
Note Matching is supported for cable bundles but not for physical cable interfaces.
|
match ip dscp {ip-dscp-value | afxy | csx | ef | default}
|
Specifies that the packet IP differentiated service code point (DSCP) value must match one or more of the specified attributes.
•ip-dscp-value—DSCP value to match. Valid values are from 0 to 63. You can specify up to 8 code point values, using a space to separate consecutive values.
Instead of specifying a numeric ip-dscp-value, you can specify one of the following reserved keywords:
•afxy—Indicates assured forwarding points. The first number (x) indicates the AF class. Valid values are from 1 to 4. The second number (y) indicates the level of drop preference within each class. Valid values are from 1 (low drop) to 3 (high drop).
•csx—Indicates class selector code points that are backward-compatible with IP precedence. Valid values for x are from 1 to 7. The CS code points (CS1 through CS7) are identical to IP precedence values from 1 to 7.
•ef—Indicates expedited forwarding.
•default—Indicates best effort or DSCP 0.
|
match ip precedence {ip-precedence-value | precedence-name}
|
Specifies that the packet IP precedence value must match one or more precedence values or the name of the precedence.
•ip-precedence-value—IP precedence value to match. Valid values are from 0 to 7. You can specify up to 8 precedence values, using a space to separate consecutive values.
•precedence-name—Name of the IP precedence value.
|
match ip rtp {lowest-udp-port range}
|
Specifies that the packet with even-numbered UDP port value must be within the specified range of port numbers. Only even-numbered ports are matched because they carry the real-time data streams. Odd-numbered ports are not matched because they only carry control information.
•lowest-udp-port—Number specified from 0 to 65535 and is the lowest number in the range.
•range—Number specified from 0 to 65535 and is the highest number in the range.
|
match mpls experimental topmost value
|
Matches the experimental (EXP) value in the topmost label.
•value—Value to which you want to set the MPLS EXP bits in the topmost label header. Valid values are from 0 to 7.
|
match qos-group number
|
Specifies that the packet QoS group number value must match the specified QoS group number.
•number—Group number specified from 0 to 99.
|
Configuring Traffic Policies
After creating traffic classes, you can configure traffic policies to configure marking features to apply certain actions to the selected traffic in those classes.
The policy-map command is used to create a traffic policy. The purpose of a traffic policy is to configure the QoS features that should be associated with the traffic that has been classified in a user-specified traffic class.
Note A packet can match only one traffic class within a traffic policy. If a packet matches more than one traffic class in the traffic policy, the first traffic class defined in the policy will be used.
SUMMARY STEPS
1. enable
2. configure terminal
3. policy-map policy-map-name
4. class {class-name | class-default}
DETAILED STEPS
| |
Command or Action
|
Purpose
|
Step 1
|
enable
Example:
Router> enable
|
Enables privileged EXEC mode.
•Enter your password if prompted.
|
Step 2
|
configure terminal
Example:
Router# configure terminal
|
Enters global configuration mode.
|
Step 3
|
policy-map policy-map-name
Example:
Router(config)# policy-map policy9
|
Creates or modifies a traffic policy and enters policy map configuration mode, where:
•policy-map-name—Name of the traffic policy to configure. Names can be a maximum of 40 alphanumeric characters.
|
Step 4
|
class {class-name | class-default}
Example:
Router(config-pmap)# class class1
|
Specifies the name of the traffic class to which this policy applies and enters policy-map class configuration mode, where:
•class-name—Policy applied to a user-defined class name previously configured.
•class-default—Specifies that the policy applies to the default traffic class.
|
Defining QoS Actions in a Policy Map
Action commands can be added from within class mode on a policy map. Action commands fall into three general categories as given below:
•Set Actions
•Police Actions
•Queuing Actions
Set Actions
Set commands allow traffic to be marked such that other network devices along the forwarding path can quickly determine the proper class of service to apply to a traffic flow. Set commands can be applied to both input and output policy maps.
Table 3 lists the set options supported on the Cisco uBR10012 Universal Broadband Router.
Table 3 Set Options Supported on the MQC QoS
Command
|
Purpose
|
set ip dscp {ip-dscp-value | afxy | csx | ef | default}
|
Marks a packet with the differentiated services code point (DSCP) you specify. Valid values are from 0 to 63.
Instead of specifying a numeric ip-dscp-value, you can specify one of the following reserved keywords:
•afxy—Indicates assured forwarding points. The first number (x) indicates the AF class. Valid values are from 1 to 4. The second number (y) indicates the level of drop preference within each class. Valid values are from 1 (low drop) to 3 (high drop).
•csx—Indicates class selector code points that are backward-compatible with IP precedence. Valid values for x are from 1 to 7. The CS code points (CS1 through CS7) are identical to IP precedence values from 1 to 7.
•ef—Indicates expedited forwarding.
•default—Indicates best effort or DSCP 0.
|
set ip precedence {precedence-value}
|
Marks a packet with the IP precedence level you specify. Valid values are from 0 to 7.
|
set qos group group-id
|
Marks a packet with the QoS group identifier you specify. Valid values are from 0 to 99.
|
Police Actions
Traffic policing is a traffic regulation mechanism that is used to limit the rate of traffic streams. Policing allows you to control the maximum rate of traffic sent or received on an interface. Policing propagates bursts of traffic and is applied to the inbound or outbound traffic on an interface. When the traffic rate exceeds the configured maximum rate, policing drops or remarks the excess traffic. Although policing does not buffer excess traffic, in the output direction, a configured queuing mechanism applies to conforming packets that might need to be queued while waiting to be serialized at the physical interface.
Traffic policing uses a token bucket algorithm to manage the maximum rate of traffic. This algorithm is used to define the maximum rate of traffic allowed on an interface at a given moment in time. The algorithm puts tokens into the bucket at a certain rate. Each token is permission for the source to send a specific number of bits into the network. With policing, the token bucket determines whether a packet exceeds or conforms to the applied rate. In either case, policing implements the action you configure such as setting the IP precedence or differentiated services code point (DSCP).
To configure traffic policing based on bits per second, use the police command in policy-map class configuration mode.
SUMMARY STEPS
1. enable
2. configure terminal
3. policy-map [name]
4. class [name]
5. police [bps] [burst-normal ] [burst-excess] conform [conform-action] exceed [exceed-action]
DETAILED STEPS
| |
Command or Action
|
Purpose
|
Step 1
|
enable
Example:
Router> enable
|
Enables privileged EXEC mode.
•Enter your password if prompted.
|
Step 2
|
configure terminal
Example:
Router# configure terminal
|
Enters global configuration mode.
|
Step 3
|
policy-map [name]
Example:
Router(config)# policy-map policy9
|
Specifies the traffic policy and enters policy-map configuration mode.
|
Step 4
|
class [name]
Example:
Router(config-pmap)# class class1
|
Specifies the name of the traffic class to which this policy applies and enters policy-map class configuration mode.
|
Step 5
|
police [bps] [burst-normal] [burst-excess] conform
[conform-action] exceed [exceed-action]
Example:
Router(config-pmap-c)# police 10000000 15000 20000
conform transmit exceed drop
|
Configures traffic policing based on bits per second.
•bps—(Optional) Average rate in bits per second (bps). Valid values are from 8,000 to 2,488,320,000 bps. If you only specify police bps, the router transmits the traffic that conforms to the bps value and drops the traffic that exceeds the bps value.
•burst-normal—(Optional) Normal or committed burst size used by the first token bucket for policing. The burst-normal option specifies the committed burst in bytes. Valid values are from 1 to 512,000,000. The default is 9,216 bytes.
•burst-excess—(Optional) Excess burst size used by the second token bucket for policing. The burst-excess option specifies the excess burst in bytes. Valid values are from 0 to 1,024,000,000 bytes. The default is 0. You must specify burst-normal before you specify burst-excess.
Note When the burst-excess value equals 0, we recommend that you set the egress burst-normal value to be greater than or equal to the ingress burst-normal value plus 1. Otherwise, packet loss can occur. For example: burst-excess = 0; egress burst-normal >= ingress burst-normal + 1.
•conform-action—Action to take on packets that conform to the rate limit. The default action is transmit. You must specify burst-excess before you specify conform.
•exceed-action—Action to take on packets that exceed the rate limit. The default action is drop. You must specify conform before you specify exceed.
|
Queuing Actions
When queuing actions are applied to a given class within a policy map, they either cause queues to be created for that particular class of traffic or control how the queues are managed. Queuing commands are valid only in the output direction.
The Cisco uBR10012 Universal Broadband Router supports the MQC policy maps for class queue creation on WAN interfaces.
The following two types of queues are supported through MQC:
•Priority queues—Used mainly for voice traffic. They are policed at their individual committed information rate (CIR) to limit their bandwidth to the subscribed level. Only one priority queue is allowed per logical interface.
•Class queues—Implemented as best effort queues. They are based on a specified bandwidth in Kbps and shaped using the "bandwidth" policy map action. Generally, the specified bandwidth is not guaranteed.
Weighted random early detection (WRED) is a mechanism for controlling congestion of queues. WRED combines the capabilities of the random early detection (RED) mechanism with IP precedence, DSCP, and discard class to provide preferential handling of higher priority packets. For additional information on WRED, refer to the Cisco IOS Quality of Service Solutions Configuration Guide, Release 12.2.
Note Cisco IOS Release 12.2(33)SCB does not support random-detect for type of service (ToS) peer-to-peer (P2P) policy maps.
Table 4 lists the queuing actions supported on the Cisco uBR10012 Universal Broadband Router.
Table 4 Queuing Actions Supported on the MQC QoS
Command
|
Purpose
|
priority
|
Assigns priority to the class you specified and reserves a priority queue for class-based weighted fair queuing (CBWFQ) traffic.
The priority command does not have any arguments. You must use the police command to specify a guaranteed bandwidth.
|
queue-limit number-of-packets
|
Specifies or modifies the maximum number of packets that a particular class queue can hold.
|
random-detect dscp-based
|
Configures WRED to drop packets based on a DSCP value.
|
random-detect precedence-based
|
Configures WRED to drop packets based on an IP precedence value.
|
random-detect dscp dscp-values sub-class-val1 [...[sub-class-val8]]minimum-thresh min-thresh-value maximum-thresh max-thresh-value mark-prob mark-prob-value
|
Configures the minimum and maximum packet thresholds for the differentiated services code point (DSCP) value.
•dscp-values—DSCP value. The DSCP value can be a number from 0 to 63.
•min-thresh-value—Minimum threshold in number of packets. The value range of this argument is from 1 to 4096.
•max-thresh-value—Maximum threshold in number of packets. The value range of this argument is from the value of the min-thresh-value argument to 4096.
•max-prob-value—Specifies the fraction of packets dropped when the average queue depth is at the maximum threshold.
|
random-detect precedence values sub-class-val1 [...[sub-class-val8]] minimum-thresh min-thresh-value maximum-thresh max-thresh-value mark-prob mark-prob-value
|
Configures WRED and distributed WRED (DWRED) parameters for a particular IP Precedence. Valid values are from 0 to 7. Typically, 0 represents low priority traffic that can be aggressively managed (dropped) and 7 represents high priority traffic.
•min-thresh-value—Minimum threshold in number of packets. The value range of this argument is from 1 to 4096.
•max-thresh-value—Maximum threshold in number of packets. The value range of this argument is from the value of the min-thresh-value argument to 4096.
•max-prob-value—Fraction of packets dropped when the average queue depth is at the maximum threshold.
|
shape [average] cir
|
Shapes traffic to the rate you specify, or shapes traffic based on the percentage of available bandwidth you specify.
•average—Specifies the committed burst (Bc) that specifies the maximum number of bits sent out in each interval.
•cir—Committed information rate (CIR), in bits per second (bps).
|
bandwidth {bandwidth-kbps | percent percentage | remaining percent percentage}
|
Specifies or modifies the minimum bandwidth allocated for a traffic class in a policy map.
•bandwidth-kbps—Minimum bandwidth allocated for a class belonging to a policy map. Accepted input values are from 8 to 10,000,000,000 although the maximum value entered should not be larger than the link bandwidth of the slowest interface to which the policy will be applied.
•percent percentage—Specifies or modifies the minimum percentage of the link bandwidth allocated for a class belonging to a policy map. Valid values are from 1 to 100.
•remaining percent percentage—Specifies or modifies the minimum percentage of unused link bandwidth allocated for a class belonging to a policy map. Valid values are from 1 to 100.
Note Configure the amount of bandwidth large enough to also accommodate Layer 2 overhead.
|
Attaching Service Policies
The service-policy command is used to attach the traffic policy, as specified with the policy-map command, to an interface. Because the elements of the traffic policy can be applied to packets entering and leaving the interface, it is essential to specify whether the traffic policy characteristics should be applied to incoming or outgoing packets.
To attach a policy map that the router can use to apply QoS policies to inbound and outbound packets, use the service-policy command in interface or map class configuration mode.
SUMMARY STEPS
1. enable
2. configure terminal
3. interface interface-name
4. service-policy {input | output} policy-map-name
| |
Command or Action
|
Purpose
|
Step 1
|
enable
Example:
Router> enable
|
Enables privileged EXEC mode.
•Enter your password if prompted.
|
Step 2
|
configure terminal
Example:
Router# configure terminal
|
Enters global configuration mode.
|
Step 3
|
interface interface-name
Example:
Router(config)# interface GigabitEthernet 3/0/0
|
Specifies the interface and enters interface configuration mode.
|
Step 4
|
Router(config-if)# service-policy {input | output}
policy-map-name
Example:
Router(config-if)# service-policy output policy1
|
Specifies a policy map that the router can use to apply QoS policies to inbound or outbound packets.
•input—Applies the QoS policy to inbound packets.
•output—Applies the QoS policy to outbound packets.
•policy-map-name—Name of the policy map (created using the policy-map command) you want to attach. The policy-map-name can be a maximum of 40 alphanumeric characters.
|
DETAILED STEPS
Configuring Output Rate
To restrict the WAN interface bandwidth output rate to a smaller value than that of the physical link bandwidth, use the output-rate command in interface configuration mode.
Note The output-rate command is valid only for Gigabit Ethernet interfaces. This command was introduced in Cisco IOS Release 12.2(33)SCC.
SUMMARY STEPS
1. enable
2. configure terminal
3. interface interface-name
4. output-rate rate
DETAILED STEPS
| |
Command or Action
|
Purpose
|
Step 1
|
enable
Example:
Router> enable
|
Enables privileged EXEC mode.
•Enter your password if prompted.
|
Step 2
|
configure terminal
Example:
Router# configure terminal
|
Enters global configuration mode.
|
Step 3
|
interface interface-name
Example:
Router(config)# interface GigabitEthernet 3/0/0
|
Specifies the interface and enters interface configuration mode.
|
Step 4
|
Router(config-if)# output-rate rate
Example:
Router(config-if)# output-rate 100
|
Specifies a custom-defined output rate to a WAN interface instead of the default line rate.
•rate—Output rate defined for the WAN interface, in kilobits per second. Valid values range from 1 to 1,000,000.
|
Configuration Examples for MQC QoS
This section provides the following configuration examples:
•Configuring the Traffic Class: Example
•Configuring the Traffic Policy: Example
•Attaching the Service Policy: Example
•Verifying QoS Policy: Example
Configuring the Traffic Class: Example
In the following example, two traffic classes are created and their match criteria are defined. For the first traffic class called class1, access control list (ACL) 101 is used as the match criterion. For the second traffic class called class2, ACL 102 is used as the match criterion. Packets are checked against the contents of these ACLs to determine if they belong to the class.
Router(config)# class-map class1
Router(config-cmap)# match access-group 101
Router(config-cmap)# exit
Router(config)# class-map class2
Router(config-cmap)# match access-group 102
Router(config-cmap)# exit
Configuring the Traffic Policy: Example
In the following example, a traffic policy called policy1 is defined to contain policy specifications for class1.
Router(config)# policy-map policy1
Router(config-pmap)# class class1
Router(config-pmap-c)# bandwidth 3000
Router(config-pmap-c)# queue-limit 30
Router(config-pmap)# exit
Attaching the Service Policy: Example
The following example shows how to attach an existing traffic policy to an interface. After you define a traffic policy with the policy-map command, you can attach it to one or more interfaces by using the service-policy command in interface configuration mode. Although you can assign the same traffic policy to multiple interfaces, each interface can have only one traffic policy attached at the input and only one traffic policy attached at the output.
Router(config)# interface GigabitEthernet 3/0/0
Router(config-if)# service-policy output policy1
Verifying QoS Policy: Example
To verify a policy map configuration, enter any of the following commands in privileged EXEC mode:.
Router# show policy-map policy-map-name class class-name
packet-based wred, exponential weight 9
random-detect precedence values 2 minimum-thresh 1024 maximum-thresh 20481
Router# show policy-map interface [type number]{input | output} class class-name
Additional References
The following sections provide references related to the MQC QoS feature.
Related Documents
Standards
Standard
|
Title
|
No new or modified standards are supported by this feature, and support for existing standards has not been modified by this feature.
|
—
|
MIBs
MIB
|
MIBs Link
|
•No new or modified MIBs are supported by this feature, and support for existing MIBs has not been modified by this feature.
|
To locate and download MIBs for selected platforms, Cisco IOS releases, and feature sets, use Cisco MIB Locator found at the following URL:
http://www.cisco.com/go/mibs
|
RFCs
RFC
|
Title
|
No new or modified RFCs are supported by this feature, and support for existing RFCs has not been modified by this feature.
|
—
|
Technical Assistance
Description
|
Link
|
The Cisco Support website provides extensive online resources, including documentation and tools for troubleshooting and resolving technical issues with Cisco products and technologies.
To receive security and technical information about your products, you can subscribe to various services, such as the Product Alert Tool (accessed from Field Notices), the Cisco Technical Services Newsletter, and Really Simple Syndication (RSS) Feeds.
Access to most tools on the Cisco Support website requires a Cisco.com user ID and password.
|
http://www.cisco.com/support
|
Feature Information for MQC QoS on the Cisco CMTS Routers
Table 5 lists the features in this module and provides links to specific configuration information. Only features that were introduced or modified in Cisco IOS Release 12.2(33)SCB or a later release appear in the table.
Not all commands may be available in your Cisco IOS software release. For release information about a specific command, see the command reference documentation.
Use Cisco Feature Navigator to find information about platform support and software image support. Cisco Feature Navigator enables you to determine which Cisco IOS, Catalyst OS, and Cisco IOS XE software images support a specific software release, feature set, or platform. To access Cisco Feature Navigator, go to http://www.cisco.com/go/cfn. An account on Cisco.com is not required.
Note Table 5 lists only the Cisco IOS software release that introduced support for a given feature in a given Cisco IOS software release. Unless noted otherwise, subsequent releases of that Cisco IOS software release also support that feature.
Table 5 Feature Information for MQC QoS on the Cisco CMTS Routers
Feature Name
|
Releases
|
Feature Information
|
MQC QoS on the Cisco CMTS Routers
|
12.2(33)SCB
12.2(33)SCC
|
MQC simplifies the configuration of QoS on the Cisco CMTS routers by defining a common command syntax and resulting set of QoS behaviors across platforms.
Cisco IOS Release 12.2(33)SCC introduces the output-rate command to limit the upstream bandwidth output rate to a smaller number than that of the physical link bandwidth.
The following command was introduced: output-rate
|
CCDE, CCENT, CCSI, Cisco Eos, Cisco HealthPresence, Cisco IronPort, the Cisco logo, Cisco Nurse Connect, Cisco Pulse, Cisco SensorBase, Cisco StackPower, Cisco StadiumVision, Cisco TelePresence, Cisco Unified Computing System, Cisco WebEx, DCE, Flip Channels, Flip for Good, Flip Mino, Flipshare (Design), Flip Ultra, Flip Video, Flip Video (Design), Instant Broadband, and Welcome to the Human Network are trademarks; Changing the Way We Work, Live, Play, and Learn, Cisco Capital, Cisco Capital (Design), Cisco:Financed (Stylized), Cisco Store, Flip Gift Card, and One Million Acts of Green are service marks; and Access Registrar, Aironet, AllTouch, AsyncOS, Bringing the Meeting To You, Catalyst, CCDA, CCDP, CCIE, CCIP, CCNA, CCNP, CCSP, CCVP, Cisco, the Cisco Certified Internetwork Expert logo, Cisco IOS, Cisco Lumin, Cisco Nexus, Cisco Press, Cisco Systems, Cisco Systems Capital, the Cisco Systems logo, Cisco Unity, Collaboration Without Limitation, Continuum, EtherFast, EtherSwitch, Event Center, Explorer, Follow Me Browsing, GainMaker, iLYNX, IOS, iPhone, IronPort, the IronPort logo, Laser Link, LightStream, Linksys, MeetingPlace, MeetingPlace Chime Sound, MGX, Networkers, Networking Academy, PCNow, PIX, PowerKEY, PowerPanels, PowerTV, PowerTV (Design), PowerVu, Prisma, ProConnect, ROSA, SenderBase, SMARTnet, Spectrum Expert, StackWise, WebEx, and the WebEx logo are registered trademarks of Cisco Systems, Inc. and/or its affiliates in the United States and certain other countries.
All other trademarks mentioned in this document or website are the property of their respective owners. The use of the word partner does not imply a partnership relationship between Cisco and any other company. (0910R)
Any Internet Protocol (IP) addresses used in this document are not intended to be actual addresses. Any examples, command display output, and figures included in the document are shown for illustrative purposes only. Any use of actual IP addresses in illustrative content is unintentional and coincidental.
© 2009 Cisco Systems, Inc. All rights reserved.
