Cisco ASR 920 series User manual

QoS: Policing and Shaping Configuration Guide (Cisco ASR 920 Series)
First Published: 2014-07-29
Last Modified: 2014-11-22
Americas Headquarters
Cisco Systems, Inc.
170 West Tasman Drive
San Jose, CA 95134-1706
USA
http://www.cisco.com
Tel: [phone]
800 553-NETS (6387)
Fax: [phone]

©2017 Cisco Systems, Inc. All rights reserved.

CONTENTS
CHAPTER 1 Class-Based Policing 1
Finding Feature Information 1
Feature Overview 1
Benefits 2
Restrictions 2
Prerequisites 3
Configuration Tasks 3
Configuring Traffic Policing 3
Verifying Traffic Policing 4
Troubleshooting Tips 4
Monitoring and Maintaining Traffic Policing 4
Configuration Examples 5
Example Configuring a Service Policy that Includes Traffic Policing 5
Additional References 6
Feature Information for Class-Based Policing 7
CHAPTER 2 Punt Policing and Monitoring 9
Finding Feature Information 9
Information About Punt Policing and Monitoring 9
Overview of Punt Policing and Monitoring 9
How to Configure Punt Policing and Monitoring 10
Configuring Punt Policing 10
Verifying Punt Policing 11
Verifying Queue-Based Punt Policing 11
Verifying Punt Policing Statistics 12
Configuration Examples for Punt Policing and Monitoring 14
Example: Configuring Punt Policing 14
Additional References 15
QoS: Policing and Shaping Configuration Guide (Cisco ASR 920 Series)
iii

Feature Information for Punt Policing and Monitoring 16
CHAPTER 3 Port-Shaper and LLQ in the Presence of EFPs 17
Finding Feature Information 17
Restrictions for Port-Shaper and LLQ in the Presence of EFPs 17
Information About Port-Shaper and LLQ in the Presence of EFPs 18
Ethernet Flow Points and LLQ 18
How to Configure Port-Shaper and LLQ in the Presence of EFPs 18
Configuring Hierarchical Policy Maps 18
Configuring an LLQ Policy Map 21
Configuring Port Level Shaping on the Main Interface with Ethernet Flow Points 23
Configuration Examples for Port-Shaper and LLQ in the Presence of EFPs 26
Example: Configuring Hierarchical QoS Port Level Shaping on the Main Interface with
EFPs 26
Example: Configuring Port Level Shaping on the Main Interface with EFPs 26
Additional References 27
Feature Information for Port-Shaper and LLQ in the Presence of EFPs 28
CHAPTER 4 Control Plane Policing 29
Finding Feature Information 29
Restrictions for Control Plane Policing 29
Information About Control Plane Policing 30
Benefits of Control Plane Policing 30
Control Plane Terms to Understand 30
Control Plane Policing Overview 30
Supported Protocols 31
Input Rate-Limiting and Silent Mode Operation 36
How to Use Control Plane Policing 36
Defining Control Plane Services 36
Verifying Control Plane Services 37
Configuring Control Plane Policing to Mitigate Denial-of-Service Attacks 38
Configuration Examples for Control Plane Policing 42
Example: Configuring Control Plane Policing on Input Telnet Traffic 42
Additional References 42
Feature Information for Control Plane Policing 43
QoS: Policing and Shaping Configuration Guide (Cisco ASR 920 Series)
iv
Contents

CHAPTER 5 Priority Shaper 45
Restrictions for Priority Shaper 45
Configuring Priority Shaper 45
Configuration Examples for Priority Shaper 47
Example: Configuring Priority Shaper 47
Verifying Priority Shaper 48
CHAPTER 6 Hierarchical Color-Aware Policing 51
Finding Feature Information 51
Prerequisites for Hierarchical Color-Aware Policing 51
Restrictions for Hierarchical Color-Aware Policing 52
Information About Hierarchical Color-Aware Policing 52
Hierarchical Order Policing 52
Limited Color-Aware Policing 53
Policing Traffic in Child Classes and Parent Classes 54
How to Configure Hierarchical Color-Aware Policing 56
Configuring the Hierarchical Color-Aware Policing Feature 56
Configuration Examples for Hierarchical Color-Aware Policing 58
Example Enabling the Hierarchical Color-Aware Policing Feature 58
Example Disallowing the Removal of an Active Color-Aware Class Map 59
Example Dismantling a Configuration of the Hierarchical Color-Aware Policing Feature 59
Example Applying show Command with Hierarchical Color-Aware Policing 59
Additional References 60
Feature Information for Hierarchical Color-Aware Policing 61
QoS: Policing and Shaping Configuration Guide (Cisco ASR 920 Series)
v
Contents

