Table Of Contents
Quality of Service Commands on Cisco IOS XR Software
hw-module qos account layer2 encapsulation
hw-module qos multicast priorityq disable
hw-module qos queue-auto-defrag
match mpls experimental topmost
service-policy (policy map class)
Quality of Service Commands on Cisco IOS XR Software
This chapter lists QoS commands in alphabetical order. For detailed information about QoS concepts, configuration tasks, and examples, see Cisco IOS XR Modular Quality of Service Configuration Guide.
bandwidth (QoS)
To specify the minimum bandwidth allocated to a class belonging to a policy map, use the bandwidth command in policy map class configuration mode. To remove the bandwidth specified for a class, use the no form of this command.
bandwidth {rate [units] | percent percentage}
no bandwidth {rate [units] | percent percentage}
Syntax Description
Defaults
The default units is kbps.
Command Modes
Policy map class configuration
Command History
Usage Guidelines
To use this command, you must be in a user group associated with a task group that includes the proper task IDs. For detailed information about user groups and task IDs, see the Configuring AAA Services on Cisco IOS XR Software module of the Cisco IOS XR System Security Configuration Guide.
The bandwidth command is used to specify the minimum guaranteed bandwidth allocated for traffic matching a particular class. Bandwidth may be defined as a specific value or may be set as a percentage of the interface bandwidth.
Note
On the Cisco CRS-1, by default, and without any QoS configuration, the default group of an interface is allowed a minimum bandwidth of either 1 percent of the interface rate or 10 mbps. This is applicable only on the egress.
The actual bandwidth used is calculated in multiples of 256 kbps, the minimum bandwidth rate. The configured value is rounded to the nearest multiple of 256 kbps. The value shown in the output of the running-configuration shows the configured value as entered by the user.
If a percentage value is set, the accuracy that can be expected is 1 percent.
The bandwidth command can be used only within egress service policies. Use within an ingress policy is not supported.
Note
Be careful when specifying bandwidth guarantees close to 100 percent, because the Layer 2 encapsulation considered does not include the entire Layer 2 header. This can lead to oversubscription, particularly in the case of small packet sizes.
For bundled interfaces, bandwidth can be configured only as a percentage.
A policy map can have a single bandwidth statement per class. Both percentage and actual value bandwidth configurations can be used within a policy map.
The bandwidth command does not specify how the bandwidth is to be shared. Instead it specifies how much bandwidth is guaranteed per class, by setting the number of tokens that are assigned to the token bucket of a particular class. For configured behavior to work correctly, you must ensure that the sum of the bandwidths plus any priority traffic is not greater than the bandwidth of the interface itself. If the interface is oversubscribed, unpredictable behavior results.
The bandwidth of the interface is set to be that of the physical interface, unless a hierarchical policy is defined that reduces the bandwidth available to the traffic. The following example shows a hierarchical policy being used to shape traffic to the specified value. The child policy then determines how the shaped bandwidth should be apportioned between the specified classes:
policy-map parentclass match_allshape average 1000000bandwidth 1000000service-policy childpolicy-map childclass goldbandwidth percent 20class silverbandwidth percent 40class defaultbandwidth percent 40
Note
For main interface service policies:
•
•
Implicit bandwidth remaining is an equal share of unallocated bandwidth among all queuing classes without either bandwidth or bandwidth remaining actions.
For subinterface policies:
•
•
•
In the following example, the hierarchical policy is attached to the main interface, and the parent classes are a mix of bandwidth and shape only classes:
policy-map hqosclass c1bandwidth percent 40service-policy childclass c2shape average 500000000service-policy childThe reference for the child policy in class c2 is the implicit bandwidth of class c2 bounded by the shape rate of class c2. Therefore, the reference = (60% * interface bandwidth) / 3 bounded by 500000000 kbps.
In the following example, the hierarchical policy is a class-default only parent shape configured on subinterfaces:
policy-map sub_int_hqosclass c1ass-defaultshape average 40service-policy childThe class-default parent shape rate is used as reference.
When the percent keyword is used with the bandwidth command, the bandwidth of the interface is defined as being the Layer 2 capacity excluding the POS/GE encapsulation but including the HDLC flags, FCS, and so on. These have to be included because they are applied per packet, and the system cannot predict how many packets of a particular packet size are being sent out.
For example, the following policy is applied to an OC-192 interface:
policy-map oc-192class c1bandwidth percent 50The resulting bandwidth reservation for class c1 is 4,792,320 kbps. This equates to 50 percent of the OC-192 bandwidth excluding the POS overhead.
Task ID
Examples
The following example shows how to guarantee 50 percent of the interface bandwidth to a class called class1 and 10 percent of the interface bandwidth to a class called class2:
RP/0/RP0/CPU0:router(config)# policy-map policy1RP/0/RP0/CPU0:router(config-pmap)# class class1RP/0/RP0/CPU0:router(config-pmap-c)# bandwidth percent 50RP/0/RP0/CPU0:router(config-pmap-c)# exitRP/0/RP0/CPU0:router(config-pmap)# class class2RP/0/RP0/CPU0:router(config-pmap-c)# bandwidth percent 10Related Commands
bandwidth remaining
To specify how to allocate leftover bandwidth to various classes, use the bandwidth remaining command in policy map class configuration mode. To return to the system defaults, use the no form of this command.
bandwidth remaining percent percentage
no bandwidth remaining percent percentage
Syntax Description
percent percentage
Specifies the amount of guaranteed bandwidth, based on an absolute percentage of the available bandwidth. Range is from 1 to 100.
Defaults
No bandwidth is specified.
Command Modes
Policy map class configuration
Command History
Usage Guidelines
To use this command, you must be in a user group associated with a task group that includes the proper task IDs. For detailed information about user groups and task IDs, see the Configuring AAA Services on Cisco IOS XR Software module of the Cisco IOS XR System Security Configuration Guide.
The bandwidth remaining command is used to set the Modified Deficit Round Robin (MDRR) weight for the particular class.
When applied within an egress service policy, the command is used to define how any unallocated bandwidth should be apportioned. It typically is used in conjunction with the bandwidth command. In such a combination, if the minimum bandwidth guarantees are met, the remaining bandwidth is shared in the ratio defined by the bandwidth remaining command in the class configuration in the policy-map.
The available bandwidth is equally distributed among those queueing classes that do not have the remaining bandwidth explicitly configured.
Note
On ingress, you cannot use the bandwidth command to set the minimum bandwidth guarantee. Therefore, the bandwidth remaining command is used to proportionally allocate bandwidth to the particular classes, but there is no reserved bandwidth capacity.
Note
On both ingress and egress, if the bandwidth remaining command is not present, then the bandwidth is shared equally among the configured queueing classes present in the policy-map. When attempting precise calculations of expected MDRR behavior, you must bear in mind that because you are dealing with the bandwidth remaining on the link, you must convert the values to the bandwidth remaining percentages on the link, based upon the packet sizes of the traffic within the class. If the packet sizes are the same in all the classes, then the defined ratio is enforced precisely and predictably on the link.
Task ID
Examples
In the following example, a class called class1 is guaranteed 50 percent of the interface bandwidth and a class called class2 is guaranteed 10 percent of the interface bandwidth. The remaining bandwidth of 40 percent is shared by classes class1 and class2 in a 20:80 ratio: class class1 receives 20 percent of the 40 percent, and class class2 receives 80 percent of the 40 percent.
RP/0/RP0/CPU0:router(config)# policy-map policy1RP/0/RP0/CPU0:router(config-pmap)# class class1RP/0/RP0/CPU0:router(config-pmap-c)# bandwidth percent 50RP/0/RP0/CPU0:router(config-pmap-c)# bandwidth remaining percent 20RP/0/RP0/CPU0:router(config-pmap-c)# exitRP/0/RP0/CPU0:router(config-pmap)# class class2RP/0/RP0/CPU0:router(config-pmap-c)# bandwidth percent 10RP/0/RP0/CPU0:router(config-pmap-c)# bandwidth remaining percent 80class (policy-map)
To specify the name of the class whose policy you want to create or change, use the class command in policy map configuration mode. To remove a class from the policy map, use the no form of this command.
class [type qos] {class-name | class-default}
no class [type qos] {class-name | class-default}
Syntax Description
type qos
(Optional) Specifies a quality-of-service (QoS) class.
class-name
Name of the class for which you want to configure or modify policy.
class-default
Configures the default class.
Defaults
No class is specified.
Type is QoS when not specified.Command Modes
Policy map configuration
Command History
Usage Guidelines
To use this command, you must be in a user group associated with a task group that includes the proper task IDs. For detailed information about user groups and task IDs, see the Configuring AAA Services on Cisco IOS XR Software module of the Cisco IOS XR System Security Configuration Guide.
Policy Map Configuration Mode
Within a policy map, the class (policy-map) command can be used to specify the name of the class whose policy you want to create or change. The policy map must be identified first.
To identify the policy map (and enter the required policy map configuration mode), use the policy-map command before you use the class (policy-map) command. After you specify a policy map, you can configure the policy for new classes or modify the policy for any existing classes in that policy map.
Class Characteristics
The class name that you specify in the policy map ties the characteristics for that class—that is, its policy—to the class map and its match criteria, as configured using the class-map command.
The class-default keyword is used for configuring default classes. It is a reserved name and cannot be used with user-defined classes. It is always added to the policy map (type qos) even if the class is not configured. For example, the following configuration shows that the class has not been configured, but the running configuration shows class class-default.
RP/0/RP0/CPU0:router(config)# policy-map pm1RP/0/RP0/CPU0:router(config-pmap)# end-policy-mapRP/0/RP0/CPU0:router(config)# end!RP/0/RP0/CPU0:router# show running-config!policy-map pm1class class-default!end-policy-map!Task ID
Examples
The following example shows how to create a policy map called policy1, which is defined to shape class1 traffic at 30 percent and default class traffic at 20 percent.
RP/0/RP0/CPU0:router(config)# class-map class1RP/0/RP0/CPU0:router(config-cmap)# match precedence ipv4 3!RP/0/RP0/CPU0:router(config)# policy-map policy1RP/0/RP0/CPU0:router(config-pmap)# class class1RP/0/RP0/CPU0:router(config-pmap-c)# shape average percent 30RP/0/RP0/CPU0:router(config-pmap-c)# exitRP/0/RP0/CPU0:router(config-pmap)# class class-defaultRP/0/RP0/CPU0:router(config-pmap-c)# shape average percent 20The default class is used for packets that do not satisfy configured match criteria for class1. Class1 must be defined before it can be used in policy1, but the default class can be directly used in a policy map, as the system defines it implicitly.
Related Commands
class-map
To define a traffic class and the associated rules that match packets to the class, use the class-map command in global configuration mode. To remove an existing class map from the router, use the no form of this command.
class-map [type qos] [match-any] class-map-name
no class-map [type qos] [match-any] class-map-name
Syntax Description
Defaults
Type is QoS when not specified.
Command Modes
Global configuration
Command History
Usage Guidelines
To use this command, you must be in a user group associated with a task group that includes the proper task IDs. For detailed information about user groups and task IDs, see the Configuring AAA Services on Cisco IOS XR Software module of the Cisco IOS XR System Security Configuration Guide.
The class-map command specifies the name of the class for which you want to create or modify class map match criteria. Use of this command enables class map configuration mode in which you can enter any match command to configure the match criteria for this class. Packets arriving on the interface are checked against the match criteria configured for a class map to determine if the packet belongs to that class.
The following commands can be used in a class map:
•
•
•
•
•
•
•
•
•
•
•
•
Task ID
Examples
The following example shows how to specify class101 as the name of a class and defines a class map for this class. The packets that match the access list 101 are matched to class class101.
RP/0/RP0/CPU0:router(config)# class-map class101RP/0/RP0/CPU0:router(config-cmap)# match access-group 101Related Commands
clear qos counters
To clear QoS counters for a specified interface, use the clear qos counters command in EXEC mode.
clear qos counters type instance [input | output]
Syntax Description
Defaults
No default behavior or values
Command Modes
EXEC
Command History
Usage Guidelines
To use this command, you must be in a user group associated with a task group that includes the proper task IDs. For detailed information about user groups and task IDs, see the Configuring AAA Services on Cisco IOS XR Software module of the Cisco IOS XR System Security Configuration Guide.
The clear qos counters command clears all input and output QoS counters that are attached to a specified interface, unless the input or output keyword is specified. If the input or output keyword is specified, only counters attached to the interface in a specified direction are cleared.
Task ID
Examples
The following example shows how to clear QoS counters attached to Packet-over-SONET/SDH (POS) interface 0/7/0/3:
RP/0/RP0/CPU0:router# clear qos counters pos 0/7/0/3The following example shows how to clear output QoS counters attached to POS interface 0/7/0/3:
RP/0/RP0/CPU0:router# clear qos counters pos 0/7/0/3 outputconform-action
To configure the action to take on packets that conform to the rate limit, use the conform-action command in policy map police configuration mode. To remove a conform action from the policy-map, use the no form of this command.
conform-action {drop | set options | transmit}
no conform-action {drop | set options | transmit}
Syntax Description
drop
Drops the packet.
set options
Configures the specified packet properties. Replace options with one of the following keywords or keyword arguments:
•
•
•
•
•
•
•
•
Note
transmit
Transmits the packets.
Defaults
By default, if no action is configured on a packet that conforms to the rate limit, the packet is transmitted.
Command Modes
Policy map police configuration
Command History
Usage Guidelines
To use this command, you must be in a user group associated with a task group that includes the proper task IDs. For detailed information about user groups and task IDs, see the Configuring AAA Services on Cisco IOS XR Software module of the Cisco IOS XR System Security Configuration Guide.
The atm-clp keyword is available on the Cisco XR 12000 Series Router only.
For more information regarding the traffic policing feature, see police rate.
On the Cisco CRS-1 router, the conform-action command can be used to set the DSCP, the precedence, or the discard class for IP packets, and experimental or discard class values for MPLS packets.
On the Cisco XR 12000 Series Router, the conform-action command can be used to set values for MPLS packets in the ingress direction. The values can be set in the following combinations:
•
•
•
Note
Task ID
Examples
In the following example for MPLS, traffic policing is configured to set the MPLS experimental bit for packets that conform to the rate limit:
RP/0/RP0/CPU0:router(config)# class-map classRP/0/RP0/CPU0:router(config-cmap)# match mpls experimental topmost 0RP/0/RP0/CPU0:router(config-cmap)# exitRP/0/RP0/CPU0:router(config)# policy-map childRP/0/RP0/CPU0:router(config-pmap)# class prec1RP/0/RP0/CPU0:router(config-pmap-c)# police rate 100000000 peak-rate 3125000 peak-burst 3125000RP/0/RP0/CPU0:router(config-pmap-c-police)# conform-action set mpls experimental imp 1RP/0/RP0/CPU0:router(config-pmap-c-police)# conform-action set qos-group 1RP/0/RP0/CPU0:router(config-pmap-c-police)# conform-action set discard-class 1RP/0/RP0/CPU0:routre(config-pmap-c-police)# exitRP/0/RP0/CPU0:router(config-pmap-c)# exitRP/0/RP0/CPU0:router(config-pmap)# exitRP/0/RP0/CPU0:router(config)# interface pos 0/5/0/0RP/0/RP0/CPU0:router(config-if) service-policy input policy1Related Commands
end-class-map
To end the configuration of match criteria for the class and to exit class map configuration mode, use the end-class-map command in class map configuration mode.
end-class-map
Syntax Description
This command has no keywords or arguments.
Defaults
No default behavior or values
Command Modes
Class map configuration
Command History
Release 3.6.0
This command was introduced on the Cisco CRS-1 and Cisco XR 12000 Series Router.
Release 3.7.0
No modification.
Usage Guidelines
To use this command, you must be in a user group associated with a task group that includes the proper task IDs. For detailed information about user groups and task IDs, see the Configuring AAA Services on Cisco IOS XR Software module of the Cisco IOS XR System Security Configuration Guide.
Task ID
Examples
The following example shows how to end the class map configuration and exit class map configuration mode.
RP/0/RP0/CPU0:router(config)# class-map class101RP/0/RP0/CPU0:router(config-cmap)# match access-group 101RP/0/RP0/CPU0:router(config-cmap)# end-class-mapRP/0/RP0/CPU0:router(config)#Related Commands
Defines a traffic class and the associated rules that match packets to the class.
end-policy-map
To end the configuration of a policy map and to exit policy map configuration mode, use the end-policy-map command in policy map configuration mode.
end-policy-map
Syntax Description
This command has no keywords or arguments.
Defaults
No default behavior or values
Command Modes
Policy map configuration
Command History
Release 3.6.0
This command was introduced on the Cisco CRS-1 and Cisco XR 12000 Series Router.
Release 3.7.0
No modification.
Usage Guidelines
To use this command, you must be in a user group associated with a task group that includes the proper task IDs. For detailed information about user groups and task IDs, see the Configuring AAA Services on Cisco IOS XR Software module of the Cisco IOS XR System Security Configuration Guide.
Task ID
Examples
The following example shows how to end the policy map configuration and exit policy map configuration mode.
RP/0/RP0/CPU0:router(config)# policy-map policy1RP/0/RP0/CPU0:router(config-pmap)# class class1RP/0/RP0/CPU0:router(config-pmap-c)# police cir 250RP/0/RP0/CPU0:router(config-pmap-c)# set precedence 3RP/0/RP0/CPU0:router(config-pmap-c)# end-class-mapRP/0/RP0/CPU0:router(config-pmap)# end-policy-mapRP/0/RP0/CPU0:router(config)#Related Commands
Creates or modifies a policy map that can be attached to one or more interfaces to specify a service policy.
exceed-action
To configure the action to take on packets that exceed the rate limit, use the exceed-action command in policy map police configuration mode. To remove an exceed action from the policy-map, use the no form of this command.
exceed-action {drop | set options | transmit}
no exceed-action {drop | set options | transmit}
Syntax Description
drop
Drops the packet.
set options
Configures the specified packet properties. Replace options with one of the following keywords or keyword arguments:
•
•
•
•
•
•
•
•
•
Note
transmit
Transmits the packets.
Defaults
By default, if no action is configured on a packet that exceeds the rate limit, the packet is dropped.
Command Modes
Policy map police configuration
Command History
Usage Guidelines
To use this command, you must be in a user group associated with a task group that includes the proper task IDs. For detailed information about user groups and task IDs, see the Configuring AAA Services on Cisco IOS XR Software module of the Cisco IOS XR System Security Configuration Guide.
The atm-clp keyword is available on the Cisco XR 12000 Series Router only.
For more information regarding the traffic policing feature, see police rate.
On the Cisco CRS-1 router, the exceed-action command can be used to set the DSCP, the precedence, or the discard class for IP packets, and experimental or discard-class values for MPLS packets.
On the Cisco XR 12000 Series Router, the exceed-action command can be used to set values for MPLS packets in the following combinations:
•
•
•
Note
Task ID
Examples
In the following example for MPLS, traffic policing is configured to drop traffic that exceeds the rate limit:
RP/0/RP0/CPU0:router(config)# class-map class1RP/0/RP0/CPU0:router(config-cmap)# match mpls experimental topmost 0RP/0/RP0/CPU0:router(config-cmap)# exitRP/0/RP0/CPU0:router(config)# policy-map policy1RP/0/RP0/CPU0:router(config-pmap)# class class1RP/0/RP0/CPU0:router(config-pmap-c)# police rate 250 kbps burst 50RP/0/RP0/CPU0:router(config-pmap-c-police)# exceed-action dropRP/0/RP0/CPU0:router(config-pmap-c-police)# exitRP/0/RP0/CPU0:router(config-pmap-c)# exitRP/0/RP0/CPU0:router(config-pmap)# exitRP/0/RP0/CPU0:router(config)# interface pos 0/5/0/0RP/0/RP0/CPU0:router(config-if) service-policy input policy1Related Commands
hw-module qos account layer2 encapsulation
To configure Layer 2 encapsulation header lengths on a node, use the hw-module qos account layer2 encapsulation command in global configuration mode. To disable this functionality, use the no form of this command.
hw-module qos account layer2 encapsulation {arpa | dot1q | length value} location node-id
no hw-module qos account layer2 encapsulation {arpa | dot1q | length value} location node-id
Syntax Description
Defaults
No default behavior or values
Command Modes
Global configuration
Command History
Usage Guidelines
To use this command, you must be in a user group associated with a task group that includes the proper task IDs. For detailed information about user groups and task IDs, see the Configuring AAA Services on Cisco IOS XR Software module of the Cisco IOS XR System Security Configuration Guide.
Task ID
Examples
The following example shows how to configure Layer 2 encapsulation header lengths to 25 on 0/1/CPU0:
RP/0/0/CPU0:router# configureRP/0/0/CPU0:router(config)# hw-module qos account layer2 encapsulation length 25 0/1/CPU0Related Commands
Enables multicast egress QoS on an interface.
Enables automatic QoS queue defragmentation on a node.
Displays the status of multicast QoS on an interface.
hw-module qos acl-deny enable
To deny access control lists (ACL) on a node, use the hw-module qos acl-deny enable command in global configuration mode. To disable this functionality, use the no form of this command.
hw-module qos acl-deny enable [location node-id]
no hw-module qos acl-deny enable [location node-id]
Syntax Description
location node-id
Denies ACLs for the designated node. The node-id argument is entered in the rack/slot/module notation.
Defaults
By default, this feature is disabled.
Command Modes
Global configuration
Command History
Release 3.6.0
This command was introduced on the Cisco XR 12000 Series Router.
Release 3.7.0
No modification.
Usage Guidelines
To use this command, you must be in a user group associated with a task group that includes the proper task IDs. For detailed information about user groups and task IDs, see the Configuring AAA Services on Cisco IOS XR Software module of the Cisco IOS XR System Security Configuration Guide.
For the hw-module qos acl-deny enable command to run effectively, you must reload the line card (LC).
Task ID
Examples
The following example shows how to configure an acl-deny function on location 0/1/CPU0:
RP/0/0/CPU0:router# configureRP/0/0/CPU0:router(config)# hw-mod qos acl-deny enable location 0/1/CPU0Related Commands
hw-module qos multicast
To enable multicast egress quality of service (QoS) on a node, use the hw-module qos multicast command in global configuration mode. To disable this functionality, use the no form of this command.
hw-module qos multicast [location node-id]
no hw-module qos multicast [location node-id]
Syntax Description
location node-id
(Optional) Enables egress QoS for the designated node. The node-id argument is entered in the rack/slot/module notation.
Defaults
All multicast traffic is routed through the default queue.
Command Modes
Global configuration
Command History
Usage Guidelines
To use this command, you must be in a user group associated with a task group that includes the proper task IDs. For detailed information about user groups and task IDs, see the Configuring AAA Services on Cisco IOS XR Software module of the Cisco IOS XR System Security Configuration Guide.
The hw-module qos multicast command enables multicast QoS, which means that general, system wide QoS applies to multicast traffic as well.
Note
If multicast QoS is disabled (which is the default value), all multicast traffic travels to the default queue. When multicast routes are configured with QoS enabled, there may be insufficient resources (PLU/TLU, MGIDs, and so on.) to support multicast QoS for all routes. In such cases, some multicast routes are unchanged and associated multicast traffic is routed to the default queue.
For complete information about QoS in Cisco IOS XR software, see the Cisco IOS XR Modular Quality of Service Configuration Guide.
Task ID
Examples
The following example shows how to enable multicast QoS on location 0/1/CPU0:
RP/0/0/CPU0:router# configureRP/0/0/CPU0:router(config)# hw-module qos multicast location 0/1/CPU0Related Commands
hw-module qos multicast priorityq disable
To divert multicast traffic slated for the priority queue to the default queue, use the hw-module qos multicast priorityq disable command in global configuration mode. To disable this functionality, use the no form of this command.
hw-module qos multicast priorityq disable {location node-id}
no hw-module qos multicast priorityq disable {location node-id}
Syntax Description
location node-id
Assigns a QoS priority value for the designated node. The node-id argument is entered in the rack/slot/module notation.
Defaults
By default, all multicast traffic is routed to the priority queue (as defined by the QoS policy).
Command Modes
Global configuration
Command History
Usage Guidelines
To use this command, you must be in a user group associated with a task group that includes the proper task IDs. For detailed information about user groups and task IDs, see the Configuring AAA Services on Cisco IOS XR Software module of the Cisco IOS XR System Security Configuration Guide.
Note
For complete information about QoS in Cisco IOS XR software, see the Cisco IOS XR Modular Quality of Service Configuration Guide.
Task ID
Examples
The following example shows how to divert multicast traffic slated for the priority queue to the default queue on 0/1/CPU0:
RP/0/0/CPU0:router# hw-module qos multicast priorityq disable 0/1/CPU0Related Commands
Enables multicast egress QoS on a node.
Displays the status of multicast QoS for one or more interfaces.
hw-module qos queue-auto-defrag
To disable automatic QoS queue defragmentation on a node, use the hw-module qos queue-auto-defrag command in global configuration mode. To disable this functionality, use the no form of this command.
hw-module qos queue-auto-defrag disable location node-id
no hw-module qos queue-auto-defrag disable location node-id
Syntax Description
Defaults
No default behavior or values
Command Modes
Global configuration
Command History
Usage Guidelines
To use this command, you must be in a user group associated with a task group that includes the proper task IDs. For detailed information about user groups and task IDs, see the Configuring AAA Services on Cisco IOS XR Software module of the Cisco IOS XR System Security Configuration Guide.
Task ID
Examples
The following example shows how to disable automatic QoS queue defragmentation on location 0/1/CPU0:
RP/0/0/CPU0:router# configureRP/0/0/CPU0:router(config)# hw-module qos queue-auto-defrag disable location 0/1/CPU0Related Commands
Configures Layer 2 encapsulation header lengths on a node.
Enables multicast egress QoS on an interface.
Displays the status of multicast QoS on an interface.
match access-group
To identify a specified access control list (ACL) number as the match criteria for a class map, use the match access-group command in class map configuration mode. To remove ACL match criteria from a class map, use the no form of this command.
match access-group [ipv4 | ipv6] access-group-name
no match access-group [ipv4 | ipv6] access-group-name
Syntax Description
Defaults
By default, if neither IPv6 nor IPv4 is specified as the match criteria for a class map, IPv4 addressing is used.
Command Modes
Class map configuration
Command History
Usage Guidelines
To use this command, you must be in a user group associated with a task group that includes the proper task IDs. For detailed information about user groups and task IDs, see the Configuring AAA Services on Cisco IOS XR Software module of the Cisco IOS XR System Security Configuration Guide.
For class-based features (such as marking, Modified Deficit Round Robin [MDRR], and policing), you define traffic classes based on match criteria, including ACLs and input interfaces. Packets satisfying the match criteria for a class constitute the traffic for that class.
The match access-group command specifies an ACL whose contents are used as the match criteria against which packets are checked to determine if they belong to the class specified by the class map.
Note
To use the match access-group command, you must first enter the class-map command to specify the name of the class whose match criteria you want to establish. You can specify upto eight IPv4 and IPv6 ACLs in a match statement.
Task ID
Examples
The following example shows how to specify a class map called map1 and configures map1 to be used as the match criteria for this class:
RP/0/RP0/CPU0:router(config)# class-map map1RP/0/RP0/CPU0:router(config-cmap)# match access-group map1Related Commands
match cos
To identify specified class of service (CoS) values as a match criteria in a class map, use the match cos command in class map configuration mode. To remove a specified CoS class value from the matching criteria for a class map, use the no form of this command.
match [not] cos cos-value {cos-value1 ... cos-value7}
no match [not] cos cos-value {cos-value1 ... cos-value7}
Syntax Description
Defaults
No match criteria are specified.
Command Modes
Class map configuration
Command History
Usage Guidelines
To use this command, you must be in a user group associated with a task group that includes the proper task IDs. For detailed information about user groups and task IDs, see the Configuring AAA Services on Cisco IOS XR Software module of the Cisco IOS XR System Security Configuration Guide.
The match cos command specifies a class of service that is used as the match criteria against which packets are checked to determine if they belong to the class specified by the class map.
To use the match cos command, you must first enter the class-map command to specify the name of the class whose match criteria you want to establish. If you specify more than one match cos command in a class map, the values of subsequent match statements are added to the first match cos command.
The match cos command is not supported on an output service policy attached to a Layer 3 interface (POS interface or routed VLAN subinterface).
The match cos command is supported on egress Layer 2 interfaces, Layer 2 subinterfaces, and Layer 3 physical interfaces. Layer 3 physical interfaces are supported, because it is possible for a Layer 3 interface to have underlying Layer 2 subinterfaces. For the Cisco XR 12000 Series Router, this command is supported only on the ingress ethernet subinterface.
Task ID
Examples
The following example shows how to configure the service policy called policy1 and attach service policy policy1 to an interface. In this example, class map cos146 evaluates all packets entering Packet-over-SONET/SDH (POS) interface 0/1/0/0 for class of service values of 1, 4, or 6. If the incoming packet has been marked with any of these CoS values, the packet is queued to the class queue with the bandwidth setting of 300 kbps.
RP/0/RP0/CPU0:router(config)# class-map cos146RP/0/RP0/CPU0:router(config-cmap)# match cos 1 4 6RP/0/RP0/CPU0:router(config-cmap)# exitRP/0/RP0/CPU0:router(config)# policy-map policy1RP/0/RP0/CPU0:router(config-pmap)# class cos146RP/0/RP0/CPU0:router(config-pmap-c)# bandwidth 300RP/0/RP0/CPU0:router(config-pmap-c)# exitRP/0/RP0/CPU0:router(config-pmap)# exitRP/0/RP0/CPU0:router(config)# interface pos 0/1/0/0RP/0/RP0/CPU0:router(config-if)# service-policy input policy1Related Commands
match destination-address
To identify a specific destination MAC address explicitly as a match criterion in a class map, use the match destination-address command in class map configuration mode. To remove a specific destination MAC address from the matching criteria for a class map, use the no form of this command.
match destination-address mac address
no match destination-address mac address
Syntax Description
Defaults
No default behavior or values
Command Modes
Class map configuration
Command History
Usage Guidelines
To use this command, you must be in a user group associated with a task group that includes the proper task IDs. For detailed information about user groups and task IDs, see the Configuring AAA Services on Cisco IOS XR Software module of the Cisco IOS XR System Security Configuration Guide.
The match destination-address command specifies a destination address that is used as the match criteria against which packets are checked to determine if they belong to the class specified by the class map.
To use the match destination-address command, you must first enter the class-map command to specify the name of the class whose match criteria you want to establish. If you specify more than one match destination-address command in a class map, only the last command entered applies.
The match destination-address command is supported only on an output service policy.
Layer 2 match criteria on a Layer 3 target, or Layer 3 match criteria on a Layer 2 target, is not allowed. The match destination-address command is supported on egress Layer 2 interfaces, Layer 2 subinterfaces, and Layer 3 physical interfaces. Layer 3 physical interfaces are supported, because it is possible for a Layer 3 interface to have underlying Layer 2 subinterfaces.
The command is allowed on a policy map that is attached to an Ethernet interface. The command is invalid on a policy that is attached to a Packet-over-SONET/SDH (POS) interface or a routed VLAN subinterface.
The match 48-bit MAC address is specified in xxxx.xxxx.xxxx format on L2VPN PE interfaces.
Task ID
Examples
The following example shows how to match a destination MAC address:
RP/0/RP0/CPU0:router(config)# class-map match-any ARP/0/RP0/CPU0:router(config-cmap)# match destination-address mac 000.f0d0.2356Related Commands
Defines a traffic class and the associated rules that match packets to the class.
match discard-class
To identify specific discard class values as a match criteria for a class map, use the match discard-class command in class map configuration mode. To remove specified discard class values from the matching criteria for a class map, use the no form of this command.
match [not] discard-class discard-class-value [discard-class-value1 ... discard-class-value7]
no match [not] discard-class discard-class-value [discard-class-value1 ... discard-class-value7]
Syntax Description
Defaults
No default behavior or values
Command Modes
Class map configuration
Command History
Usage Guidelines
To use this command, you must be in a user group associated with a task group that includes the proper task IDs. For detailed information about user groups and task IDs, see the Configuring AAA Services on Cisco IOS XR Software module of the Cisco IOS XR System Security Configuration Guide.
The match discard-class command specifies a discard class that is used as the match criteria against which packets are checked to determine if they belong to the class specified by the class map.
To use the match discard-class command, you must first enter the class-map command to specify the name of the class whose match criteria you want to establish. If you specify more than one match discard-class command in a class map, the new values are added to the existing match statement.
The match discard-class command sets the match criteria for examining discard classes marked on the packet. Up to eight discard class values can be matched in one match statement. For example, match discard-class 0 1 2 3 4 5 6 7 returns matches for discard class values 0, 1, 2, 3, 4, 5, 6, and 7. Only one of the seven values is needed to yield a match (OR operation).
The discard class value is used as a matching criterion only. The value has no mathematical significance. For instance, the discard class value 2 is not greater than 1. The value simply indicates that a packet marked with the discard class of 2 should be treated differently than a packet marked with a discard class value of 1.
Note
Task ID
Examples
The following example shows a service policy called policy1 attached to an interface. In this example, class map discard class5 is created to evaluate all packets leaving Packet-over-SONET/SDH (POS) interface 0/2/0/1 for a discard-class value of 5. Packets marked with the discard class value of 5 are queued to a class queue with the bandwidth setting 300 kbps.
RP/0/RP0/CPU0:router(config)# class-map discard-class5RP/0/RP0/CPU0:router(config-cmap)# match discard-class 5RP/0/RP0/CPU0:router(config-cmap)# exitRP/0/RP0/CPU0:router(config)# policy-map policy1RP/0/RP0/CPU0:router(config-pmap)# class discard-class5RP/0/RP0/CPU0:router(config-pmap-c)# bandwidth 300RP/0/RP0/CPU0:router(config-pmap-c)# exitRP/0/RP0/CPU0:router(config-pmap)# exitRP/0/RP0/CPU0:router(config)# interface pos 0/2/0/1RP/0/RP0/CPU0:router(config-if)# service-policy output policy1Related Commands
match dscp
To identify specific IP differentiated services code point (DSCP) values as match criteria for a class map, use the match dscp command in class map configuration mode. To remove a DSCP value from a class map, use the no form of this command.
match [not] dscp [ipv4 | ipv6] dscp-value [dscp-value1 ... dscp-value7]
no match [not] dscp [ipv4 | ipv6] dscp-value [dscp-value1 ... dscp-value7]
Syntax Description
not
(Optional) Negates the specified match result.
ipv4
(Optional) Specifies the IPv4 DSCP value.
ipv6
(Optional) Specifies the IPv6 DSCP value.
dscp-value
IP DSCP value identifier that specifies the exact value or a range of values. Range is 0 to 63. Up to eight IP DSCP values can be specified to match packets. Reserved keywords can be specified instead of numeric values. Table 1 describes the reserved keywords.
Note
Defaults
Matching on both IP Version 4 (IPv4) and IPv6 packets is the default.
Command Modes
Class map configuration
Command History
Usage Guidelines
To use this command, you must be in a user group associated with a task group that includes the proper task IDs. For detailed information about user groups and task IDs, see the Configuring AAA Services on Cisco IOS XR Software module of the Cisco IOS XR System Security Configuration Guide.
The match dscp command specifies a DSCP value that is used as the match criteria against which packets are checked to determine if they belong to the class specified by the class map.
To use the match dscp command, you must first enter the class-map command to specify the name of the class whose match criteria you want to establish. If you specify more than one match dscp command in a class map, only the last command entered applies.
The match dscp command examines the higher-order six bits in the type of service (ToS) byte of the IP header. Only one of the eight values is needed to yield a match (OR operation).
The command supports only eight IP DSCP values. If you try to configure more match statements after all the eight values are matched, the statements get rejected.
The IP DSCP value is used as a matching criterion only. The value has no mathematical significance. For instance, the IP DSCP value 2 is not greater than 1. The value simply indicates that a packet marked with the IP DSCP value of 2 should be treated differently than a packet marked with an IP DSCP value of 1. The treatment of these marked packets is defined by the user through the setting of QoS policies in policy map class configuration mode.
The reserved keywords listed in Table 1 can be specified instead of numeric values.
Task ID
Examples
The following example shows how to configure the service policy called policy1 and attach service policy policy1 to an interface. In this example, class map dscp14 evaluates all packets entering Packet-over-SONET/SDH (POS) interface 0/1/0/0 for an IP DSCP value of 14. If the incoming packet has been marked with the IP DSCP value of 14, the packet is queued to the class queue with the bandwidth setting of 300 kbps.
RP/0/RP0/CPU0:router(config)# class-map dscp14RP/0/RP0/CPU0:router(config-cmap)# match dscp ipv4 14RP/0/RP0/CPU0:router(config-cmap)# exitRP/0/RP0/CPU0:router(config)# policy-map policy1RP/0/RP0/CPU0:router(config-pmap)# class dscp14RP/0/RP0/CPU0:router(config-pmap-c)# bandwidth 300RP/0/RP0/CPU0:router(config-pmap-c)# exitRP/0/RP0/CPU0:router(config-pmap)# exitRP/0/RP0/CPU0:router(config)# interface pos 0/1/0/0RP/0/RP0/CPU0:router(config-if)# service-policy input policy1Related Commands
match frame-relay dlci
To specify a Frame Relay packet data-link connection identifier (DLCI) number or number range as a match criterion in a class map, use the match frame-relay dlci command in class map configuration mode. To remove a previously specified DLCI number as a match criterion, use the no form of this command.
match frame-relay dlci [Dlci | StartDlci-EndDlci]
no match frame-relay dlci [Dlci | StartDlci-EndDlci]
Syntax Description
Dlci
A DLCI number associated with the packet. Range is from 16 to 1007.
StartDlci-EndDlci
A DLCI number range from 16 to 1007. Numbers are separated by a hyphen.
Defaults
No DLCI number is specified.
Command Modes
Class map configuration
Command History
Release 3.4.0
This command was introduced on the Cisco XR 12000 Series Router.
Release 3.5.0
No modification.
Release 3.6.0
No modification.
Release 3.7.0
No modification.
Usage Guidelines
To use this command, you must be in a user group associated with a task group that includes the proper task IDs. For detailed information about user groups and task IDs, see the Configuring AAA Services on Cisco IOS XR Software module of the Cisco IOS XR System Security Configuration Guide.
The match criterion for the match frame-relay dlci command can be used only on hierarchical policy maps.
Task ID
Examples
The following example shows how to create the fr-dlci class map, and specify the Frame Relay DLCI number range 100-200 as a match criterion. Packets with DLCIs matching this criterion are placed in fr-dlci. In this example, class map fr-dlci evaluates all packets entering Packet-over-SONET/SDH (POS) interface 0/1/0/0.1 for DLCIs in the range from 100 through 200. If the incoming packet has been marked with the DLCI in the range from 100 through 200, the packet is queued to the class queue with the bandwidth setting of 300 kbps.
RP/0/0/CPU0:router(config)# class-map fr-dlciRP/0/0/CPU0:router(config-cmap)# match frame relay dlci 100-200RP/0/0/CPU0:router(config-cmap)# endRP/0/0/CPU0:router(config)# policy-map policy1RP/0/0/CPU0:router(config-pmap)# class fr-dlciRP/0/0/CPU0:router(config-pmap-c)# bandwidth 300RP/0/0/CPU0:router(config-pmap-c)# exitRP/0/0/CPU0:router(config-pmap)# exitRP/0/0/CPU0:router(config)# interface pos 0/1/0/0.1RP/0/0/CPU0:router(config-if)# service-policy input policy1Related Commands
match mpls experimental topmost
To identify specific three-bit experimental (EXP) field values in the topmost Multiprotocol Label Switching (MPLS) label as match criteria for a class map, use the match mpls experimental topmost command in class map configuration mode. To remove experimental field values from the class map match criteria, use the no form of the command.
match [not] mpls experimental topmost exp-value [exp-value1 ... exp-value7]
no match [not] mpls experimental topmost exp-value [exp-value1 ... exp-value7]
Syntax Description
not
(Optional) Negates the specified match result.
exp-value
Experimental value that specifies the exact value from 0 to 7. Up to eight experimental values can be specified to match MPLS headers.
Defaults
No default behavior or values
Command Modes
Class map configuration
Command History
Usage Guidelines
To use this command, you must be in a user group associated with a task group that includes the proper task IDs. For detailed information about user groups and task IDs, see the Configuring AAA Services on Cisco IOS XR Software module of the Cisco IOS XR System Security Configuration Guide.
The match mpls experimental topmost command is used by the class map to identify MPLS experimental values matching on a packet.
To use the match mpls experimental topmost command, you must first enter the class-map command to specify the name of the class whose match criteria you want to establish. If you specify more than one match mpls experimental topmost command in a class map, the new values are added to the existing match statement.
This command examines the three experimental bits contained in the topmost label of an MPLS packet. Up to eight experimental values can be matched in one match statement. For example, match mpls experimental topmost 2 4 5 7 returns matches for experimental values of 2, 4, 5, and 7. Only one of the four values is needed to yield a match (OR operation).
The experimental values are used as a matching criterion only. The value has no mathematical significance. For instance, the experimental value 2 is not greater than 1. The value indicates that a packet marked with the experimental value of 2 should be treated differently than a packet marked with the EXP value of 1. The treatment of these different packets is defined by the user through the setting of QoS policies in policy map class configuration mode.
Task ID
Examples
The following example shows how to configure the service policy called policy1 and attach service policy policy1 to an interface. In this example, class map mplsmap1 evaluates all packets entering Packet-over-SONET/SDH (POS) interface 0/5/0/0 for an MPLS experimental value of 1. If the incoming packet has been marked with the MPLS experimental value of 1, the packet is queued to the class queue with the bandwidth setting of 300 kbps.
RP/0/RP0/CPU0:router(config)# class-map mplsmap1RP/0/RP0/CPU0:router(config-cmap)# match mpls experimental topmost 1RP/0/RP0/CPU0:router(config-cmap)# exitRP/0/RP0/CPU0:router(config)# policy-map policy1RP/0/RP0/CPU0:router(config-pmap)# class mplsmap1RP/0/RP0/CPU0:router(config-pmap-c)# bandwidth 300RP/0/RP0/CPU0:router(config-pmap-c)# exitRP/0/RP0/CPU0:router(config-pmap)# exitRP/0/RP0/CPU0:router(config)# interface pos 0/5/0/0RP/0/RP0/CPU0:router(config-if)# service-policy input policy1Related Commands
match precedence
To identify IP precedence values as match criteria, use the match precedence command in class map configuration mode. To remove precedence values from a class map, use the no form of this command.
match [not] precedence [ipv4 | ipv6] precedence-value [precedence-value1 ... precedence-value7]
no match [not] precedence [ipv4 | ipv6] precedence-value [precedence-value1 ... precedence-value7]
Syntax Description
not
(Optional) Negates the specified match result.
ipv4
(Optional) Specifies the IPv4 precedence value.
ipv6
(Optional) Specifies the IPv6 precedence value.
precedence-value
An IP precedence value identifier that specifies the exact value. Range is from 0 to 7. Reserved keywords can be specified instead of numeric values. Table 2 describes the reserved keywords.
Up to eight precedence values can be matched in one match statement.
Defaults
Matching on both IP Version 4 (IPv4) and IPv6 packets is the default.
Command Modes
Class map configuration
Command History
Usage Guidelines
To use this command, you must be in a user group associated with a task group that includes the proper task IDs. For detailed information about user groups and task IDs, see the Configuring AAA Services on Cisco IOS XR Software module of the Cisco IOS XR System Security Configuration Guide.
The match precedence command specifies a precedence value that is used as the match criteria against which packets are checked to determine if they belong to the class specified by the class map.
To use the match precedence command, you must first enter the class-map command to specify the name of the class whose match criteria you want to establish. If you specify more than one match precedence command in a class map, only the last command entered applies.
The match precedence command examines the higher-order three bits in the type of service (ToS) byte of the IP header. Up to eight precedence values can be matched in one match statement. For example, match precedence ipv4 0 1 2 3 4 5 6 7 returns matches for IP precedence values of 0, 1, 2, 3, 4, 5, 6, and 7. Only one of the eight values is needed to yield a match (OR operation).
The precedence values are used as a matching criterion only. The value has no mathematical significance. For instance, the precedence value 2 is not greater than 1. The value simply indicates that a packet marked with the precedence value of 2 is different than a packet marked with the precedence value of 1. The treatment of these different packets is defined by the user through the setting of QoS policies in policy map class configuration mode.
Table 2 lists the IP precedence value number and associated name in descending order of importance.
Table 2 IP Precedence Values and Names
0
routine
1
priority
2
immediate
3
flash
4
flash-override
5
critical
6
internet
7
network
ipv4
ipv4 precedence
ipv6
ipv6 precedence
Task ID
Examples
The following example shows how to configure the service policy called policy1 and attach service policy policy1 to an interface. In this example, class map ipprec5 evaluates all packets entering Packet-over-SONET/SDH (POS) interface 0/1/0/0 for a precedence value of 5. If the incoming packet has been marked with the precedence value of 5, the packet is queued to the class queue with the bandwidth setting 300 kbps.
RP/0/RP0/CPU0:router(config)# class-map ipprec5RP/0/RP0/CPU0:router(config-cmap)# match precedence ipv4 5RP/0/RP0/CPU0:router(config-cmap)# exitRP/0/RP0/CPU0:router(config)# policy-map policy1RP/0/RP0/CPU0:router(config-pmap)# class ipprec5RP/0/RP0/CPU0:router(config-pmap-c)# bandwidth 300RP/0/RP0/CPU0:router(config-pmap-c)# exitRP/0/RP0/CPU0:router(config-pmap)# exitRP/0/RP0/CPU0:router(config)# interface pos 0/1/0/0RP/0/RP0/CPU0:router(config-if)# service-policy input policy1Related Commands
match protocol
To identify a specific protocol as the match criterion for a class map, use the match protocol command in class map configuration mode. To remove protocol-based match criteria from a class map, use the no form of this command.
match [not] protocol protocol-value [protocol-value1 ... protocol-value7]
no match [not] protocol protocol-value [protocol-value1 ... protocol-value7]
Syntax Description
Defaults
No default behavior or values
Command Modes
Class map configuration
Command History
Usage Guidelines
To use this command, you must be in a user group associated with a task group that includes the proper task IDs. For detailed information about user groups and task IDs, see the Configuring AAA Services on Cisco IOS XR Software module of the Cisco IOS XR System Security Configuration Guide.
Definitions of traffic classes are based on match criteria, including protocols, access control lists (ACLs), input interfaces, QoS labels, and experimental (EXP) field values. Packets satisfying the match criteria for a class constitute the traffic for that class.
The match protocol command specifies the name of a protocol to be used as the match criteria against which packets are checked to determine if they belong to the class specified by the class map. Available protocol names are listed in Table 3.
The protocol-value argument supports a range of protocol numbers. After you identify the class, you may use the match protocol command to configure its match criteria.
Task ID
Examples
In the following example, all TCP packets belong to class class1:
RP/0/RP0/CPU0:router(config)# class class1RP/0/RP0/CPU0:router(config-cmap)# match protocol tcpRelated Commands
match qos-group
To identify specific quality-of-service (QoS) group values as match criteria in a class map, use the match qos-group command in class map configuration mode. To remove a specific QoS group value from the matching criteria for a class map, use the no form of this command.
match [not] qos-group {qos-group-value1 ... qos-group-value7}
no match [not] qos-group
Syntax Description
Defaults
No match criteria are specified.
Command Modes
Class map configuration
Command History
Usage Guidelines
To use this command, you must be in a user group associated with a task group that includes the proper task IDs. For detailed information about user groups and task IDs, see the Configuring AAA Services on Cisco IOS XR Software module of the Cisco IOS XR System Security Configuration Guide.
The match qos-group command sets the match criteria for examining QoS groups marked on the packet. Up to eight QoS group values can be matched in one match statement. For example, match qos-group 4 9 11 15 16 21 30 31 returns matches for QoS group values of 4 9 11 15 16 21 30, and 31. Only one of the eight values is needed to yield a match (OR operation).
The match qos-group command is used on the ingress match to support QoS Policy Propagation using BGP (QPPB). To use this command, you must first enter the class-map command to specify the name of the class whose match criteria you want to establish. If you specify more than one match qos-group command in a class map, the subsequent match statements are added to the first match qos-group command.
The QoS group value is used as a matching criterion only. The value has no mathematical significance. For instance, the QoS group value 2 is not greater than 1. The value simply indicates that a packet marked with the QoS group value of 2 should be treated differently than a packet marked with a QoS group value of 1. The treatment of these different packets is defined using the service-policy command in policy map class configuration mode.
The QoS group setting is limited in scope to the local router. Typically, the QoS group is set on the local router and is used in conjunction with WRED or MDRR to give differing levels of service based on the group identifier.
Task ID
Examples
The following example shows a service policy called policy1 attached to an interface. In this example, class map qosgroup5 will evaluate all packets leaving Packet-over-SONET/SDH (POS) interface 1/0/0/1 for a QoS group value of 5. If the packet has been marked with the QoS group value of 5, the packet is queued to the class queue with the bandwidth setting 300 kbps.
RP/0/RP0/CPU0:router(config)# class-map qosgroup5RP/0/RP0/CPU0:router(config-cmap)# match qos-group 5RP/0/RP0/CPU0:router(config-cmap)# exitRP/0/RP0/CPU0:router(config)# policy-map policy1RP/0/RP0/CPU0:router(config-pmap)# class qosgroup5RP/0/RP0/CPU0:router(config-pmap-c)# bandwidth 300RP/0/RP0/CPU0:router(config-pmap-c)# exitRP/0/RP0/CPU0:router(config-pmap)# exitRP/0/RP0/CPU0:router(config)# interface pos 0/1/0/0RP/0/RP0/CPU0:router(config-if)# service-policy output policy1Related Commands
match source-address
To identify a specific source MAC address as match criterion in a class map, use the match source-address command in class map configuration mode. To remove a specific source MAC address from the matching criteria for a class map, use the no form of this command.
match source-address mac {address}
no match source-address mac {address}
Syntax Description
Defaults
No default behavior or values
Command Modes
Class map configuration
Command History
Usage Guidelines
To use this command, you must be in a user group associated with a task group that includes the proper task IDs. For detailed information about user groups and task IDs, see the Configuring AAA Services on Cisco IOS XR Software module of the Cisco IOS XR System Security Configuration Guide.
The match source-address command specifies a source address that is used as the match criterion against which packets are checked to determine if they belong to the class specified by the class map.
To use the match source-address command, you must first enter the class-map command to specify the name of the class whose match criteria you want to establish. If you specify more than one match source-address command in a class map, only the last command entered applies.
This command is supported on an input service policy only.
Layer 2 match criteria on a Layer 3 target, or Layer 3 match criteria on a Layer 2 target is not allowed. The match source-address command is supported on egress Layer 2 interfaces, Layer 2 subinterfaces, and Layer 3 physical interfaces. Layer 3 physical interfaces are supported, because it is possible for a Layer 3 interface to have underlying Layer 2 subinterfaces.
The match source-address command is allowed on a policy map that is attached to an Ethernet interface. The command is invalid on a policy that is attached to a Packet-over-SONET/SDH (POS) interface or a routed VLAN subinterface.
The match 48-bit MAC address is specified in xxxx.xxxx.xxxx format on L2VPN PE interfaces.
Task ID
Examples
The following example shows how to match a source MAC address:
RP/0/RP0/CPU0:router(config)# class-map match-any ARP/0/RP0/CPU0:router(config-cmap)# match source-address mac 000.f0d0.2356Related Commands
Defines a traffic class and the associated rules that match packets to the class.
match vlan
To identify selected VLAN IDs as the match criteria for a class map, use the match vlan command in class map configuration mode. To remove VLAN ID match criteria from a class map, use the no form of this command.
match vlan vlanid [vlanid1... vlanid7]
no match vlan vlanid [vlanid1 ... vlanid7]
Syntax Description
Defaults
No match criteria are specified.
Command Modes
Class map configuration
Command History
Usage Guidelines
To use this command, you must be in a user group associated with a task group that includes the proper task IDs. For detailed information about user groups and task IDs, see the Configuring AAA Services on Cisco IOS XR Software module of the Cisco IOS XR System Security Configuration Guide.
The match vlan command specifies a VLAN ID that is used as the match criteria against which packets are checked to determine if they belong to the class specified by the class map.
To use the match vlan command, you must first enter the class-map command to specify the name of the class whose match criteria you want to establish. If you specify more than one match vlan command in a class map, upto eight values of the subsequent match statements are added to the first match vlan command, exceeding which, the statement is rejected.
Task ID
Examples
The following example shows how to configure the service policy called policy1 and attach service policy policy1 to an interface. In this example, class map vlan1 evaluates all packets entering Gigabit Ethernet interface 0/1/0/0 for VLAN IDs of 1234, 1698, and all the VLAN IDs in the range 3000 to 4000. If the incoming packet has been marked with any of these VLAN IDs, the packet is queued to the class queue with the bandwidth setting of 300 kbps.
RP/0/RP0/CPU0:router(config)# class-map vlan1RP/0/RP0/CPU0:router(config-cmap)# match vlan 1234 1698 3000-4000RP/0/RP0/CPU0:router(config-cmap)# exitRP/0/RP0/CPU0:router(config)# policy-map policy1RP/0/RP0/CPU0:router(config-pmap)# class vlan1RP/0/RP0/CPU0:router(config-pmap-c)# bandwidth 300RP/0/RP0/CPU0:router(config-pmap-c)# exitRP/0/RP0/CPU0:router(config-pmap)# exitRP/0/RP0/CPU0:router(config)# interface gigabitethernet 0/1/0/0RP/0/RP0/CPU0:router(config-if)# service-policy input policy1Related Commands
Defines a traffic class and the associated rules that match packets to the class.
police rate
To configure traffic policing and enter policy map police configuration mode, use the police rate command in policy map class configuration mode. To remove traffic policing from the configuration, use the no form of this command.
police rate {value [units] | percent percentage} [burst burst-size [burst-units]][peak-rate value [units]] [peak-burst peak-burst [burst-units]] | percent percentage]
no police rate {value [units] | percent percentage} [burst burst-size [burst-units]] [peak-rate value [units]][peak-burst peak-burst [burst-units]] | percent percentage]
Syntax Description
Defaults
No restrictions on the flow of data are applied to any interface.
Command Modes
Policy map class configuration
Command History
Usage Guidelines
To use this command, you must be in a user group associated with a task group that includes the proper task IDs. For detailed information about user groups and task IDs, see the Configuring AAA Services on Cisco IOS XR Software module of the Cisco IOS XR System Security Configuration Guide.
The atm-clp keyword is available on the Cisco XR 12000 Series Router only.
The traffic policing feature works with a single-token bucket algorithm on the Cisco XR 12000 Series Router, and a two-token bucket algorithm on the Cisco CRS-1.
The police command can set the DSCP, the precedence, or the discard class for IP packets, and experimental and discard-class values for MPLS packets.
For bundled interfaces, traffic policing can be configured only as a percentage.
On the Cisco CRS-1 router, if no violate-action is specified, a default action of drop is applied, thereby activating two token buckets.
Policing can be applied in both ingress and egress directions.
The parameters set by the action keywords are rounded by the hardware. To check the actual values programmed in the hardware use the show qos interface command.
For police rate commands in the child policy, the reference used for percentage parameters is relative to the maximum rate of the parent. If traffic policing or shaping is not configured on the parent, then the parent inherits the interface shape rate.
Hierarchical policing is also supported. In such a configuration, both parent and child policies have class-maps containing policing statements, as in the following example:
!policy-map childclass goldpolice rate percent 50 conform-action set precedence immediate exceed-action drop!!policy-map parentclass match_allpolice rate 10000 kbps burst 15000 exceed-action dropservice-policy child!!The Cisco XR 12000 Series Router supports hierarchical ingress policing, which consists of a two-level hierarchical policy-map. The two levels are as follows:
•
•
You can police the ingress interface while applying different classification submodels on the ingress interfaces. The order of the actions within the hierarchical policy-map is from child to parent as specified by the Modular Quality of Service command-line interface (MQC), except the queuing action (shape), which is executed after any police/set actions. If a police action is configured in a child policy, the child police action is executed before the parent police action.
The police command action is invoked with only transmit/drop actions under conform-action and exceed-action options specified for class-default traffic.
The following example explains a hierarchical policer configuration:
!policy-map parentclass class-defaultservice-policy childpolice rate percent 50 conform-action transmit exceed-action drop!
Note
The policer uses an incremental step size of 256 kbps. The configured value is rounded down to the nearest 256 kbps. The value shown in the output of the running-configuration shows the configured value as entered by the user.
If the burst value is not specifically configured, it is automatically set to equate to 250 msec-worth of the CIR value. For example, if a CIR value of 1000000 kbps is entered, the burst value is calculated to be 32000000 bytes. However, the maximum burst value supported is 2,097,120 bytes.
Task ID
Examples
In the following example for MPLS, traffic policing is configured with the average rate at 250 kbps, and the normal burst size at 50 bytes for all packets leaving Packet-over-SONET/SDH (POS) interface 0/5/0/0:
RP/0/RP0/CPU0:router(config)# class-map class1RP/0/RP0/CPU0:router(config-cmap)# match mpls experimental topmost 0RP/0/RP0/CPU0:router(config-cmap)# exitRP/0/RP0/CPU0:router(config)# policy-map policy1RP/0/RP0/CPU0:router(config-pmap)# class class1RP/0/RP0/CPU0:router(config-pmap-c)# police rate 250 kbps burst 50 conform-action set mpls experimental topmost 4RP/0/RP0/CPU0:router(config-pmap-c)# exitRP/0/RP0/CPU0:router(config-pmap)# exitRP/0/RP0/CPU0:router(config)# interface pos 0/5/0/0RP/0/RP0/CPU0:router(config-if) service-policy input policy1Related Commands
policy-map
To create or modify a policy map that can be attached to one or more interfaces to specify a service policy, use the policy-map command in global configuration mode. To delete a policy map, use the no form of this command.
policy-map [type qos] policy-name
no policy-map [type qos] policy-name
Syntax Description
type qos
(Optional) Specifies a quality-of-service (QoS) policy map.
policy-name
Name of the policy map.
Defaults
A policy map does not exist until one is configured. Because a policy map is applied to an interface, no restrictions on the flow of data are applied to any interface until a policy map is created.
Type is QoS when not specified.Command Modes
Global configuration
Command History
Usage Guidelines
To use this command, you must be in a user group associated with a task group that includes the proper task IDs. For detailed information about user groups and task IDs, see the Configuring AAA Services on Cisco IOS XR Software module of the Cisco IOS XR System Security Configuration Guide.
Use the policy-map command to specify the name of the policy map to be created, added to, or modified before you can configure policies for classes whose match criteria are defined in a class map. Entering the policy-map command enables policy map configuration mode in which you can configure or modify the class policies for that policy map.
You can configure class policies in a policy map only if the classes have match criteria defined for them. Use the class-map and match commands to configure the match criteria for a class. Because you can configure a maximum of 512 classes in one policy map, no policy map can contain more than 512 class policies. The maximum number of 512 classes per policy includes the implicit default class and its child policies.
A single policy map can be attached to multiple interfaces concurrently. The maximum number of policy maps supported is 1000.
Task ID
Examples
The following examples show how to create a policy map called policy1 and configures two class policies included in that policy map. The policy map is defined to contain policy specification for class1 and the default class (called class-default) to which packets that do not satisfy configured match criteria are directed. Class1 specifies policy for traffic that matches access control list 136.
RP/0/RP0/CPU0:router(config)# class-map class1RP/0/RP0/CPU0:router(config-cmap)# match access-group 136RP/0/RP0/CPU0:router(config)# policy-map policy1RP/0/RP0/CPU0:router(config-pmap)# class class1RP/0/RP0/CPU0:router(config-pmap-c)# police cir 250RP/0/RP0/CPU0:router(config-pmap-c)# set precedence 3RP/0/RP0/CPU0:router(config-pmap-c)# exitRP/0/RP0/CPU0:router(config-pmap)# class class-defaultRP/0/RP0/CPU0:router(config-pmap-c)# queue-limit bytes 1000000Related Commands
priority (QoS)
To assign a priority to a class of traffic belonging to a policy map, use the priority command in policy map class configuration mode. To remove a previously specified priority for a class, use the no form of this command.
priority
no priority
Syntax Description
This command has no keywords or arguments.
Defaults
No default behavior or values
Command Modes
Policy map class configuration
Command History
Usage Guidelines
To use this command, you must be in a user group associated with a task group that includes the proper task IDs. For detailed information about user groups and task IDs, see the Configuring AAA Services on Cisco IOS XR Software module of the Cisco IOS XR System Security Configuration Guide.
The priority command configures low latency queueing (LLQ), providing strict priority queueing (PQ). Strict PQ allows delay-sensitive data such as voice to be dequeued and sent before packets in other queues are dequeued. When a class is marked as high priority using the priority command, we recommend that you configure a policer to limit the priority traffic. This policer ensures that the priority traffic does not starve all other traffic on the line card, which protects low-priority traffic from starvation. Use the police command to explicitly configure the policer.
The priority command sets up classes based on a variety of criteria (not just User Datagram Protocol [UDP] ports) and assigns a priority to them.
The bandwidth and priority commands cannot be used in the same class, within the same policy map. These commands can be used together in the same policy map, however.
Within a policy map, you can give one or more classes priority status. When multiple classes within a single policy map are configured as priority classes, all traffic from these classes is queued to the same, single, priority queue.
Task ID
Examples
The following example shows how to configure priority queuing for the policy map named policy1:
RP/0/RP0/CPU0:router(config)# policy-map policy1RP/0/RP0/CPU0:router(config-pmap)# class class1RP/0/RP0/CPU0:router(config-pmap-c)# priorityRelated Commands
queue-limit
To specify or modify the maximum number of packets the queue can hold for a class policy configured in a policy map, use the queue-limit command in policy map class configuration mode. To remove the queue packet limit from a class, use the no form of this command.
queue-limit value [units]
no queue-limit value [units]
Syntax Description
Defaults
100 milliseconds: maximum threshold for tail drop
10 ms: maximum threshold for high-priority queues
Maximum threshold units are in packets.
Note
Command Modes
Policy map class configuration
Command History
Usage Guidelines
To use this command, you must be in a user group associated with a task group that includes the proper task IDs. For detailed information about user groups and task IDs, see the Configuring AAA Services on Cisco IOS XR Software module of the Cisco IOS XR System Security Configuration Guide.
Packets satisfying the match criteria for a class accumulate in the queue reserved for the class until they are serviced by the scheduling mechanism. The queue-limit command defines the maximum threshold for a class. When that threshold is reached, enqueued packets to the class queue result in tail drop (packet drop). Tail drop is a congestion avoidance technique that drops packets when an output queue is full, until congestion is eliminated.
Use the show qos interface command to display the queue limit and other policer values.
Queue Limit Default Values
The following default values are used when queue-limit is not configured in the class:
•
–
•
–
Queue limit is 100 ms at the guaranteed service rate of the queue for non-priority queues.
Queue limit is 10 ms at the interface rate for Level 1 priority classes.
Queue limit is 10 ms at parent guaranteed service rate for Level 2 priority classes.
–
Queue limit is two times the WRED maximum threshold. The maximum threshold can be an explicitly configured value or an implicit 100 ms.
If more than one WRED profile is configured in the class, the maximum threshold is the maximum for all profiles.
When the queue-limit is configured in time units, the guaranteed service rate is used to compute the queue limit.
When the queue limit is configured in time units, the guaranteed service rate of the class is used to calculate the queue limit in bytes. For example:
time_unit in ms * guaranteed_service_rate in kbps / 8 is equivalent to queue-limit in bytes.
The following restrictions apply to queue limits:
•
•
•
Guaranteed Service Rate
The guaranteed service rate is defined as the service rate of the queue when all queues are backlogged and derived as:
minimum_bandwidth + (bandwidth_remaining_percent * unallocated_bandwidth)
The following example shows the guaranteed service rate calculation:
policy-map sample_policyclass c1bandwidth percent 30bandwidth remaining percent 40class c2bandwidth percent 20class class-defaultguaranteed service rate of c1 = 30 % LR + (40% * 50% * LR )
guaranteed service rate of c2 = 20 % LR + (30% * 50% * LR)
guaranteed service rate of class-default = 30% * 50% * LR
*where LR is line rate of the target on which service policy "sample_policy" is attached.
*50% is unallocated bandwidth.
Task ID
Examples
The following example shows how to set the queue limit for a class to 1000000 packets for policy map policy1:
RP/0/RP0/CPU0:router(config)# policy-map policy1RP/0/RP0/CPU0:routers(config-pmap)# class class1RP/0/RP0/CPU0:router(config-pmap-c)# queue-limit 1000000Related Commands
random-detect
To enable random early detection (RED), use the random-detect command in policy map class configuration mode. To return the thresholds to the default, use the no form of this command.
random-detect {default | min-threshold [units] max-threshold [units]}
no random-detect {default | min-threshold [units] max-threshold [units]}
Syntax Description
Defaults
Default unit for max-threshold and min-threshold is packets.
Command Modes
Policy map class configuration
Command History
Usage Guidelines
To use this command, you must be in a user group associated with a task group that includes the proper task IDs. For detailed information about user groups and task IDs, see the Configuring AAA Services on Cisco IOS XR Software module of the Cisco IOS XR System Security Configuration Guide.
The RED congestion avoidance technique takes advantage of the congestion control mechanism of TCP. By randomly dropping packets before periods of high congestion, RED tells the packet source to decrease its transmission rate. Assuming the packet source is using TCP, it decreases its transmission rate until all the packets reach their destination, indicating that the congestion is cleared. You can use RED as a way to cause TCP to slow transmission of packets. TCP not only pauses, but it also restarts quickly and adapts its transmission rate to the rate that the network can support.
RED distributes losses in time and maintains normally low queue depth while absorbing traffic bursts. When enabled on an interface, RED begins dropping packets when congestion occurs at a rate you select during configuration.
When time units are used, the guaranteed service rate is used to compute thresholds.
The default values for RED are calculated as follows:
default min_threshold = 0.03 * B
default max_threshold = 0.1 * B
where B is the bandwidth for the queue. When all the queues are conjested, the bandwidth for the queue is equal to the guaranteed service rate of the queue.
The mark probability is always set to 1.
When the units are packets, packets are assumed to be 256 bytes in size.
Weighted Random Early Detection
The following restrictions apply to weighted random early detection (WRED):
•
•
•
For bundles, queue limit and WRED thresholds are supported in time units only.
Note
Task ID
Examples
The following example shows how to enable RED using a minimum threshold value of 1000000 and a maximum threshold value of 2000000:
RP/0/RP0/CPU0:router(config)# policy-map policy1RP/0/RP0/CPU0:router(config-pmap)# class class1RP/0/RP0/CPU0:router(config-pmap-c)# random-detect 1000000 2000000Related Commands
random-detect cos
To configure Weighted random early detection (WRED) thresholds for packets with a specific class of service (CoS) value, use the random-detect cos command in policy map class configuration mode. To return the thresholds to the default for the CoS, use the no form of this command.
random-detect cos {cos-value min-threshold} [units] max-threshold [units]
no random-detect cos
Syntax Description
Defaults
Default unit for max-threshold and min-threshold is packets.
min-threshold: 30 ms
max-threshold: 100 msCommand Modes
Policy map class configuration
Command History
Usage Guidelines
To use this command, you must be in a user group associated with a task group that includes the proper task IDs. For detailed information about user groups and task IDs, see the Configuring AAA Services on Cisco IOS XR Software module of the Cisco IOS XR System Security Configuration Guide.
The random-detect cos command is allowed in a service policy attached to Layer 2 VPN attachment circuit or physical Ethernet interface only. (The command in invalid in a policy attached to Layer 3 interface.)
Note
When the units are packets, packets are assumed to be 256 bytes in size.
Task ID
.Examples
The following example shows how to configure CoS:
RP/0/RP0/CPU0:router(config)# policy-map map1RP/0/RP0/CPU0:router(config-pmap)# class cRP/0/RP0/CPU0:router(config-pmap-c)# random-detect cos 3 1000 bytes 2000 bytesRelated Commands
random-detect discard-class
To configure the Weighted Random Early Detection (WRED) thresholds for packets with a specific discard class value, use the random-detect discard-class command in policy map class configuration mode. To return the thresholds to the default for the discard class, use the no form of this command.
random-detect discard-class {discard-value min-threshold} [units] max-threshold [units]
no random-detect discard-class
Syntax Description
Defaults
Default unit for max-threshold and min-threshold is packets.
Command Modes
Policy map class configuration
Command History
Usage Guidelines
To use this command, you must be in a user group associated with a task group that includes the proper task IDs. For detailed information about user groups and task IDs, see the Configuring AAA Services on Cisco IOS XR Software module of the Cisco IOS XR System Security Configuration Guide.
WRED is a congestion avoidance mechanism that slows traffic by randomly dropping packets when congestion exists. WRED is most useful with protocols like TCP that respond to dropped packets by decreasing the transmission rate.
When you configure the random-detect discard-class command on an interface, packets are given preferential treatment based on the discard class of the packet.
When the units are packets, packets are assumed to be 256 bytes in size.
Task ID
.Examples
The following example shows how to set the discard class values for discard class 3 to a minimum byte threshold of 1000000 and a maximum byte threshold of 2000000:
RP/0/RP0/CPU0:router(config)# policy-map policy1RP/0/RP0/CPU0:router(config-pmap)# class class1RP/0/RP0/CPU0:router(config-pmap-c)# random-detect discard-class 3 1000000 2000000Related Commands
random-detect dscp
To configure the Weighted Random Early Detection (WRED) thresholds for packets with a specific differentiated services code point (DSCP) value, use the random-detect dscp command in policy map class configuration mode. To return the thresholds to the default for the DSCP value, use the no form of this command.
random-detect dscp {dscp-value min-threshold} [units] max-threshold [units]
no random-detect dscp
Syntax Description
dscp-value
DSCP value. Up to eight dscp-values (any combination of numbers, ranges, and reserved keywords) can be used separated by commas. The following arguments are supported:
•
•
•
Note
min-threshold
Minimum threshold in number of packets. The value range of this argument is from 0 to 1073741823. When the average queue length reaches the minimum threshold, Weighted Random Early Detection (WRED) randomly drops some packets with the specified DSCP value.
max-threshold
Maximum threshold in number of packets. The value range of this argument is from the value of the min-threshold argument to 1073741823. When the average queue length exceeds the maximum threshold, WRED drops all packets with the specified DSCP value.
units
(Optional) Units for the threshold values. Values can be:
•
•
•
•
•
•
•
•
Defaults
Match packets with default dscp (000000).
Default unit for max-threshold and min-threshold is packets.
Command Modes
Policy map class configuration
Command History
Usage Guidelines
To use this command, you must be in a user group associated with a task group that includes the proper task IDs. For detailed information about user groups and task IDs, see the Configuring AAA Services on Cisco IOS XR Software module of the Cisco IOS XR System Security Configuration Guide.
WRED is a congestion avoidance mechanism that slows traffic by randomly dropping packets when congestion exists. WRED is most useful with protocols like TCP that respond to dropped packets by decreasing the transmission rate.
For the random-detect dscp command to take effect on the Cisco XR 12000 Series Router, you must configure both the shape average and bandwidth commands in the policy map class.
Reserved keywords can be specified instead of numeric values. See Table 1 for the list of keywords.
When the units are packets, packets are assumed to be 256 bytes in size.
Task ID
Examples
The following example shows that for packets with DSCP AF11, the WRED minimum threshold is 1,000,000 bytes and the maximum threshold is 2,000,000 bytes:
RP/0/RP0/CPU0:router(config)# policy-map policy1RP/0/RP0/CPU0:router(config-pmap)# class class1RP/0/RP0/CPU0:router(config-pmap-c)# random-detect dscp AF11 1000000 2000000Related Commands
random-detect exp
To configure the Weighted Random Early Detection (WRED) thresholds for packets marked with a specific MPLS experimental (EXP) bit value, use the random-detect exp command in policy map class configuration mode. To return the value to the default, use the no form of this command.
random-detect exp {exp-value min-threshold} [units] max-threshold [units]
no random-detect exp
Syntax Description
Defaults
Default unit for max-threshold and min-threshold is packets.
Command Modes
Policy map class configuration
Command History
Usage Guidelines
To use this command, you must be in a user group associated with a task group that includes the proper task IDs. For detailed information about user groups and task IDs, see the Configuring AAA Services on Cisco IOS XR Software module of the Cisco IOS XR System Security Configuration Guide.
WRED is a congestion avoidance mechanism that slows traffic by randomly dropping packets when congestion exists. WRED is most useful with protocols like TCP that respond to dropped packets by decreasing the transmission rate.
When the units are packets, packets are assumed to be 256 bytes in size.
Task ID
Examples
The following example shows that for Multiprotocol Label Switching (MPLS) packets with an EXP field value of 4, the WRED minimum threshold is 1,000,000 bytes and the maximum threshold is 2,000,000 bytes:
RP/0/RP0/CPU0:router(config)# policy-map policy1RP/0/RP0/CPU0:router(config-pmap)# class class1RP/0/RP0/CPU0:router(config-pmap-c)# random-detect exp 4 1000000 20000Related Commands
random-detect precedence
To configure the Weighted Random Early Detection (WRED) thresholds for packets with a particular IP precedence, use the random-detect precedence command in policy map class configuration mode. To return the thresholds to the default for the precedence, use the no form of this command.
random-detect precedence {precedence-value min-threshold} [units] max-threshold [units]
no random-detect precedence
Syntax Description
precedence-value
An IP precedence value identifier that specifies the exact value. Range is from 0 to 7. Reserved keywords can be specified instead of numeric values. Table 2 describes the reserved keywords. Up to eight values or reserved keywords can be entered separated by commas.
min-threshold
Minimum threshold in number of packets. Range is from 0 to 1073741823 in bytes.
max-threshold
Maximum threshold in the units specified. Range is from the value of the min-threshold argument to 1073741823. When the average queue length exceeds the maximum threshold, WRED drops all packets with the specified precedence value.
units
(Optional) Units for the threshold values. Values can be:
•
•
•
•
•
•
•
•
Defaults
Default unit for max-threshold and min-threshold is packets.
Command Modes
Policy map class configuration
Command History
Usage Guidelines
To use this command, you must be in a user group associated with a task group that includes the proper task IDs. For detailed information about user groups and task IDs, see the Configuring AAA Services on Cisco IOS XR Software module of the Cisco IOS XR System Security Configuration Guide.
WRED is a congestion avoidance mechanism that slows traffic by randomly dropping packets when congestion exists. WRED is most useful with protocols like TCP that respond to dropped packets by decreasing the transmission rate.
When you configure the random-detect command on an interface, packets are given preferential treatment based on the IP precedence of the packet. Use the random-detect precedence command to adjust the treatment for different precedences.
When the units are packets, packets are assumed to be 256 bytes in size.
Task ID
Examples
The following example shows that for packets with precedence 3, the WRED minimum threshold is 1,000,000 bytes and maximum threshold is 2,000,000 bytes:
RP/0/RP0/CPU0:router(config)# policy-map policy1RP/0/RP0/CPU0:router(config-pmap)# class class1RP/0/RP0/CPU0:router(config-pmap-c)# random-detect precedence 3 1000000 2000000Related Commands
service-policy (interface)
To attach a policy map to an input interface or output interface to be used as the service policy for that interface, use the service-policy command in the appropriate configuration mode. To remove a service policy from an input or output interface, use the no form of this command.
service-policy {input | output} policy-map
no service-policy {input | output}
Syntax Description
Defaults
No service policy is specified.
Command Modes
Interface configuration
Layer 2 transport configurationCommand History
Usage Guidelines
To use this command, you must be in a user group associated with a task group that includes the proper task IDs. For detailed information about user groups and task IDs, see the Configuring AAA Services on Cisco IOS XR Software module of the Cisco IOS XR System Security Configuration Guide.
You can attach a single policy map to one or more interfaces to specify the service policy for those interfaces. The class policies composing the policy map are then applied to packets that satisfy the class map match criteria for the class. To apply a new policy to an interface, you must remove the previous policy. A new policy cannot replace an existing policy.
Task ID
Examples
The following example shows policy map policy1 applied to Packet-over-SONET/SDH (POS) interface 0/2/0/0:
RP/0/RP0/CPU0:router(config)# class class1RP/0/RP0/CPU0:router(config-cmap)# match precedence ipv4 1RP/0/RP0/CPU0:router(config-cmap)# exitRP/0/RP0/CPU0:router(config)# policy policy1RP/0/RP0/CPU0:router(config-pmap)# class class1RP/0/RP0/CPU0:router(config-pmap-c)# set precedence 2RP/0/RP0/CPU0:router(config-pmap)# exitRP/0/RP0/CPU0:router(config)# interface pos 0/2/0/0RP/0/RP0/CPU0:router(config-if)# service-policy output policy1Related Commands
service-policy (policy map class)
To use a service policy as a QoS policy within a policy map (called a hierarchical service policy), use the service-policy command in policy map class configuration mode. To disable a particular service policy as a QoS policy within a policy map, use the no form of this command.
service-policy [type qos] policy-map-name
no service-policy [type qos] policy-map-name
Syntax Description
Defaults
No service policy is specified.
Type is QoS when not specified.Command Modes
Policy map class configuration
Command History
Usage Guidelines
To use this command, you must be in a user group associated with a task group that includes the proper task IDs. For detailed information about user groups and task IDs, see the Configuring AAA Services on Cisco IOS XR Software module of the Cisco IOS XR System Security Configuration Guide.
The service-policy (policy-map class) command creates hierarchical service policies in policy-map class configuration mode.
This command is different from the service-policy (interface) command used in interface configuration mode.
The child policy is the previously defined service policy that is being associated with the class default of the parent policy-map. The new service policy using the preexisting service policy is the parent policy.
The service-policy (policy-map class) command has the following restrictions:
•
•
Task ID
Examples
The following example shows how to create a hierarchical service policy in the service policy called parent:
RP/0/RP0/CPU0:router(config)# policy-map childRP/0/RP0/CPU0:router(config-pmap)# class class1RP/0/RP0/CPU0:router(config-pmap-c)# priorityRP/0/RP0/CPU0:router(config-pmap-c)# exitRP/0/RP0/CPU0:router(config-pmap)# exitRP/0/RP0/CPU0:router(config)# policy-map parentRP/0/RP0/CPU0:router(config-pmap)# class class-defaultRP/0/RP0/CPU0:router(config-pmap-c)# shape average 10000000RP/0/RP0/CPU0:router(config-pmap-c)# service-policy childRelated Commands
set atm-clp
To set the cell loss priority (CLP) bit when a policy map is configured, use the set atm-clp command in policy map class configuration mode. To remove a specific CLP bit setting, use the no form of this command.
set atm-clp
no set atm-clp
Syntax Description
This command has no arguments or keywords.
Defaults
The CLP bit is automatically set to 0 when Cisco routers convert IP packets into ATM cells for transmission through Multiprotocol Label Switching (MPLS)-aware ATM networks.
Command Modes
Policy map class configuration
Command History
Release 3.4.0
This command was introduced on the Cisco XR 12000 Series Router.
Release 3.5.0
No modification.
Release 3.6.0
No modification.
Release 3.7.0
No modification.
Usage Guidelines
To use this command, you must be in a user group associated with a task group that includes the proper task IDs. For detailed information about user groups and task IDs, see the Configuring AAA Services on Cisco IOS XR Software module of the Cisco IOS XR System Security Configuration Guide.
The set atm-clp command sets the CLP bit within the packet. After the CLP bit is set, other QoS services such as Modified Deficit Round Robin (MDRR) and Weighted Random Early Detection (WRED) can operate on the bit settings.
A policy map containing the set atm-clp command can be attached as an output policy only. The set atm-clp command does not support packets that originate from the router.
Task ID
Examples
The following example illustrates setting the CLP bit using the set atm-clp command in the policy map:
RP/0/0/CPU0:router(config)# class-map c1RP/0/0/CPU0:router(config-cmap)# match precedence ipv4 0 1RP/0/0/CPU0:router(config-cmap)# exitRP/0/0/CPU0:router(config)# policy-map atm-clp-setRP/0/0/CPU0:router(config-pmap)# class c1RP/0/0/CPU0:router(config-pmap-c)# set atm-clpRP/0/0/CPU0:router(config-pmap-c)# exitRP/0/0/CPU0:router(config-pmap)# exitRP/0/0/CPU0:router(config)# interface atm 0/2/0/0.1RP/0/0/CPU0:router(config-subif)# pvc 10/100RP/0/0/CPU0:router(config-atm-vc)# service-policy output atm-clp-setRP/0/0/CPU0:router(config-atm-vc)# endRelated Commands
set cos
To set the Layer 2 class of service (CoS) value of an outgoing packet, use the set cos command in policy map class configuration mode. To remove a specific CoS value setting, use the no form of this command.
set cos cos-value
no set cos cos-value
Syntax Description
Defaults
No Layer 2 CoS value of an outgoing packet is set.
Command Modes
Policy map class configuration
Command History
Usage Guidelines
To use this command, you must be in a user group associated with a task group that includes the proper task IDs. For detailed information about user groups and task IDs, see the Configuring AAA Services on Cisco IOS XR Software module of the Cisco IOS XR System Security Configuration Guide.
Use the set cos command to mark a packet that is being sent to a switch. Switches can leverage Layer 2 header information, including a CoS value marking.
The set cos command can be used only in service policies that are attached in the output direction of an interface. Packets entering an interface cannot be set with a CoS value.
Task ID
Examples
In the following example, the policy map called cos-set is created to assign different CoS values for different types of traffic, and then is attached to output Packet-over-SONET/SDH interface 0/2/0/0.
RP/0/RP0/CPU0:router(config)# policy-map cos-setRP/0/RP0/CPU0:router(config-pmap)# class class1RP/0/RP0/CPU0:router(config-pmap-c)# set cos 1RP/0/RP0/CPU0:router(config-pmap-c)# exitRP/0/RP0/CPU0:router(config-pmap)# class class2RP/0/RP0/CPU0:router(config-pmap-c)# set cos 2RP/0/RP0/CPU0:router(config-pmap-c)# exitRP/0/RP0/CPU0:router(config-pmap)# exitRP/0/RP0/CPU0:router(config)# interface pos 0/2/0/0RP/0/RP0/CPU0:router(config-if)# service-policy output cos-setRelated Commands
set discard-class
To set the discard class and Quality of Service (QoS) group identifiers on IP Version 4 (IPv4) or Multiprotocol Label Switching (MPLS) packets, use the set discard-class command in policy map class configuration mode. To leave the discard-class values unchanged, use the no form of this command.
set discard-class discard-class-value [qos-group group-value]
no set discard-class discard-class-value [qos-group group-value]
Syntax Description
Defaults
No group ID is specified.
Command Modes
Policy map class configuration
Command History
Usage Guidelines
To use this command, you must be in a user group associated with a task group that includes the proper task IDs. For detailed information about user groups and task IDs, see the Configuring AAA Services on Cisco IOS XR Software module of the Cisco IOS XR System Security Configuration Guide.
The set discard-class command associates a discard class ID with a packet. After the discard class and QoS group IDs are set, other QoS services such as Modified Deficit Round Robin (MDRR) and Weighted Random Early Detection (WRED) can operate on the bit settings.
Discard-class indicates the discard portion of the per hop behavior (PHB). The set discard-class command is typically used in Pipe mode. Discard-class is required when the input PHB marking will be used to classify packets on the output interface.
The discard-class values can be used to specify the type of traffic that is dropped when there is congestion.
Note
Task ID
Examples
The following example shows how to set the discard class value to 5 for packets that match the MPLS experimental bits 1:
RP/0/RP0/CPU0:router(config)# class-map cust1RP/0/RP0/CPU0:router(config-cmap)# match mpls experimental topmost 1RP/0/RP0/CPU0:router(config-cmap)# exitRP/0/RP0/CPU0:router(config)# policy-map policy2RP/0/RP0/CPU0:router(config-pmap)# class cust1RP/0/RP0/CPU0:router(config-pmap-c)# set discard-class 5RP/0/RP0/CPU0:router(config-pmap-c)# exitRP/0/RP0/CPU0:router(config-pmap)# exitRP/0/RP0/CPU0:router(config)# interface pos 0/7/0/0RP/0/RP0/CPU0:router(config-if)# service-policy input policy2Related Commands
set dscp
To mark a packet by setting the IP differentiated services code point (DSCP) in the type of service (ToS) byte, use the set dscp command in policy-map class configuration mode. To remove a previously set DSCP value, use the no form of this command.
set dscp [tunnel] dscp-value
no set dscp dscp-value
Syntax Description
tunnel
(Optional) Sets the DSCP on the outer IP header. This option is available for IPSec on the Cisco XR 12000 Series Router only.
dscp-value
Number from 0 to 63 that sets the DSCP value. Reserved keywords can be specified instead of numeric values. Table 1 describes the reserved keywords.
Defaults
No default behavior or values
Command Modes
Policy map class configuration
Command History
Usage Guidelines
To use this command, you must be in a user group associated with a task group that includes the proper task IDs. For detailed information about user groups and task IDs, see the Configuring AAA Services on Cisco IOS XR Software module of the Cisco IOS XR System Security Configuration Guide.
After the DSCP bit is set, other quality-of-service (QoS) services can then operate on the bit settings.
The network gives priority (or some type of expedited handling) to marked traffic. Typically, you set the DSCP value at the edge of the network (or administrative domain); data then is queued based on the DSCP value. Modified Deficit Round Robin (MDRR) can speed up handling for high DSCP traffic at congestion points. Weighted Random Early Detection (WRED) ensures that high DSCP traffic has lower loss rates than other traffic during times of congestion.
Reserved keywords can be specified instead of numeric values. Table 1 describes the reserved keywords.
Task ID
Examples
In the following example, the DSCP ToS byte is set to 8 in the policy map called policy1. All packets that satisfy the match criteria of class1 are marked with the DSCP value of 8. The network configuration determines how packets are marked.
RP/0/RP0/CPU0:router(config)# policy-map policy1RP/0/RP0/CPU0:router(config-pmap)# class class1RP/0/RP0/CPU0:router(config-pmap-c)# set dscp 8Related Commands
set mpls experimental
To set the experimental (EXP) value of the Multiprotocol Label Switching (MPLS) packet topmost or imposition labels, use the set mpls experimental command in policy map configuration mode. To leave the EXP value unchanged, use the no form of this command.
set mpls experimental {imposition | topmost} exp-value
no set mpls experimental {imposition | topmost} exp-value
Syntax Description
imposition
Specifies to set the EXP value of the imposition label.
topmost
Specifies to set the EXP value of the topmost label.
exp-value
Value of the MPLS packet label. Range is 0 to 7.
Defaults
No MPLS experimental value is set
Command Modes
Policy map class configuration
Command History
Usage Guidelines
To use this command, you must be in a user group associated with a task group that includes the proper task IDs. For detailed information about user groups and task IDs, see the Configuring AAA Services on Cisco IOS XR Software module of the Cisco IOS XR System Security Configuration Guide.
After the MPLS experimental bits are set, other QoS services such as modified deficit round robin (MDRR) and Weighted Random Early Detection (WRED) then operate on the bit settings.
The network gives priority (or some type of expedited handling) to the marked traffic through the application of MDRR or WRED at points downstream in the network. Typically, the MPLS experimental value is set at the edge of the network (or administrative domain) and queueing is acted on it thereafter. MDRR can speed up handling for high-priority traffic at congestion points. WRED ensures that high-priority traffic has lower loss rates than other traffic during times of congestion.
Task ID
.Examples
The following example shows how to set the MPLS experimental to 5 for packets that match access list 101:
RP/0/RP0/CPU0:router(config)# class-map class1RP/0/RP0/CPU0:router(config-cmap)# match access-group acl101RP/0/RP0/CPU0:router(config-cmap)# exitRP/0/RP0/CPU0:router(config)# policy-map policy1RP/0/RP0/CPU0:router(config-pmap)# class class1RP/0/RP0/CPU0:router(config-pmap-c)# set mpls experimental topmost 5RP/0/RP0/CPU0:router(config-pmap-c)# exitRP/0/RP0/CPU0:router(config-pmap)# exitRP/0/RP0/CPU0:router(config)# interface pos 0/7/0/0RP/0/RP0/CPU0:router(config-if)# service-policy output policy1Related Commands
set precedence
To set the precedence value in the IP header, use the set precedence command in policy map class configuration mode. To leave the precedence value unchanged, use the no form of this command.
set precedence [tunnel] value
no set precedence [tunnel] value
Syntax Description
tunnel
(Optional) Sets the IP precedence on the outer IP header. This option is available for IPSec on the Cisco XR 12000 Series Router only.
value
Number or name that sets the precedence bits in the IP header. Range is from 0 to 7. Reserved keywords can be specified instead of numeric values. Table 2 describes the reserved keywords.
Defaults
Marking is not configured.
Command Modes
Policy map class configuration
Command History
Usage Guidelines
To use this command, you must be in a user group associated with a task group that includes the proper task IDs. For detailed information about user groups and task IDs, see the Configuring AAA Services on Cisco IOS XR Software module of the Cisco IOS XR System Security Configuration Guide.
Precedence can be set using a number or corresponding name. After IP Precedence bits are set, other QoS services such as Modified Deficit Round Robin (MDRR) and Weighted Random Early Detection (WRED) then operate on the bit settings.
The network gives priority (or some type of expedited handling) to the marked traffic through the application of MDRR or WRED at points downstream in the network. IP precedence can be set at the edge of the network (or administrative domain) and have queueing act on it thereafter. MDRR can speed handling for high-precedence traffic at congestion points. WRED ensures that high-precedence traffic has lower loss rates than other traffic during times of congestion.
The mapping from keywords such as 0 (routine) and 1 (priority) to a precedence value is useful only in some instances. That is, the use of the precedence bit is evolving. You can define the meaning of a precedence value by enabling other features that use the value. In the case of high-end Internet QoS, IP precedences can be used to establish classes of service that do not necessarily correspond numerically to better or worse handling in the network.
Task ID
Examples
The following example shows how to set the IP precedence to 5 (critical) for packets that match the access control list named customer1:
RP/0/RP0/CPU0:router(config)# class-map class1RP/0/RP0/CPU0:router(config-cmap)# match access-group customer1RP/0/RP0/CPU0:router(config-cmap)# exitRP/0/RP0/CPU0:router(config)# policy-map policy1RP/0/RP0/CPU0:router(config-pmap)# class class1RP/0/RP0/CPU0:router(config-pmap-c)# set precedence 5RP/0/RP0/CPU0:router(config-pmap-c)# exitRP/0/RP0/CPU0:router(config-pmap)# exitRP/0/RP0/CPU0:router(config)# interface pos 0/7/0/0RP/0/RP0/CPU0:router(config-if)# service-policy output policy1Related Commands
set qos-group
To set the quality of service (QoS) group identifiers on packets, use the set qos-group command in policy map class configuration mode. To leave the QoS group values unchanged, use the no form of this command.
set qos-group qos-group-value [discard-class discard-class-value]
no set qos-group qos-group-value [discard-class discard-class-value]
Syntax Description
Defaults
No group ID is specified.
Command Modes
Policy map class configuration
Command History
Usage Guidelines
To use this command, you must be in a user group associated with a task group that includes the proper task IDs. For detailed information about user groups and task IDs, see the Configuring AAA Services on Cisco IOS XR Software module of the Cisco IOS XR System Security Configuration Guide.
The set qos-group command associates a QoS group ID with a packet. After the QoS group ID is set, other QoS services, such as Modified Deficit Round Robin (MDRR) and Weighted Random Early Detection (WRED), can operate on the QoS group setting.
The QoS group setting is limited in scope to the local router. Typically, the QoS group is set on the local router and used in conjunction with WRED or MDRR to give differing levels of service based on the group identifier.
Task ID
Examples
The following example sets the QoS group to 5 for packets that match the MPLS experimental bits 1:
RP/0/RP0/CPU0:router(config)# class-map class1RP/0/RP0/CPU0:router(config-cmap)# match mpls experimental topmost 1RP/0/RP0/CPU0:router(config-cmap)# exitRP/0/RP0/CPU0:router(config)# policy-map policy1RP/0/RP0/CPU0:router(config-pmap)# class class1RP/0/RP0/CPU0:router(config-pmap-c)# set qos-group 5RP/0/RP0/CPU0:router(config-pmap-c)# exitRP/0/RP0/CPU0:router(config-pmap)# exitRP/0/RP0/CPU0:router(config)# interface pos 0/7/0/0RP/0/RP0/CPU0:router(config-if)# service-policy input policy1Related Commands
set srp-priority
To set the Spatial Reuse Protocol (SRP) priority value of an outgoing packet, use the set srp-priority command in policy map class configuration mode. To remove a specific SRP priority setting, use the no form of this command.
set srp-priority {priority-value}
no set srp-priority {priority-value}
Syntax Description
Defaults
No SRP CoS value of an outgoing packet is set.
Command Modes
Policy map class configuration
Command History
Usage Guidelines
To use this command, you must be in a user group associated with a task group that includes the proper task IDs. For detailed information about user groups and task IDs, see the Configuring AAA Services on Cisco IOS XR Software module of the Cisco IOS XR System Security Configuration Guide.
The set srp-priority command can be used only in service policies that are attached in the output direction of an interface.
Task ID
.Examples
In the following example, the policy map called srp-set is created to assign different SRP CoS values for different types of traffic, and then is attached to output SRP interface 0/2/0/0:
RP/0/RP0/CPU0:router(config)# policy-map srp-setRP/0/RP0/CPU0:router(config-pmap)# class class1RP/0/RP0/CPU0:router(config-pmap-c)# set srp-priority 5RP/0/RP0/CPU0:router(config-pmap-c)# exitRP/0/RP0/CPU0:router(config-pmap)# exitRP/0/RP0/CPU0:router(config)# interface srp 0/2/0/0RP/0/RP0/CPU0:router(config-if)# service-policy output srp-setRelated Commands
shape average
To shape traffic to the indicated bit rate according to the algorithm specified, use the shape average command in policy map class configuration mode. To remove traffic shaping, use the no form of this command.
shape average {percent percentage | rate [units]} [burst-size [burst-units]]
no shape average {percent percentage | rate [units]} [burst-size [burst-units]]
Syntax Description
Defaults
units: bps
Command Modes
Policy map class configuration
Command History
To use this command, you must be in a user group associated with a task group that includes the proper task IDs. For detailed information about user groups and task IDs, see the Configuring AAA Services on Cisco IOS XR Software module of the Cisco IOS XR System Security Configuration Guide.
When you use the shape average command on the Cisco CRS-1, egress shaping is done at the Layer 2 level and includes the Layer 2 header in the rate calculation. Ingress shaping is done at the Layer 3 level and does not include the Layer 2 header in the rate calculation. Shaping is performed in multiples of 256 kbps, the minimum shaping rate.
When using this command on the Cisco XR 12000 Series Router, egress and ingress shaping is performed in multiples of 64 kbps on the Layer 3 level.
For shape average commands in the child policy, the reference used for percentage parameters is relative to the maximum rate of the parent. If shaping or policing is not configured on the parent, then the parent inherits the interface rate.
For bundled interfaces, shape average can be configured only as a percentage.
If you have both shape and bandwidth configured for a class, ensure that the shape percent value is always greater than the percent value for bandwidth.
Task ID
.Examples
The following example sets traffic shaping to 50 milliseconds:
RP/0/RP0/CPU0:router(config)# policy-map policy1RP/0/RP0/CPU0:router(config-pmap)# class class1RP/0/RP0/CPU0:router(config-pmap-c)# shape average percent 50The following example shows how to set traffic shaping to 5,000,000 kbps:
RP/0/RP0/CPU0:router(config)# policy-map policy1RP/0/RP0/CPU0:router(config-pmap)# class class1RP/0/RP0/CPU0:router(config-pmap-c)# shape average 5000000 kbpsshow fmgr interface
To display ternary content addressable memory (TCAM) feature entries for QoS, use the show fmgr interface command in EXEC mode.
show fmgr interface type instance feature {fabqos | policer | qos | qos-all} {input | output} [[hw | sw] [all | ipv4-mpls | ipv6 | l2] [dup-bank] [location node-id]]
Syntax Description
Defaults
No default behavior or values
Command Modes
EXEC
Command History
Usage Guidelines
To use this command, you must be in a user group associated with a task group that includes the proper task IDs. For detailed information about user groups and task IDs, see the Configuring AAA Services on Cisco IOS XR Software module of the Cisco IOS XR System Security Configuration Guide.
Task ID
Examples
The following sample output shows how to display all ingress QoS and policer TCAM entries for a Gigabit Ethernet interface:
RP/0/RP0/CPU0:router# show fmgr interface GigabitEthernet 0/1/5/0 feature qos-all inQOS ENTRIES===============================================================================Interface = GigabitEthernet0_1_5_0 Feature = qos Direction = inTCAM Fields:ip/mpls bndl vlg_id cid dscp exp dc qos-idCSRAM Fields:prio sh_q red_ctr qos_grp dc l2_mark l3_mark l3_mark_val max_th seg_size min_th1st_seg pol_has_hpq===============================================================================No QoS configured on this interfacePOLICER ENTRIES===============================================================================Interface = GigabitEthernet0_1_5_0 Feature = policer Direction = inTCAM Fields:IPv4: ip/mpls vlg_id l2_cos drid ip_src l4_proto frag dscp ip_dest qos_grp dc dst_port qos-idMPLS: ip/mpls vlg_id l2_cos label exp qos_grp dc qos-idCSRAM Fields:cid token1 stats_ptr conform1 exceed1 violate1 token2 conform2 exceed2 violate2===============================================================================No QoS configured on this interfacePOLICER ENTRIES===============================================================================Interface = GigabitEthernet0_1_5_0 Feature = policer Direction = inTCAM Fields:IPv6: ipv6 vlg_id l2_cos dest_port src_port ip_dest ip_src ext_dst ext_rtg ext_h ext_frag dest_rng_id dc qos_grp l4_proto dscp/prec qos-idCSRAM Fields:cid token1 stats_ptr conform1 exceed1 violate1 token2 conform2 exceed2 violate2===============================================================================No QoS configured on this interfaceRP/0/RP0/CPU0:router#Table 4 describes the significant fields shown in the display.
show hw-module multicast qos
To display the multicast QoS group information, use the show hw-module multicast qos command in EXEC mode.
show hw-module multicast qos [group-info [port] location node-id | queue-info [type instance] location node-id | wred location node-id]
Syntax Description
Defaults
No default behavior or values
Command Modes
EXEC
Command History
Usage Guidelines
To use this command, you must be in a user group associated with a task group that includes the proper task IDs. For detailed information about user groups and task IDs, see the Configuring AAA Services on Cisco IOS XR Software module of the Cisco IOS XR System Security Configuration Guide.
If you do not enter a node-id argument, all configured interfaces are displayed.
Task ID
Examples
The following sample output shows how to display QoS information about for Packet-over-SONET/SDH (POS) interface 0/7/0/3:
RP/0/RP0/CPU0:router# show hw-module multicast qosPOS 0/7/0/3 output: p1Class c1Matched (packets/bytes) : 0/0Marked (packets/bytes) : 0/0Table 5 describes the significant fields shown in the display.
Related Commands
show policy-map interface
To display policy configuration information for all classes configured for all service policies on the specified interface, use the show policy-map interface command in EXEC mode.
show policy-map interface type instance [input | output [member type instance]]
Syntax Description
Defaults
No default behavior or values
Command Modes
EXEC
Command History
Usage Guidelines
To use this command, you must be in a user group associated with a task group that includes the proper task IDs. For detailed information about user groups and task IDs, see the Configuring AAA Services on Cisco IOS XR Software module of the Cisco IOS XR System Security Configuration Guide.
The show policy-map interface command displays the statistics for classes in the service policy attached to an interface. The counters displayed after the command is entered are updated only if congestion is present on the interface.
Task ID
Examples
The following sample output shows how to display policy configuration information for all classes on Packet-over-SONET (POS) interface 0/7/0/3 that are in the output and input direction:
RP/0/RP0/CPU0:router# show policy-map interface POS 0/7/0/3POS 0/7/0/3 output: p1Class c1Matched (packets/bytes) : 0/0Marked (packets/bytes) : 0/0Class c2Matched (packets/bytes) : 10/1320POS 0/7/0/3 input: p4Class c3Matched (packets/bytes) : 9/499Marked (packets/bytes) : 0/0Table 6 describes the significant fields shown in the display.
The following sample output shows how to display L2VPN QoS policy statistics information for all classes on TenGigE interface 0/1/0/0 that are in the output direction on the Cisco CRS-1 router:
RP/0/RP0/CPU0:router# show policy-map interface TenGigE 0/1/0/0TenGigE0/1/0/0 output: p1Class c1Classification statistics (packets/bytes) (rate - kbps)Matched : 23571609/1838585502 0Policing statistics (packets/bytes) (rate - kbps)Policed(conform) : 4417095/344533410 84894Policed(exceed) : 13443/1048554 259Policed(violate) : 19141071/1493003538 367877Policed and dropped : 0/0Class c2Classification statistics (packets/bytes) (rate - kbps)Matched : 4660985/363556830 88887Transmitted : 4660985/363556830 88887Total Dropped : 0/0 0Queueing statisticsVital (packets) : 0Queueing statisticsQueue ID : 25High watermark (packets) : 0Inst-queue-len (bytes) : 0Avg-queue-len (bytes) : 0TailDrop Threshold(bytes) : 250000000Taildropped(packets/bytes) : 0/0Class default<similar output as above for default action>
Note
Table 7 describes the significant fields shown in the display.
The following example shows sample output shows when a policy has been suspended on a Cisco XR 12000 Series Router multilink interface:
RP/0/0/CPU0:router#show policy-map interface Multilink 0/2/0/0/201 inputMultilink0/2/0/0/201 input: ps1 suspended by EA: No bandwidthshow qos acl-deny enable
To display the acl-deny information for a particular location, use the show qos acl-deny enable command in the root configuration mode. To disable this functionality, use the no form of this command.
show qos acl-deny enable [location node-id]
no show qos acl-deny enable [location node-id]
Syntax Description
location node-id
Displays the acl-deny function on a node. The node-id argument is entered in the rack/slot/module notation.
Defaults
No default behavior or values
Command Modes
Root configuration
Command History
Release 3.6.0
This command was first introduced on the Cisco XR 12000 Series Router.
Release 3.7.0
No modification.
Usage Guidelines
To use this command, you must be in a user group associated with a task group that includes the proper task IDs. For detailed information about user groups and task IDs, see the Configuring AAA Services on Cisco IOS XR Software module of the Cisco IOS XR System Security Configuration Guide.
This command displays the administration and operational states of the acl-deny function. The operational state dictates the current operational behavior while the administration state dictates the operational state after the next line card (LC) reload.
Task ID
Examples
The following example shows how to display an acl-deny function on 0/0/CPU0:
RP/0/0/RP0/CPU0:router# F14-01RP/0/0/CPU0:F14-01# show qos acl-deny location 0/0/CPU0show qos interface
To display QoS information for a specific interface, use the show qos interface command in EXEC mode.
show qos interface type instance {input | output} [location node-id]
Syntax Description
Defaults
No default behavior or values
Command Modes
EXEC
Command History
Usage Guidelines
To use this command, you must be in a user group associated with a task group that includes the proper task IDs. For detailed information about user groups and task IDs, see the Configuring AAA Services on Cisco IOS XR Software module of the Cisco IOS XR System Security Configuration Guide.
The show qos interface command displays configuration for all classes in the service policy that is attached to an interface.
Use this command to check the actual values programmed in the hardware from the action keywords in the police rate command.
Task ID
Examples
The following sample output shows the L2VPN QoS information on a GigabitEthernet interface running on the Cisco CRS-1 router:
RP/0/RP0/CPU0:router# show qos interface GigabitEthernet 0/2/0/0 outputNOTE:- Configured values are displayed within parenthesesInterface TenGigE0_2_0_0 -- output policyTotal number of classes: 3-------------------------------------------------------Level1 class = c1Egressq Queue ID = 25 (LP queue)Queue belongs to Group = 9Queue Max. BW. = 999936 kbps (10 %)Queue Min. BW. = 0 kbps (default)Weight = 10 (BWR not configured)Shaper burst = 31248 bytesGuaranteed service rate = 1000000 kbpsTailDrop Threshold = 12500000 bytes / 100 ms (default)Policer not configured for this classWRED not configured for this classLevel1 class = c2Egressq Queue ID = 26 (LP queue)Queue belongs to Group = 9Queue Max. BW. = 10000128 kbps (default)Queue Min. BW. = 2000128 kbps (20 %)Weight = 10 (BWR not configured)Guaranteed service rate = 4666666 kbpsTailDrop Threshold = 58333325 bytes / 100 ms (default)Policer not configured for this classWRED not configured for this classLevel1 class = class-defaultEgressq Queue ID = 9 (Group default LP queue)Queue belongs to Group = 9Queue Max. BW. = 10000128 kbps (default)Queue Min. BW. = 0 kbps (default)Weight = 10 (BWR not configured)Guaranteed service rate = 1000000 kbpsTailDrop Threshold = 12500000 bytes / 100 ms (default)Policer slot # = 224Policer committed rate = 1000000 kbps (10 %)Policer conform burst = 2097120 bytes (default)Policer conform action = Just TXPolicer exceed action = DROP PKTWRED not configured for this classTable 8 describes the significant fields shown in the display.
The following example shows sample output displays QoS policy configuration information on a GigabitEthernet interface on the Cisco XR 12000 Series Router:
RP/0/0/CPU0:router# show qos interface GigabitEthernet 0/5/0/0 inputTable 9 describes the significant fields shown in the display.
show qos wred-curve
To display the QoS weighted random early detection (WRED) curve data point information, use the show qos wred-curve command in EXEC mode.
show qos wred-curve {input | output} location node-id
Syntax Description
Defaults
No default behavior or values
Command Modes
EXEC
Command History
Release 3.6.0
This command was introduced on the Cisco CRS-1.
Release 3.7.0
No modification.
Usage Guidelines
To use this command, you must be in a user group associated with a task group that includes the proper task IDs. For detailed information about user groups and task IDs, see the Configuring AAA Services on Cisco IOS XR Software module of the Cisco IOS XR System Security Configuration Guide.
Task ID
Examples
The following example shows how to display QoS WRED curve information:
RP/0/RP0/CPU0:router# show qos wred-curve input location 0/1/0switch-fabric service-policy
To configure a service policy for the switch fabric, use the switch-fabric service-policy command in global configuration mode. To remove a specified service policy from the switch fabric, use the no form of this command.
switch-fabric service-policy policy-map-name
no switch-fabric service-policy policy-map-name
Syntax Description
policy-map-name
Name of the predefined policy map to be used as a QoS policy. The name can be a maximum of 40 alphanumeric characters.
Defaults
No service policy is specified.
Command Modes
Global configuration
Command History
Usage Guidelines
To use this command, you must be in a user group associated with a task group that includes the proper task IDs. For detailed information about user groups and task IDs, see the Configuring AAA Services on Cisco IOS XR Software module of the Cisco IOS XR System Security Configuration Guide.
Task ID
Examples
The following example configures the service policy for policy map1.
RP/0/RP0/CPU0:router# configureRP/0/RP0/CPU0:router(config)# switch-fabric service-policy map1violate-action
To configure the action to take on packets that violate the rate limit, use the violate-action command in policy map police configuration mode. To remove a conform action from the policy-map, use the no form of this command.
violate-action {drop | set options | transmit}
no violate-action {drop | set options | transmit}
Syntax Description
drop
Drops the packet.
set options
Configures the specified packet properties. Replace options with one of the following keywords or keyword arguments:
•
•
•
•
•
•
•
transmit
Transmits the packets.
Defaults
No default behavior or values
Command Modes
Policy map police configuration
Command History
Usage Guidelines
To use this command, you must be in a user group associated with a task group that includes the proper task IDs. For detailed information about user groups and task IDs, see the Configuring AAA Services on Cisco IOS XR Software module of the Cisco IOS XR System Security Configuration Guide.
The atm-clp keyword is available on the Cisco XR 12000 Series Router only.
For more information regarding the traffic policing feature refer to police rate.
The violate-action command can set the DSCP, the precedence, or the discard class for IP packets, and experimental and discard-class values for MPLS packets.
Task ID
Examples
In the following example for MPLS, traffic policing is configured to drop packets that violate the rate limit:
RP/0/RP0/CPU0:router(config)# class-map class1RP/0/RP0/CPU0:router(config-cmap)# match mpls experimental topmost 0RP/0/RP0/CPU0:router(config-cmap)# exitRP/0/RP0/CPU0:router(config)# policy-map policy1RP/0/RP0/CPU0:router(config-pmap)# class class1RP/0/RP0/CPU0:router(config-pmap-c)# police rate 250 kbps burst 50RP/0/RP0/CPU0:router(config-pmap-c-police)# violate-action dropRP/0/RP0/CPU0:router(config-pmap-c-police)# exitRP/0/RP0/CPU0:router(config-pmap-c)# exitRP/0/RP0/CPU0:router(config-pmap)# exitRP/0/RP0/CPU0:router(config)# interface pos 0/5/0/0RP/0/RP0/CPU0:router(config-if) service-policy input policy1Related Commands
