 Feedback
|
Table Of Contents
QoS—Ingress Hierarchical Policing for Cisco 12000 Series Router Line Cards
QoS-Ingress Hierarchical Policing Feature Overview
Related Features and Technologies
Supported Standards, MIBs, and RFCs
Verifying, Monitoring, and Troubleshooting QoS-Ingress Hierarchical Policing
QoS—Ingress Hierarchical Policing for Cisco 12000 Series Router Line Cards
Part Number: OL-8681-01 (Rev. A0) November 16, 2007
Feature History
This feature module contains the following sections:
•
QoS-Ingress Hierarchical Policing Feature Overview
•
QoS-Ingress Hierarchical Policing Feature Overview
QoS-Ingress Hierarchical Policing for Cisco IOS software Release 12.0(32)S is a Cisco IOS Modular Quality of Service CLI (MQC)-based solution that supports hierarchical policing on the ingress interfaces of Integrated Services Engine (ISE) and multiservice engine line cards on Cisco 12000 series routers.
This feature allows enforcement of SLA agreements while applying classification sub-models for different QoS classes on the inbound provider edge interfaces.
QoS-Ingress Hierarchical Policing provides support for a 2-level hierarchical policy-map:
•
•
This allows the user to police the ingress interface while applying different classification submodels on ingress interfaces.
The order of the actions within the hierarchical policy-map is from child to parent, 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 first, then the parent police action.
The parent police bandwidth value is used as the reference bandwidth for the child policy in child percentage commands. The parent police bandwidth is calculated as follows:
if conform & exceed actions are drop => reference rate is zero.else if conform action is drop => reference rate is: interface_rate-cir (if interface_rate > cir then reference rate is zero).else if exceed action is drop => reference rate is MIN(cir, interface_rate)else reference rate is interface_rate.The hierarchical policing policy map shown below first executes the police action of the nested policy map, child, and secondly, the main policy map, parent. The action invoked in the parent policy is the police command with only transmit/drop actions under conform-action and exceed-action options specified for class-default traffic. The child level consists of a flat policy that can be configured with any action or class within the current restrictions of the hardware and the Cisco IOS software release. Thus:
•
•
2-Level Policing with Hierarchical Policy Map
Router#Router#config tRouter(config)#policy-map parentRouter(config-pmap)#Class class-defaultRouter(config-pmap-c)#police cir 200000000 bc 100000 be 100000Router(config-pmap-c)#conform-action transmitRouter(config-pmap-c)#exceed-action dropRouter(config-pmap-c)#service-policy childRouter(config-pmap-c)#exitRouter(config-pmap)#exitRouter(config)#Router(config)#policy-map childRouter(config-pmap)#class prec1Router(config-pmap-c)#police cir 100000000 bc 3125000 be 3125000Router(config-pmap-c)#conform-action set-prec-transmit 3Router(config-pmap-c)#exceed-action dropRouter(config-pmap-c)#exitRouter(config-pmap)#class prec2Router(config-pmap-c)#police cir 100000000 bc 3125000 be 3125000Router(config-pmap-c)#conform-action transmitRouter(config-pmap-c)#exceed-action dropRouter(config-pmap-c)#exitRouter(config-pmap)#class prec3Router(config-pmap-c)#police cir 100000000 bc 3125000 be 3125000Router(config-pmap-c)#conform-action transmitRouter(config-pmap-c)#exceed-action dropRouter(config-pmap-c)#exitRouter(config-pmap)#exitRouter(config)#class-map match-any Prec1Router(config-cmap)#Match ip precedence 1Router(config-cmap)#exitRouter(config)#class-map match-any Prec2Router(config-cmap)#Match ip precedence 2Router(config-cmap)#exitRouter(config)#class-map match-any Prec3Router(config-cmap)#Match ip precedence 3Router(config-cmap)#exitRouter(config)#Router(config)#interface gigabitEthernet 1/0.1Router(config-if)#service-policy input parentRouter(config-if)#exitRouter(config)#exitRouter#Class match counters of the parent class, as shown by the show policy-map interface command are the sum of all class match counters of the child classes. Dropped packets in the child class are counted in the class match counters of the parent. However, packets that are dropped by a child class due to a police action are not counted in the parent police.
Note
Benefits
QoS-Ingress Hierarchical Policing for Cisco IOS Release 12.0(32)S is a Cisco IOS Modular Quality of Service CLI (MQC)-based solution.
Restrictions
QoS-Ingress Hierarchical Policing for Cisco IOS Release 12.0(32)S has the following restrictions.
1.
2.
3.
4.
5.
6.
7.
8.
9.
10.
Related Features and Technologies
Cisco IOS Quality of Service (QoS) Solutions for Cisco 12000 series routers
Related Documents
For additional information on configuring Cisco 12000 series routers, refer to the following documents.
•
•
•
•
•
Also, refer to the installation and configuration guide for a specific Cisco 12000 series router.
Supported Platforms
QoS-Ingress Hierarchical Policing is supported on the following Cisco 12000 series router Integrated Services Engine (ISE) and multiservice engine line cards and SPAs running Cisco IOS Release 12.0(32)S:
•
–
–
–
–
–
–
–
•
–
–
–
•
–
•
–
–
–
–
•
–
–
–
–
–
–
–
Supported Standards, MIBs, and RFCs
Standards
No new or modified standards are supported, and support for existing standards was not modified.
MIBs
No new or modified MIBs are supported, and support for existing MIBs was not modified.
RFCs
No new or modified RFCs are supported, and support for existing RFCs was not modified.
Prerequisites
No prerequisites are required for this feature.
Configuration Tasks
Verifying, Monitoring, and Troubleshooting QoS-Ingress Hierarchical Policing
Use the following show commands to verify, monitor, and troubleshoot QoS-Ingress Hierarchical Policing.
Configuration Examples
Configure QoS-Ingress Hierarchical Policing as follows:
For 1CnD, nCnD QoS models:
Router#Router#config tRouter(config)#Policy-map parentRouter(config-pmap)#class class-defaultRouter(config-pmap-c)#police 200M conform transmit exceed dropRouter(config-pmap-c)#service-policy childRouter(config-pmap-c)#exitRouter(config)#Router(config)#policy-map childRouter(config-pmap)#class prec1Router(config-pmap-c)#police 100M conform set-prec-transmit 2 exceed dropRouter(config-pmap-c)#exitRouter(config)#interface gigabitEthernet 1/0.1Router(config-if)#service-policy input parentRouter(config-if)#exitRouter(config)#exitRouter#For the nCmD QoS model:
Router#Router#config tRouter(config)#class-map match-any customeraRouter(config-cmap)#match vlan 1 - 3Router(config-cmap)#exitRouter(config)#class-map match-any customerbRouter(config-cmap)#match vlan 4 - 6Router(config-cmap)#exitRouter(config)#policy-map parentRouter(config-pmap)#class customeraRouter(config-pmap-c)#police 200M conform transmit exceed dropRouter(config-pmap-c)#service-policy childaRouter(config-pmap-c)#exitRouter(config-pmap)#class customerbRouter(config-pmap-c)#police 300M conform transmit exceed dropRouter(config-pmap-c)#service-policy childbRouter(config-pmap-c)#exitRouter(config-pmap)#exitRouter(config)#interface gigabitEthernet 1/0.1Router(config-if)#service-policy input parentRouter(config-if)#exitRouter(config)#exitRouter#Command Reference
No new or modified commands were introduced for the QoS-Ingress Hierarchical Policing feature for Cisco IOS Release 12.0(32)S.
Glossary
AToM
Any Transport over MPLS
QoS
Cisco IOS Quality of Service
MQC
Cisco IOS Modular Quality of Service CLI (MQC)
SLA
Service level agreements
VC
Virtual connection
© 2006 Cisco Systems, Inc. All rights reserved.