QoS: Policing and Shaping Configuration Guide (Cisco ASR 920 Series)
vi
Contents

CHAPTER 1
Class-Based Policing
•Finding Feature Information, page 1
•Feature Overview, page 1
•Prerequisites, page 3
•Configuration Tasks, page 3
•Monitoring and Maintaining Traffic Policing, page 4
•Configuration Examples, page 5
•Additional References, page 6
•Feature Information for Class-Based Policing, page 7
Finding Feature Information
Your software release may not support all the features documented in this module. For the latest caveats and
feature information, see Bug Search Tool and the release notes for your platform and software release. To
find information about the features documented in this module, and to see a list of the releases in which each
feature is supported, see the feature information table.
Use Cisco Feature Navigator to find information about platform support and Cisco software image support.
To access Cisco Feature Navigator, go to www.cisco.com/go/cfn. An account on Cisco.com is not required.
Feature Overview
Class-Based Policing allows you to control the maximum rate of traffic transmitted or received on an interface.
The Class-Based Policing feature is applied when you attach a traffic policy contain the Class-Based Policing
configuration to an interface.
The Class-Based Policing feature performs the following functions:
•Limits the input or output transmission rate of a class of traffic based on user-defined criteria
QoS: Policing and Shaping Configuration Guide (Cisco ASR 920 Series)
1

•Marks packets by setting the ATM Cell Loss Priority (CLP) bit, Frame Relay Discard Eligibility (DE)
bit, IP precedence value, IP differentiated services code point (DSCP) value, MPLS experimental value,
and Quality of Service (QoS) group.
Benefits
Bandwidth Management Through Rate Limiting
Class-Based Policing allows you to control the maximum rate of traffic transmitted or received on an interface.
Class-Based Policing is often configured on interfaces at the edge of a network to limit traffic into or out of
the network. In most Class-Based Policing configurations, traffic that falls within the rate parameters is
transmitted, whereas traffic that exceeds the parameters is dropped or transmitted with a different priority.
Packet Marking
Packet marking allows you to partition your network into multiple priority levels or classes of service (CoS).
A packet is marked and these markings can be used to identify and classify traffic for downstream devices.
In some cases, such as ATM Cell Loss Priority (CLP) marking or Frame Relay Discard Eligibility (DE)
marking, the marking is used to classify traffic.
•Use Class-Based Policing to set the IP precedence or DSCP values for packets entering the network.
Networking devices within your network can then use the adjusted IP precedence values to determine
how the traffic should be treated. For example, the Weighted Random Early Detection (WRED) feature
uses the IP precedence values to determine the probability that a packet will be dropped.
•Use Class-Based Policing to assign packets to a QoS group. The router uses the QoS group to determine
how to prioritize packets within the router.
Traffic can be marked without using the Class-Based Policing feature. If you want to mark traffic but do not
want to use Class-Based Policing, see the "Marking Network Traffic" module.
Packet Prioritization for Frame Relay Frames
The Class-Based Policing feature allows users to mark the Frame Relay DE bit of the Frame Relay frame.
The Frame Relay DE bit is one bit and, therefore, can be set to either 0 or 1. In congested environments,
frames with the DE bit set to 1 are discarded before frames with the DE bit set to 0.
Packet Prioritization for ATM Cells
The Class-Based Policing feature allows users to mark the ATM CLP bit in ATM cells. The ATM CLP bit
is used to prioritize packets in ATM networks. The ATM CLP bit is one bit and, therefore, can be set to either
0 or 1. In congested environments, cells with the ATM CLP bit set to 1 are discarded before cells with the
ATM CLP bit set to 0.
Restrictions
•To use the set-clp-transmitaction available with this feature, the Enhanced ATM Port Adapter (PA-A3)
is required. Therefore, the set-clp-transmit action is not supported on any platform that does not support
the PA-A3 adapter. For more information, see the documentation for your specific device.
QoS: Policing and Shaping Configuration Guide (Cisco ASR 920 Series)
2
Class-Based Policing
Benefits

•On a Cisco ASR 920 Series router in egress, 1R2C means confirm-action transmit and exceed-action
drop. By configuring exceed-action transmit on egress will drop those packets.
•On a Cisco ASR 920 Series router, Class-Based Policing can monitor Cisco Express Forwarding (CEF)
switching paths only. In order to use the Class-Based Policing feature, Cisco Express Forwarding must
be configured on both the interface receiving the packet and the interface sending the packet.
•On a Cisco ASR 920 Series router, Class-Based Policing cannot be applied to packets that originated
from or are destined to a device.
•Class-Based Policing can be configured on an interface or a subinterface.
•Class-Based Policing is not supported on the following interfaces:
•Fast EtherChannel
•PRI
•Any interface on a Cisco ASR 920 Series router that does not support Cisco Express Forwarding
•Tunnel
Class-Based Policing is supported on tunnels that are using the Cisco generic routing encapsulation (GRE)
tunneling protocol.
Note
Prerequisites
On a Cisco ASR 920 Series router, Cisco Express Forwarding (CEF) must be configured on the interface
before Class-Based Policing can be used.
Configuration Tasks
Configuring Traffic Policing
PurposeCommand
Specifies a maximum bandwidth usage by a traffic
class.
The Class-Based Policing feature works with
a token bucket mechanism. There are
currently two types of token bucket
algorithms: a single token bucket algorithm
and a two token bucket algorithm. A single
token bucket system is used when the
violate-action option is not specified, and a
two token bucket system is used when the
violate-action option is specified.
Note
Device(config-pmap-c)# police bps burst-normal
burst-max conform-action action exceed-action
action violate-action action
QoS: Policing and Shaping Configuration Guide (Cisco ASR 920 Series)
3
Class-Based Policing
Prerequisites

Verifying Traffic Policing
Use the show policy-map interface EXEC command to verify that the Class-Based Policing feature is
configured on your interface. If the feature is configured on your interface, the show policy-map interface
command output displays policing statistics:
Device# show policy-map interface
Ethernet1/7
service-policy output: x
class-map: a (match-all)
0 packets, 0 bytes
5 minute rate 0 bps
match: ip precedence 0
police:
1000000 bps, 10000 limit, 10000 extended limit
conformed 0 packets, 0 bytes; action: transmit
exceeded 0 packets, 0 bytes; action: drop
conformed 0 bps, exceed 0 bps, violate 0 bps
Troubleshooting Tips
•Check the interface type. Verify that your interface is not mentioned in the nonsupported interface
description in the Restrictions, on page 2 section of this module.
•For input Class-Based Policing on a Cisco ASR 920 Series router, verify that CEF is configured on the
interface where Class-Based Policing is configured.
•For output Class-Based Policing on a Cisco ASR 920 Series router, ensure that the incoming traffic is
CEF-switched. Class-Based Policing cannot be used on the switching path unless CEF switching is
enabled.
Monitoring and Maintaining Traffic Policing
PurposeCommand
Displays all configured policy maps.Device# show policy-map
Displays the user-specified policy map.
Device# show policy-map policy-map-name
Displays statistics and configurations of all input and
output policies that are attached to an interface.
Device# show policy-map interface
Displays the policy map information for a given
service instance under a port channel.
Device# show policy-map interface service instance
QoS: Policing and Shaping Configuration Guide (Cisco ASR 920 Series)
4
Class-Based Policing
Verifying Traffic Policing

Configuration Examples
Example Configuring a Service Policy that Includes Traffic Policing
In the following example, Class-Based Policing is configured with the average rate at 8000 bits per second,
the normal burst size at 1000 bytes, and the excess burst size at 1000 bytes for all packets leaving Fast Ethernet
interface 0/0.
class-map access-match
match access-group 1
exit
policy-map police-setting
class access-match
police 8000 1000 1000 conform-action transmit exceed-action set-qos-transmit 1 violate-action
drop
exit
exit
service-policy output police-setting
The treatment of a series of packets leaving Fast Ethernet interface 0/0 depends on the size of the packet and
the number of bytes remaining in the conform and exceed token buckets. The series of packets are policed
based on the following rules:
•If the previous arrival of the packet was at T1 and the current arrival of the packet is at T, the bucket is
updated with T -T1 worth of bits based on the token arrival rate. The refill tokens are placed in the
conform bucket. If the tokens overflow the conform bucket, the overflow tokens are placed in the exceed
bucket. The token arrival rate is calculated as follows:
(time between packets <which is equal to T - T1> * policer rate)/8 bytes
•If the number of bytes in the conform bucket B is greater than or equal to 0, the packet conforms and
the conform action is taken on the packet. If the packet conforms, B bytes are removed from the conform
bucket and the conform action is taken. The exceed bucket is unaffected in this scenario.
•If the number of bytes in the conform bucket B is less than 0, the excess token bucket is checked for
bytes by the packet. If the number of bytes in the exceed bucket B is greater than or equal to 0, the exceed
action is taken and B bytes are removed from the exceed token bucket. No bytes are removed from the
conform bucket in this scenario.
•If the number bytes in the exceed bucket B is fewer than 0, the packet violates the rate and the violate
action is taken. The action is complete for the packet.
In this example, the initial token buckets starts full at 1000 bytes. If a 450-byte packet arrives, the packet
conforms because enough bytes are available in the conform token bucket. The conform action (send) is taken
by the packet and 450 bytes are removed from the conform token bucket (leaving 550 bytes).
If the next packet arrives 0.25 seconds later, 250 bytes are added to the conform token bucket
((0.25 * 8000)/8), leaving 800 bytes in the conform token bucket. If the next packet is 900 bytes, the packet
does not conform because only 800 bytes are available in the conform token bucket.
The exceed token bucket, which starts full at 1000 bytes (as specified by the excess burst size) is then checked
for available bytes. Because enough bytes are available in the exceed token bucket, the exceed action (set the
QoS transmit value of 1) is taken and 900 bytes are taken from the exceed bucket (leaving 100 bytes in the
exceed token bucket.
QoS: Policing and Shaping Configuration Guide (Cisco ASR 920 Series)
5
Class-Based Policing
Configuration Examples

If the next packet arrives 0.40 seconds later, 400 bytes are added to the token buckets ((.40 * 8000)/8).
Therefore, the conform token bucket now has 1000 bytes (the maximum number of tokens available in the
conform bucket) and 200 bytes overflow the conform token bucket (because it only 200 bytes were needed
to fill the conform token bucket to capacity). These overflow bytes are placed in the exceed token bucket,
giving the exceed token bucket 300 bytes.
If the arriving packet is 1000 bytes, the packet conforms because enough bytes are available in the conform
token bucket. The conform action (transmit) is taken by the packet, and 1000 bytes are removed from the
conform token bucket (leaving 0 bytes).
If the next packet arrives 0.20 seconds later, 200 bytes are added to the token bucket ((.20 * 8000)/8). Therefore,
the conform bucket now has 200 bytes. If the arriving packet is 400 bytes, the packet does not conform because
only 200 bytes are available in the conform bucket. Similarly, the packet does not exceed because only 300
bytes are available in the exceed bucket. Therefore, the packet violates and the violate action (drop) is taken.
Additional References
Related Documents
Document TitleRelated Topic
Cisco IOS Quality of Service Solutions Command
Reference
QoS commands: complete command syntax,
command modes, command history, defaults, usage
guidelines, and examples
"Applying QoS Features Using the MQC" moduleModular Quality of Service (QoS) Command-Line
Interface (CLI) (MQC), hierarchical policies, policy
maps
"Policing and Shaping Overview" modulePolicing and shaping traffic
Standards
TitleStandard
--No new or modified standards are supported by this
feature, and support for existing standards has not
been modified by this feature.
MIBs
MIBs LinkMIB
To locate and download MIBs for selected platforms,
Cisco IOS XE software releases, and feature sets, use
Cisco MIB Locator found at the following URL:
http://www.cisco.com/go/mibs
No new or modified MIBs are supported by this
feature, and support for existing MIBs has not been
modified by this feature.
QoS: Policing and Shaping Configuration Guide (Cisco ASR 920 Series)
6
Class-Based Policing
Additional References

RFCs
TitleRFC
--No new or modified RFCs are supported by this
feature, and support for existing RFCs has not been
modified by this feature.
Technical Assistance
LinkDescription
http://www.cisco.com/cisco/web/support/index.html
The Cisco Support and Documentation website
provides online resources to download documentation,
software, and tools. Use these resources to install and
configure the software and to troubleshoot and resolve
technical issues with Cisco products and technologies.
Access to most tools on the Cisco Support and
Documentation website requires a Cisco.com user ID
and password.
Feature Information for Class-Based Policing
The following table provides release information about the feature or features described in this module. This
table lists only the software release that introduced support for a given feature in a given software release
train. Unless noted otherwise, subsequent releases of that software release train also support that feature.
Use Cisco Feature Navigator to find information about platform support and Cisco software image support.
To access Cisco Feature Navigator, go to www.cisco.com/go/cfn. An account on Cisco.com is not required.
Table 1: Feature Information for Class-Based Policing
Feature InformationReleasesFeature Name
This feature was introduced on the
Cisco ASR 920 Series Aggregation
Services Router
(ASR-920-12CZ-A,
ASR-920-12CZ-D,
ASR-920-4SZ-A,
ASR-920-4SZ-D).
Cisco IOS XE Release 3.13.0SClass-Based Policing
QoS: Policing and Shaping Configuration Guide (Cisco ASR 920 Series)
7
Class-Based Policing
Feature Information for Class-Based Policing

QoS: Policing and Shaping Configuration Guide (Cisco ASR 920 Series)
8
Class-Based Policing
Feature Information for Class-Based Policing

CHAPTER 2
Punt Policing and Monitoring
Punt policing protects the Route Processor (RP) from having to process noncritical traffic, which increases
the CPU bandwidth available to critical traffic. Traffic is placed into different CPU queues based on various
criteria. The Punt Policing and Monitoring feature allows you to police the punt rate on a per-queue basis.
•Finding Feature Information, page 9
•Information About Punt Policing and Monitoring, page 9
•How to Configure Punt Policing and Monitoring, page 10
•Configuration Examples for Punt Policing and Monitoring, page 14
•Additional References, page 15
•Feature Information for Punt Policing and Monitoring, page 16
Finding Feature Information
Your software release may not support all the features documented in this module. For the latest caveats and
feature information, see Bug Search Tool and the release notes for your platform and software release. To
find information about the features documented in this module, and to see a list of the releases in which each
feature is supported, see the feature information table.
Use Cisco Feature Navigator to find information about platform support and Cisco software image support.
To access Cisco Feature Navigator, go to www.cisco.com/go/cfn. An account on Cisco.com is not required.
Information About Punt Policing and Monitoring
Overview of Punt Policing and Monitoring
Packets received on an interface are punted to the Router Processor (RP) for various reasons. Some examples
of these various reasons include, unicast and multicast control plane traffic that are destined for a routing
protocol process running on the RP, and IP packets that generate Internet Control Message Protocol (ICMP)
exceptions such as a Time to live (TTL) expiration. The RP has a limited capacity to process the punted
QoS: Policing and Shaping Configuration Guide (Cisco ASR 920 Series)
9

packets, and while some of them are critical for the router operation and should not be dropped, some can be
dropped without impacting the router operation.
Punt policing frees the RP from having to process noncritical traffic. Traffic is placed in queues based on
various criteria, and you can configure the maximum punt rate for each queue which allows you to configure
the system so that packets are less likely to be dropped from queues that contain critical traffic.
Traffic on certain CPU queues could still be dropped, regardless of the configured punt rate, based on
other criteria such as the queue priority, queue size, and traffic punt rate.
Note
How to Configure Punt Policing and Monitoring
Configuring Punt Policing
Traffic on a specific CPU queue may be dropped irrespective of the configured maximum punt rate, based
on the queue priority, queue size, and the configured traffic punt rate.
Note
Perform this task to specify the maximum punt rate on the specified queue.
SUMMARY STEPS
1. enable
2. configure terminal
3. platform qos-policer queue queue-id cir
4. end
DETAILED STEPS
PurposeCommand or Action
Enables privileged EXEC mode.enable
Step 1
Example:
•Enter your password if prompted.
Enters global configuration mode.configure terminal
Example:
Step 2
Device# configure terminal
Enables punt policing on a queue, and specifies the
maximum punt rate on a per-queue basis.
platform qos-policer queue queue-id cir
Example:
Step 3
QoS: Policing and Shaping Configuration Guide (Cisco ASR 920 Series)
10
Punt Policing and Monitoring
How to Configure Punt Policing and Monitoring

PurposeCommand or Action
Device(config)# platform punt-police queue 20 9000
10000
(Optional) Returns to privileged EXEC mode.end
Example:
Step 4
Device(config)# end
Verifying Punt Policing
Verifying Queue-Based Punt Policing
Use the show platform software infrastructure punt statistics to display punt police statistics:
Router# show platform software infrastructure punt statistics
UEA Punt Statistics
Global drops : 0
Queue Name | Rx count | Drop count
------------------------+---------------------------+-----------------------
SW FORWARDING Q | 0 | 0
ROUTING PROTOCOL Q | 0 | 0
ICMP Q | 0 | 0
HOST Q | 57115 | 0
ACL LOGGING Q | 0 | 0
STP Q | 0 | 0
L2 PROTOCOL Q | 6571 | 0
MCAST CONTROL Q | 208839 | 0
BROADCAST Q | 4 | 0
REP Q | 0 | 0
CFM Q | 0 | 0
CONTROL Q | 0 | 0
IP MPLS TTL Q | 0 | 0
DEFAULT MCAST Q | 0 | 0
MCAST ROUTE DATA Q | 0 | 0
MCAST MISMATCH Q | 0 | 0
RPF FAIL Q | 0 | 0
ROUTING THROTTLE Q | 87 | 0
MCAST Q | 0 | 0
MPLS OAM Q | 0 | 0
IP MPLS MTU Q | 0 | 0
PTP Q | 0 | 0
LINUX ND Q | 0 | 0
KEEPALIVE Q | 0 | 0
ESMC Q | 0 | 0
FPGA BFD Q | 0 | 0
FPGA CCM Q | 0 | 0
FPGA CFE Q | 0 | 0
L2PT DUP Q | 0 | 0
QoS: Policing and Shaping Configuration Guide (Cisco ASR 920 Series)
11
Punt Policing and Monitoring
Verifying Punt Policing

Verifying Punt Policing Statistics
Use the show platform hardware pp active infrastructure pi npd rx policer command to display the punt
policing statistics for all queues.
Ring | Queue Name | Punt rate | Burst rate
-----+---------------------+---------------------+--------------------
0 | SW FORWARDING Q | 500 | 1000
1 | ROUTING PROTOCOL Q | 500 | 1000
2 | ICMP Q | 500 | 1000
3 | HOST Q | 1000 | 2000
4 | ACL LOGGING Q | 500 | 1000
5 | STP Q | 3000 | 6000
6 | L2 PROTOCOL Q | 1000 | 2000
7 | MCAST CONTROL Q | 1000 | 2000
8 | BROADCAST Q | 1000 | 2000
9 | REP Q | 3000 | 6000
10 | BGP LDP Q | 3000 | 6000
11 | CONTROL Q | 1000 | 2000
12 | IP MPLS TTL Q | 1000 | 2000
13 | DEFAULT MCAST Q | 500 | 1000
14 | MCAST ROUTE DATA Q | 500 | 1000
15 | MCAST HIGH PRI Q | 1000 | 2000
16 | RPF FAIL Q | 500 | 1000
17 | ROUTING THROTTLE Q | 500 | 1000
18 | MCAST Q | 500 | 1000
19 | MPLS OAM Q | 1000 | 2000
20 | IP MPLS MTU Q | 500 | 1000
21 | PTP Q | 3000 | 6000
22 | LINUX ND Q | 500 | 1000
23 | KEEPALIVE Q | 1000 | 2000
24 | ESMC Q | 3000 | 6000
25 | FPGA BFD Q | 4000 | 8000
26 | FPGA CCM Q | 4000 | 8000
27 | FPGA CFE Q | 1000 | 2000
28 | L2PT DUP Q | 4000 | 8000
29 | TDM CTRL Q | 3000 | 6000
30 | ICMP UNREACHABLE Q | 500 | 1000
31 | SSFPD Q | 6000 | 12000
Router# show platform hardware pp active infrastructure pi npd rx policer
PUNT POLICER
Ring | Queue Name | Punt rate | Burst rate
-----+---------------------+---------------------+--------------------
0 | SW FORWARDING Q | 500 | 1000
1 | ROUTING PROTOCOL Q | 500 | 1000
2 | ICMP Q | 500 | 1000
3 | HOST Q | 1000 | 2000
4 | ACL LOGGING Q | 500 | 1000
5 | STP Q | 3000 | 6000
6 | L2 PROTOCOL Q | 1000 | 2000
7 | MCAST CONTROL Q | 1000 | 2000
8 | BROADCAST Q | 500 | 1000
9 | REP Q | 3000 | 6000
10 | CFM Q | 3000 | 6000
11 | CONTROL Q | 1000 | 2000
12 | IP MPLS TTL Q | 1000 | 2000
13 | DEFAULT MCAST Q | 500 | 1000
14 | MCAST ROUTE DATA Q | 500 | 1000
15 | MCAST MISMATCH Q | 500 | 1000
16 | RPF FAIL Q | 500 | 1000
17 | ROUTING THROTTLE Q | 500 | 1000
18 | MCAST Q | 500 | 1000
19 | MPLS OAM Q | 1000 | 2000
20 | IP MPLS MTU Q | 500 | 1000
21 | PTP Q | 3000 | 6000
22 | LINUX ND Q | 500 | 1000
23 | KEEPALIVE Q | 1000 | 2000
24 | ESMC Q | 3000 | 6000
25 | FPGA BFD Q | 3000 | 6000
QoS: Policing and Shaping Configuration Guide (Cisco ASR 920 Series)
12
Punt Policing and Monitoring
Verifying Punt Policing

26 | FPGA CCM Q | 3000 | 6000
27 | FPGA CFE Q | 3000 | 6000
28 | L2PT DUP Q | 4000 | 8000
Router#show platform hardware pp active infrastructure pi npd rx policer
PUNT POLICER
Ring | Queue Name | Punt rate | Burst rate
-----+---------------------+---------------------+--------------------
0 | SW FORWARDING Q | 500 | 1000
1 | ROUTING PROTOCOL Q | 500 | 1000
2 | ICMP Q | 500 | 1000
3 | HOST Q | 1000 | 2000
4 | ACL LOGGING Q | 500 | 1000
5 | STP Q | 3000 | 6000
6 | L2 PROTOCOL Q | 1000 | 2000
7 | MCAST CONTROL Q | 1000 | 2000
8 | BROADCAST Q | 500 | 1000
9 | REP Q | 3000 | 6000
10 | CFM Q | 3000 | 6000
11 | CONTROL Q | 1000 | 2000
12 | IP MPLS TTL Q | 1000 | 2000
13 | DEFAULT MCAST Q | 500 | 1000
14 | MCAST ROUTE DATA Q | 500 | 1000
15 | MCAST MISMATCH Q | 500 | 1000
16 | RPF FAIL Q | 500 | 1000
17 | ROUTING THROTTLE Q | 500 | 1000
18 | MCAST Q | 500 | 1000
19 | MPLS OAM Q | 1000 | 2000
20 | IP MPLS MTU Q | 9000 | 10000
21 | PTP Q | 3000 | 6000
22 | LINUX ND Q | 500 | 1000
23 | KEEPALIVE Q | 1000 | 2000
24 | ESMC Q | 3000 | 6000
25 | FPGA BFD Q | 4000 | 8000
26 | FPGA CCM Q | 2000 | 4000
27 | FPGA CFE Q | 3000 | 6000
28 | L2PT DUP Q | 4000 | 8000
Use the show platform hardware pp active feature qos policer cpu all 1 command to clear the statistics
of all the CPU queues.
Use the show platform hardware pp active feature qos policer cpu all 0 command to clear the statistics
of a particular CPU queue.
########## Stats for CPU queue 0 ##########
Internal Qnum: 1 Queue Name: SW FORWARDING Q
Policer conform: 0 (packets) 0 (bytes)
Policer exceed: 0 (packets) 0 (bytes)
RM Drops: 0 (packets) 0 (bytes)
Policer commit rate is: 1000000, Policer burst commit is 100000
########### Stats for CPU queue 1 ##########
Internal Qnum: 2 Queue Name: ROUTING PROTOCOL Q
Policer conform: 0 (packets) 0 (bytes)
Policer exceed: 0 (packets) 0 (bytes)
RM Drops: 0 (packets) 0 (bytes)
Policer commit rate is: 1000000, Policer burst commit is 100000
———————
———————
———————
########### Stats for CPU queue 30 ##########
Internal Qnum: 31 Queue Name: ICMP UNREACHABLE Q
Policer conform: 0 (packets) 0 (bytes)
Policer exceed: 0 (packets) 0 (bytes)
RM Drops: 0 (packets) 0 (bytes)
Policer commit rate is: 1000000, Policer burst commit is 100000
########### Stats for CPU queue 31 ##########
Internal Qnum: 32 Queue Name: SSFPD Q
Policer conform: 0 (packets) 0 (bytes)
Policer exceed: 0 (packets) 0 (bytes)
QoS: Policing and Shaping Configuration Guide (Cisco ASR 920 Series)
13
Punt Policing and Monitoring
Verifying Punt Policing

RM Drops: 0 (packets) 0 (bytes)
Policer commit rate is: 1000000, Policer burst commit is 100000
Use show platform hardware pp active feature qos policer cpu 3 0 to display the queue specific statistics.
########### Stats for CPU queue 3 ##########
Internal Qnum: 4 Queue Name: HOST Q
Policer conform: 0 (packets) 0 (bytes)
Policer exceed: 0 (packets) 0 (bytes)
RM Drops: 0 (packets) 0 (bytes)
Policer commit rate is: 12000000, Policer burst commit is 3000000
3—— queueId of CPU and 0 —show stats
Use the show platform hardware qfp active statistics drop to display the output after adding the drop cause:
Device# show platform hardware qfp active statistics drop
---------------------------------------------------------------------
Global Drop Stats Packets
Octets
---------------------------------------------------------------------
PuntPerIntfPolicerDrops 257
274166
Use the show platform hardware pp active feature qos policer cpu all 0 to display the output after adding
the drop cause. Following commands are applicable only for RSP3 module:
########### Stats for CPU queue 0 ##########
Internal Qnum: 8000CPU
Port num: 0
Policer conform: 0 (packets) 0 (bytes)
Policer exceed: 0 (packets) 0 (bytes)
Policer commit rate is: 500000 bps, Policer burst commit is 16000 bytes
########### Stats for CPU queue 1 ##########
Internal Qnum: 8008CPU
Port num: 0
Policer conform: 0 (packets) 0 (bytes)
Policer exceed: 0 (packets) 0 (bytes)
Policer commit rate is: 1000000 bps, Policer burst commit is 100000 bytes
########### Stats for CPU queue 2 ##########
Internal Qnum: 8016CPU
Port num: 0
Policer conform: 0 (packets) 0 (bytes)
Policer exceed: 0 (packets) 0 (bytes)
Policer commit rate is: 1000000 bps, Policer burst commit is 100000 bytes
When a packet is dropped by per interface punt policer, a log including the source interface is displayed
as follows (the log shows one log in 30 seconds):
Note
*Jun 6 08:25:35.893: %IOSXE-5-PLATFORM: F0: cpp_cp: QFP:0.0
Thread:046 TS:00000000400859588264 %PUNT_INJECT-5-DROP_PUNT_INTF:
punt interface policer drop packet from GigabitEthernet2/3/1.726
Configuration Examples for Punt Policing and Monitoring
Example: Configuring Punt Policing
The following example shows how to enable punt-policing:
Router# enable
Router# configure terminal
Router(config)# platform qos-policer queue 3 64000
QoS: Policing and Shaping Configuration Guide (Cisco ASR 920 Series)
14
Punt Policing and Monitoring
Configuration Examples for Punt Policing and Monitoring