To display the statistics and the configurations of the input and output policies that are attached to an interface, use
the
show policy-map interface command in user EXEC or privileged EXEC mode.
ATM Shared Port Adapters
show policy-map interface slot/subslot/port . [subinterface]
Cisco CMTS Routers
show policy-map interface interface-type slot/subslot/port
Cisco 3660, 3845, 7200, 7400, 7500, Cisco ASR 903 Series Routers, and Cisco ASR 1000 Series Routers
show policy-map interface type type-parameter [vc [vpi] [/]vci] [dlci dlci] [input | output] [class class-name]
Cisco 6500 Series Switches
show policy-map interface [interface-type interface-number | vlan vlan-id] [detailed] [ {input | output} [class class-name]]
show policy-map interface [port-channel channel-number [class class-name]]
Cisco 7600 Series Routers
show policy-map interface [interface-type interface-number | null 0 | vlan vlan-id] [input | output]
Syntax Description
|
slot
|
(CMTS and ATM shared port adapter only) Chassis slot number. See the appropriate hardware manual for slot information. For
SIPs, see the platform-specific SPA hardware installation guide or the corresponding “Identifying Slots and Subslots for SIPs
and SPAs” topic in the platform-specific SPA software configuration guide.
|
|
/subslot
|
(CMTS and ATM shared port adapter only) Secondary slot number on an SPA interface processor (SIP) where a SPA is installed.
See the platform-specific SPA hardware installation guide and the corresponding “Specifying the Interface Address on an SPA”
topic in the platform-specific SPA software configuration guide for subslot information.
|
|
port
|
(CMTS and ATM shared port adapter only) Port or interface number. See the appropriate hardware manual for port information.
For SPAs, see the corresponding “Specifying the Interface Address” topics in the platform-specific SPA software configuration
guide.
|
|
.subinterface
|
(ATM shared port adapter only—Optional) Subinterface number. The number that precedes the period must match the number to
which this subinterface belongs. The range is 1 to 4,294,967,293.
|
|
type
|
Type of interface or subinterface whose policy configuration is to be displayed.
|
|
type-parameter
|
Port, connector, interface card number, class-map name or other parameter associated with the interface or subinterface type.
|
|
vc
|
(Optional) For ATM interfaces only, shows the policy configuration for a specified PVC.
|
|
vpi
/
|
(Optional) ATM network virtual path identifier (VPI) for this permanent virtual circuit (PVC). On the Cisco 7200 and 7500
series routers, this value ranges from 0 to 255.
The
vpi and
vci arguments cannot both be set to 0; if one is 0, the other cannot be 0.
The absence of both the forward slash (/ ) and a
vpi value defaults the
vpi value to 0. If this value is omitted, information for all virtual circuits (VCs) on the specified ATM interface or subinterface
is displayed.
|
|
vci
|
(Optional) ATM network virtual channel identifier (VCI) for this PVC. This value ranges from 0 to 1 less than the maximum
value set for this interface by the
atmvc-per-vp command. Typically, the lower values 0 to 31 are reserved for specific traffic (F4 Operation, Administration, and Maintenance
[OAM], switched virtual circuit [SVC] signaling, Integrated Local Management Interface [ILMI], and so on) and should not be
used.
The VCI is a 16-bit field in the header of the ATM cell. The VCI value is unique only on a single link, not throughout the
ATM network, because it has local significance only.
The
vpi and
vci arguments cannot both be set to 0; if one is 0, the other cannot be 0.
|
|
dlci
|
(Optional) Indicates a specific PVC for which policy configuration will be displayed.
|
|
dlci
|
(Optional) A specific data-link connection identifier (DLCI) number used on the interface. Policy configuration for the corresponding
PVC will be displayed when a DLCI is specified.
|
|
input
|
(Optional) Indicates that the statistics for the attached input policy will be displayed.
|
|
output
|
(Optional) Indicates that the statistics for the attached output policy will be displayed.
|
|
class
class-name
|
(Optional) Displays the QoS policy actions for the specified class.
|
|
interface-type
|
(Optional) Interface type; possible valid values are
atm ,
ethernet ,
fastethernet ,
ge-wan
gigabitethernet ,
pos ,
pseudowire and
tengigabitethernet .
|
|
interface-number
|
(Optional) Module and port number; see the “Usage Guidelines” section for valid values.
|
|
vlan
vlan-id
|
(Optional) Specifies the VLAN ID; valid values are from 1 to 4094.
|
|
detailed
|
(Optional) Displays additional statistics.
|
|
port-channel
channel-number
|
(Optional) Displays the EtherChannel port-channel interface.
|
|
null
0
|
(Optional) Specifies the null interface; the only valid value is 0.
|
Command Default
This command displays the packet statistics of all classes that are configured for all service policies on the specified
interface or subinterface or on a specific permanent virtual circuit (PVC) on the interface.
When used with the ATM shared port adapter, this command has no default behavior or values.
Command Modes
Privileged EXEC (#)
ATM Shared Port Adapter
User EXEC (>)
Privileged EXEC (#)
Command History
|
Release
|
Modification
|
|
12.0(5)T
|
This command was introduced.
|
|
12.0(5)XE
|
This command was integrated into Cisco IOS Release 12.0(5)XE.
|
|
12.0(7)S
|
This command was integrated into Cisco IOS Release 12.0(7)S.
|
|
12.0(28)S
|
This command was modified for the QoS: Percentage-Based Policing feature to include milliseconds when calculating the committed
(conform) burst (bc) and excess (peak) burst (be) sizes.
|
|
12.1(1)E
|
This command was integrated into Cisco IOS Release 12.1(1)E.
|
|
12.1(2)T
|
This command was modified to display information about the policy for all Frame Relay PVCs on the interface or, if a DLCI
is specified, the policy for that specific PVC. This command was also modified to display the total number of packets marked
by the quality of service (QoS) set action.
|
|
12.1(3)T
|
This command was modified to display per-class accounting statistics.
|
|
12.2(4)T
|
This command was modified for two-rate traffic policing and can display burst parameters and associated actions.
|
|
12.2(8)T
|
This command was modified for the Policer Enhancement—Multiple Actions feature and the WRED—Explicit Congestion Notification
(ECN) feature.
For the Policer Enhancement—Multiple Actions feature, the command was modified to display the multiple actions configured
for packets conforming to, exceeding, or violating a specific rate.
For the WRED—Explicit Congestion Notification (ECN) feature, the command displays ECN marking information.
|
|
12.2(13)T
|
The following modifications were made:
-
This command was modified for the Percentage-Based Policing and Shaping feature.
-
This command was modified for the Class-Based RTP and TCP Header Compression feature.
-
This command was modified as part of the Modular QoS CLI (MQC) Unconditional Packet Discard feature. Traffic classes in policy
maps can now be configured to discard packets belonging to a specified class.
-
This command was modified to display the Frame Relay DLCI number as a criterion for matching traffic inside a class map.
-
This command was modified to display Layer 3 packet length as a criterion for matching traffic inside a class map.
-
This command was modified for the Enhanced Packet Marking feature. A mapping table (table map) can now be used to convert
and propagate packet-marking values.
|
|
12.2(14)SX
|
This command was modified. Support for this command was introduced on Cisco 7600 series routers.
|
|
12.2(15)T
|
This command was modified to display Frame Relay voice-adaptive traffic-shaping information.
|
|
12.2(17d)SXB
|
This command was implemented on the Supervisor Engine 2 and integrated into Cisco IOS Release 12.2(17d)SXB.
|
|
12.3(14)T
|
This command was modified to display bandwidth estimation parameters.
|
|
12.2(18)SXE
|
This command was integrated into Cisco IOS Release 12.2(18)SXE. This command was modified to display aggregate WRED statistics
for the ATM shared port adapter. Note that changes were made to the syntax, defaults, and command modes. These changes are
labelled “ATM Shared Port Adapter.”
|
|
12.4(4)T
|
This command was modified. The
typeaccess-control keywords were added to support flexible packet matching.
|
|
12.2(28)SB
|
This command was integrated into Cisco IOS Release 12.2(28)SB, and the following modifications were made:
-
This command was modified to display either legacy (undistributed processing) QoS or hierarchical queueing framework (HQF)
parameters on Frame Relay interfaces or PVCs.
-
This command was modified to display information about Layer 2 Tunnel Protocol Version 3 (L2TPv3) tunnel marking.
|
|
12.2(31)SB2
|
The following modifications were made:
-
This command was enhanced to display statistical information for each level of priority service configured and information
about bandwidth-remaining ratios, and this command was implemented on the Cisco 10000 series router for the PRE3.
-
This command was modified to display statistics for matching packets on the basis of VLAN identification numbers. As of Cisco
IOS Release 12.2(31)SB2, matching packets on the basis of VLAN identification numbers is supported on Cisco 10000 series routers
only.
|
|
12.2(33)SRC
|
This command was integrated into Cisco IOS Release 12.2(33)SRC.
|
|
12.4(15)T2
|
This command was modified to display information about Generic Routing Encapsulation (GRE) tunnel marking.
|
Note
|
As of this release, GRE-tunnel marking is supported on the Cisco MGX Route Processor Module (RPM-XF) platform
only .
|
|
|
12.2(33)SB
|
This command was modified to display information about GRE-tunnel marking, and support for the Cisco 7300 series router was
added.
|
|
Cisco IOS XE 2.1
|
This command was integrated into Cisco IOS XE Release 2.1 and was implemented on the Cisco ASR 1000 series router.
|
|
12.4(20)T
|
This command was modified. Support was added for hierarchical queueing framework (HQF) using the Modular Quality of Service
(QoS) Command-Line Interface (CLI) (MQC).
|
|
12.2(33)SXI
|
This command was implemented on the Catalyst 6500 series switch and modified to display the strict level in the priority
feature and the counts per level.
|
|
12.2(33)SRE
|
This command was modified to automatically round off the bc and be values, in the MQC police policy map, to the interface’s
MTU size.
|
|
Cisco IOS XE Release 2.6
|
The command output was modified to display information about subscriber QoS statistics.
|
|
12.2(54)SG
|
This command was modified to display only the applicable count of policer statistics.
|
|
12.2(33)SCF
|
This command was integrated into Cisco IOS Release 12.2(33)SCF.
|
|
Cisco IOS XE Release 3.7S
|
This command was implemented on Cisco ASR 903 Series Routers.
|
|
Cisco IOS XE Release 3.8S
|
This command was modified. The
pseudowire
interface type was added.
|
|
Cisco IOS XE Release 3.8S
|
This command was modified. The
pseudowire
interface type was added on Cisco 1000 Series Routers.
|
|
Cisco IOS Release 15.3(1)S
|
This command was modified. The
pseudowire
interface type was added.
|
Usage Guidelines
Cisco 3660, 3845, 7200, 7400, 7500, Cisco ASR 903 Series Routers, and Cisco ASR 1000 Series Routers
The
show policy-map interface command displays the packet statistics for classes on the specified interface or the specified PVC only if a service policy
has been attached to the interface or the PVC.
The counters displayed after the
show policy-map interface command is entered are updated only if congestion is present on the interface.
The
show policy-map interface command displays policy information about Frame Relay PVCs only if Frame Relay Traffic Shaping (FRTS) is enabled on the interface.
The
show policy-map interface command displays ECN marking information only if ECN is enabled on the interface.
To determine if shaping is active with HQF, check the queue depth field of the “(queue depth/total drops/no-buffer drops)”
line in the
show policy-map interface command output.
In HQF images for Cisco IOS Releases 12.4(20)T and later, the packets delayed and the bytes delayed counters were removed
for traffic shaping classes.
Cisco 7600 Series Routers and Catalyst 6500 Series Switches
The pos, atm, and ge-wan interfaces are not supported on Cisco 7600 series routers or Catalyst 6500 series switches that
are configured with a Supervisor Engine 720
Cisco 7600 series routers and Catalyst 6500 series switches that are configured with a Supervisor Engine 2 display packet
counters.
Cisco 7600 series routers and Catalyst 6500 series switches that are configured with a Supervisor Engine 720 display byte
counters.
The output does not display policed-counter information; 0 is displayed in its place (for example, 0 packets, 0 bytes). To
display dropped and forwarded policed-counter information, enter the
show mls qos command.
On the Cisco 7600 series router, for OSM WAN interfaces only, if you configure policing within a policy map, the hardware
counters are displayed and the class-default counters are not displayed. If you do not configure policing within a policy
map, the class-default counters are displayed.
On the Catalyst 6500 series switch, the
show policy-map interface command displays the strict level in the priority feature and the counts per level.
The
interface-number argument designates the module and port number. Valid values for
interface-number depend on the specified interface type and the chassis and module that are used. For example, if you specify a Gigabit Ethernet
interface and have a 48-port 10/100BASE-T Ethernet module that is installed in a 13-slot chassis, valid values for the module
number are from 1 to 13 and valid values for the port number are from 1 to 48.
HQF
When you configure HQF, the
show policy-map interface command displays additional fields that include the differentiated services code point (DSCP) value, WRED statistics in bytes,
transmitted packets by WRED, and a counter that displays packets output/bytes output in each class.
Examples
This section provides sample output from typical
show policy-map interface commands. Depending upon the interface or platform in use and the options enabled, the output you see may vary slightly from
the ones shown below.
Examples
The following sample output of the
show policy-map interface command displays the statistics for the serial 3/1 interface, to which a service policy called mypolicy (configured as shown
below) is attached. Weighted fair queueing (WFQ) has been enabled on this interface. See the table below for an explanation
of the significant fields that commonly appear in the command output.
policy-map mypolicy
class voice
priority 128
class gold
bandwidth 100
class silver
bandwidth 80
random-detect
Router# show policy-map interface serial3/1 output
Serial3/1
Service-policy output: mypolicy
Class-map: voice (match-all)
0 packets, 0 bytes
5 minute offered rate 0 bps, drop rate 0 bps
Match: ip precedence 5
Weighted Fair Queueing
Strict Priority
Output Queue: Conversation 264
Bandwidth 128 (kbps) Burst 3200 (Bytes)
(pkts matched/bytes matched) 0/0
(total drops/bytes drops) 0/0
Class-map: gold (match-all)
0 packets, 0 bytes
5 minute offered rate 0 bps, drop rate 0 bps
Match: ip precedence 2
Weighted Fair Queueing
Output Queue: Conversation 265
Bandwidth 100 (kbps) Max Threshold 64 (packets)
(pkts matched/bytes matched) 0/0
(depth/total drops/no-buffer drops) 0/0/0
Class-map: silver (match-all)
0 packets, 0 bytes
5 minute offered rate 0 bps, drop rate 0 bps
Match: ip precedence 1
Weighted Fair Queueing
Output Queue: Conversation 266
Bandwidth 80 (kbps)
(pkts matched/bytes matched) 0/0
(depth/total drops/no-buffer drops) 0/0/0
exponential weight: 9
mean queue depth: 0
class Transmitted Random drop Tail drop Minimum Maximum Mark
pkts/bytes pkts/bytes pkts/bytes thresh thresh prob
0 0/0 0/0 0/0 20 40 1/10
1 0/0 0/0 0/0 22 40 1/10
2 0/0 0/0 0/0 24 40 1/10
3 0/0 0/0 0/0 26 40 1/10
4 0/0 0/0 0/0 28 40 1/10
5 0/0 0/0 0/0 30 40 1/10
6 0/0 0/0 0/0 32 40 1/10
7 0/0 0/0 0/0 34 40 1/10
rsvp 0/0 0/0 0/0 36 40 1/10
Class-map: class-default (match-any)
0 packets, 0 bytes
5 minute offered rate 0 bps, drop rate 0 bps
Match: any
Examples
The following sample output from the
show policy-map interface command displays the statistics for the serial 3/2 interface, to which a service policy called p1 (configured as shown below)
is attached. Traffic shaping has been enabled on this interface. See the table below for an explanation of the significant
fields that commonly appear in the command output.
Note
|
In HQF images for Cisco IOS Releases 12.4(20)T and later, the packets delayed and bytes delayed counters were removed for
traffic shaping classes.
|
policy-map p1
class c1
shape average 320000
Router# show policy-map interface serial3/2 output
Serial3/2
Service-policy output: p1
Class-map: c1 (match-all)
0 packets, 0 bytes
5 minute offered rate 0 bps, drop rate 0 bps
Match: ip precedence 0
Traffic Shaping
Target Byte Sustain Excess Interval Increment Adapt
Rate Limit bits/int bits/int (ms) (bytes) Active
320000 2000 8000 8000 25 1000 -
Queue Packets Bytes Packets Bytes Shaping
Depth Delayed Delayed Active
0 0 0 0 0 no
Class-map: class-default (match-any)
0 packets, 0 bytes
5 minute offered rate 0 bps, drop rate 0 bps
Match: any
The table below describes significant fields commonly shown in the displays. The fields in the table are grouped according
to the relevant QoS feature. A number in parentheses may appear next to the service-policy output name, class-map name, and
match criteria information. The number is for Cisco internal use only and can be disregarded.
Table 27. show policy-map interface Field Descriptions
|
Field
|
Description
|
|
Fields Associated with Classes or Service Policies
|
|
|
Service-policy output
|
Name of the output service policy applied to the specified interface or VC.
|
|
Class-map
|
Class of traffic being displayed. Output is displayed for each configured class in the policy. The choice for implementing
class matches (for example, match-all or match-any) can also appear next to the traffic class.
|
|
packets and bytes
|
Number of packets (also shown in bytes) identified as belonging to the class of traffic being displayed.
|
|
offered rate
|
Rate, in kbps, of packets coming in to the class.
|
Note
|
If the packets are compressed over an outgoing interface, the improved packet rate achieved by packet compression is not
reflected in the offered rate. Also, if the packets are classified
before they enter a combination of tunnels (for example, a generic routing encapsulation (GRE) tunnel and an IP Security (IPSec)
tunnel), the offered rate does not include all the extra overhead associated with tunnel encapsulation in general. Depending
on the configuration, the offered rate may include no overhead, may include the overhead for only
one tunnel encapsulation, or may include the overhead for
all tunnel encapsulations. In most of the GRE and IPSec tunnel configurations, the offered rate includes the overhead for GRE
tunnel encapsulation only.
|
|
|
drop rate
|
Rate, in kbps, at which packets are dropped from the class. The drop rate is calculated by subtracting the number of successfully
transmitted packets from the offered rate.
|
|
Note
|
In distributed architecture platforms (such as the Cisco 7500 series platform), the value of the transfer rate, calculated
as the difference between the offered rate and the drop rate counters, can sporadically deviate from the average by up to
20 percent or more. This can occur while no corresponding burst is registered by independent traffic analyser equipment.
|
|
|
|
Match
|
Match criteria specified for the class of traffic. Choices include criteria such as IP precedence, IP differentiated services
code point (DSCP) value, Multiprotocol Label Switching (MPLS) experimental (EXP) value, access groups, and QoS groups. For
more information about the variety of match criteria that are available, see the “Classifying Network Traffic” module in the
Cisco IOS Quality of Service Solutions Configuration Guide .
|
|
Fields Associated with Queueing (if Enabled)
|
|
|
Output Queue
|
The weighted fair queueing (WFQ) conversation to which this class of traffic is allocated.
|
|
Bandwidth
|
Bandwidth, in either kbps or percentage, configured for this class and the burst size.
|
|
pkts matched/bytes matched
|
Number of packets (also shown in bytes) matching this class that were placed in the queue. This number reflects the total
number of matching packets queued at any time. Packets matching this class are queued only when congestion exists. If packets
match the class but are never queued because the network was not congested, those packets are not included in this total.
However, if process switching is in use, the number of packets is always incremented even if the network is not congested.
|
|
depth/total drops/no-buffer drops
|
Number of packets discarded for this class. No-buffer indicates that no memory buffer exists to service the packet.
|
|
Fields Associated with Weighted Random Early Detection (WRED) (if Enabled)
|
|
|
exponential weight
|
Exponent used in the average queue size calculation for a WRED parameter group.
|
|
mean queue depth
|
Average queue depth based on the actual queue depth on the interface and the exponential weighting constant. It is a fluctuating
average. The minimum and maximum thresholds are compared against this value to determine drop decisions.
|
|
class
|
IP precedence level.
|
|
Transmitted pkts/bytes
|
Number of packets (also shown in bytes) passed through WRED and not dropped by WRED.
|
Note
|
If there is insufficient memory in the buffer to accommodate the packet, the packet can be dropped
after the packet passes through WRED. Packets dropped because of insufficient memory in the buffer (sometimes referred to as “no-buffer
drops”) are not taken into account by the WRED packet counter.
|
|
|
Random drop pkts/bytes
|
Number of packets (also shown in bytes) randomly dropped when the mean queue depth is between the minimum threshold value
and the maximum threshold value for the specified IP precedence level.
|
|
Tail drop pkts/bytes
|
Number of packets dropped when the mean queue depth is greater than the maximum threshold value for the specified IP precedence
level.
|
|
Minimum thresh
|
Minimum threshold. Minimum WRED threshold in number of packets.
|
|
Maximum thresh
|
Maximum threshold. Maximum WRED threshold in number of packets.
|
|
Mark prob
|
Mark probability. Fraction of packets dropped when the average queue depth is at the maximum threshold.
|
|
Fields Associated with Traffic Shaping (if Enabled)
|
|
|
Target Rate
|
Rate used for shaping traffic.
|
|
Byte Limit
|
Maximum number of bytes that can be transmitted per interval. Calculated as follows:
((Bc+Be) /8) x 1
|
|
Sustain bits/int
|
Committed burst (Bc) rate.
|
|
Excess bits/int
|
Excess burst (Be) rate.
|
|
Interval (ms)
|
Time interval value in milliseconds (ms).
|
|
Increment (bytes)
|
Number of credits (in bytes) received in the token bucket of the traffic shaper during each time interval.
|
|
Queue Depth
|
Current queue depth of the traffic shaper.
|
|
Packets
|
Total number of packets that have entered the traffic shaper system.
|
|
Bytes
|
Total number of bytes that have entered the traffic shaper system.
|
|
Packets Delayed
|
Total number of packets delayed in the queue of the traffic shaper before being transmitted.
|
|
Bytes Delayed
|
Total number of bytes delayed in the queue of the traffic shaper before being transmitted.
|
|
Shaping Active
|
Indicates whether the traffic shaper is active. For example, if a traffic shaper is active, and the traffic being sent exceeds
the traffic shaping rate, a “yes” appears in this field.
|
Examples
The following sample output of the
show policy-map interface command displays the statistics for the ATM shared port adapter interface 4/1/0.10, to which a service policy called prec-aggr-wred
(configured as shown below) is attached. Because aggregate WRED has been enabled on this interface, the class through Mark Prob statistics are aggregated by subclasses. See the table below for an explanation of the significant fields
that commonly appear in the command output.
Router(config)# policy-map prec-aggr-wred
Router(config-pmap)# class class-default
Router(config-pmap-c)# random-detect aggregate
Router(config-pmap-c)# random-detect precedence values 0 1 2 3 minimum thresh 10 maximum-thresh 100 mark-prob 10
Router(config-pmap-c)# random-detect precedence values 4 5 minimum-thresh 40 maximum-thresh 400 mark-prob 10
Router(config-pmap-c)# random-detect precedence values 6 minimum-thresh 60 maximum-thresh 600 mark-prob 10
Router(config-pmap-c)# random-detect precedence values 7 minimum-thresh 70 maximum-thresh 700 mark-prob 10
Router(config-pmap-c)# exit
Router(config-pmap)# exit
Router(config)# interface ATM4/1/0.10 point-to-point
Router(config-if)# ip address 10.0.0.2 255.255.255.0
Router(config-if)# pvc 10/110
Router(config-if)# service-policy output prec-aggr-wred
Router# show policy-map interface atm4/1/0.10
ATM4/1/0.10: VC 10/110 -
Service-policy output: prec-aggr-wred
Class-map: class-default (match-any)
0 packets, 0 bytes
5 minute offered rate 0 bps, drop rate 0 bps
Match: any
Exp-weight-constant: 9 (1/512)
Mean queue depth: 0
class Transmitted Random drop Tail drop Minimum Maximum Mark
pkts/bytes pkts/bytes pkts/bytes thresh thresh prob
0 1 2 3 0/0 0/0 0/0 10 100 1/10
4 5 0/0 0/0 0/0 40 400 1/10
6 0/0 0/0 0/0 60 600 1/10
7 0/0 0/0 0/0 70 700 1/10
Examples
The following sample output of the
show policy-map interface command displays the statistics for the ATM shared port adapter interface 4/1/0.11, to which a service policy called dscp-aggr-wred
(configured as shown below) is attached. Because aggregate WRED has been enabled on this interface, the class through Mark
Prob statistics are aggregated by subclasses. See the table below for an explanation of the significant fields that commonly
appear in the command output.
Router(config)# policy-map dscp-aggr-wred
Router(config-pmap)# class class-default
Router(config-pmap-c)# random-detect dscp-based aggregate minimum-thresh 1 maximum-thresh 10 mark-prob 10
Router(config-pmap-c)# random-detect dscp values 0 1 2 3 4 5 6 7 minimum-thresh 10 maximum-thresh 20 mark-prob 10
Router(config-pmap-c)# random-detect dscp values 8 9 10 11 minimum-thresh 10 maximum-thresh 40 mark-prob 10
Router(config-pmap-c)# exit
Router(config-pmap)# exit
Router(config)# interface ATM4/1/0.11 point-to-point
Router(config-subif)# ip address 10.0.0.2 255.255.255.0
Router(config-subif)# pvc 11/101
Router(config-subif)# service-policy output dscp-aggr-wred
Router# show policy-map interface atm4/1/0.11
ATM4/1/0.11: VC 11/101 -
Service-policy output: dscp-aggr-wred
Class-map: class-default (match-any)
0 packets, 0 bytes
5 minute offered rate 0 bps, drop rate 0 bps
Match: any
Exp-weight-constant: 0 (1/1)
Mean queue depth: 0
class Transmitted Random drop Tail drop Minimum Maximum Mark
pkts/bytes pkts/bytes pkts/bytes thresh thresh prob
default 0/0 0/0 0/0 1 10 1/10
0 1 2 3
4 5 6 7 0/0 0/0 0/0 10 20 1/10
8 9 10 11 0/0 0/0 0/0 10 40 1/10
The table below describes the significant fields shown in the display when aggregate WRED is configured for an ATM shared
port adapter.
Table 28. show policy-map interface Field Descriptions—Configured for Aggregate WRED on ATM Shared Port Adapter
|
Field
|
Description
|
|
exponential weight
|
Exponent used in the average queue size calculation for a Weighted Random Early Detection (WRED) parameter group.
|
|
mean queue depth
|
Average queue depth based on the actual queue depth on the interface and the exponential weighting constant. It is a fluctuating
average. The minimum and maximum thresholds are compared against this value to determine drop decisions.
|
|
Note
|
When Aggregate Weighted Random Early Detection (WRED) is enabled, the following WRED statistics will be aggregated based
on their subclass (either their IP precedence or differentiated services code point (DSCP) value).
|
|
|
class
|
IP precedence level or differentiated services code point (DSCP) value.
|
|
Transmitted pkts/bytes
|
Number of packets (also shown in bytes) passed through WRED and not dropped by WRED.
|
Note
|
If there is insufficient memory in the buffer to accommodate the packet, the packet can be dropped
after the packet passes through WRED. Packets dropped because of insufficient memory in the buffer (sometimes referred to as “no-buffer
drops”) are not taken into account by the WRED packet counter.
|
|
|
Random drop pkts/bytes
|
Number of packets (also shown in bytes) randomly dropped when the mean queue depth is between the minimum threshold value
and the maximum threshold value for the specified IP precedence level or DSCP value.
|
|
Tail drop pkts/bytes
|
Number of packets dropped when the mean queue depth is greater than the maximum threshold value for the specified IP precedence
level or DSCP value.
|
|
Minimum thresh
|
Minimum threshold. Minimum WRED threshold in number of packets.
|
|
Maximum thresh
|
Maximum threshold. Maximum WRED threshold in number of packets.
|
|
Mark prob
|
Mark probability. Fraction of packets dropped when the average queue depth is at the maximum threshold.
|
Examples
The following sample output shows that Frame Relay voice-adaptive traffic shaping is currently active and has 29 seconds
left on the deactivation timer. With traffic shaping active and the deactivation time set, this means that the current sending
rate on DLCI 201 is minCIR, but if no voice packets are detected for 29 seconds, the sending rate will increase to CIR.
Note
|
In HQF images for Cisco IOS Releases 12.4(20)T and later, the packets delayed and bytes delayed counters were removed for
traffic shaping classes.
|
Router# show policy interface Serial3/1.1
Serial3/1.1:DLCI 201 -
Service-policy output:MQC-SHAPE-LLQ1
Class-map:class-default (match-any)
1434 packets, 148751 bytes
30 second offered rate 14000 bps, drop rate 0 bps
Match:any
Traffic Shaping
Target/Average Byte Sustain Excess Interval Increment
Rate Limit bits/int bits/int (ms) (bytes)
63000/63000 1890 7560 7560 120 945
Adapt Queue Packets Bytes Packets Bytes Shaping
Active Depth Delayed Delayed Active
BECN 0 1434 162991 26 2704 yes
Voice Adaptive Shaping active, time left 29 secs
The table below describes the significant fields shown in the display. Significant fields that are not described in the table
below are described in the table above (for “show policy-map interface Field Descriptions”).
Table 29. show policy-map interface Field Descriptions—Configured for Frame Relay Voice-Adaptive Traffic Shaping
|
Field
|
Description
|
|
Voice Adaptive Shaping active/inactive
|
Indicates whether Frame Relay voice-adaptive traffic shaping is active or inactive.
|
|
time left
|
Number of seconds left on the Frame Relay voice-adaptive traffic shaping deactivation timer.
|
Examples
The following is sample output from the
show policy-map interface command when two-rate traffic policing has been configured. In the example below, 1.25 Mbps of traffic is sent (“offered”)
to a policer class.
Router# show policy-map interface serial3/0
Serial3/0
Service-policy output: policy1
Class-map: police (match all)
148803 packets, 36605538 bytes
30 second offered rate 1249000 bps, drop rate 249000 bps
Match: access-group 101
police:
cir 500000 bps, conform-burst 10000, pir 1000000, peak-burst 100000
conformed 59538 packets, 14646348 bytes; action: transmit
exceeded 59538 packets, 14646348 bytes; action: set-prec-transmit 2
violated 29731 packets, 7313826 bytes; action: drop
conformed 499000 bps, exceed 500000 bps violate 249000 bps
Class-map: class-default (match-any)
19 packets, 1990 bytes
30 seconds offered rate 0 bps, drop rate 0 bps
Match: any
The two-rate traffic policer marks 500 kbps of traffic as conforming, 500 kbps of traffic as exceeding, and 250 kbps of traffic
as violating the specified rate. Packets marked as conforming will be sent as is, and packets marked as exceeding will be
marked with IP Precedence 2 and then sent. Packets marked as violating the specified rate are dropped.
The table below describes the significant fields shown in the display.
Table 30. show policy-map interface Field Descriptions—Configured for Two-Rate Traffic Policing
|
Field
|
Description
|
|
police
|
Indicates that the
police command has been configured to enable traffic policing. Also, displays the specified CIR, conform burst size, peak information
rate (PIR), and peak burst size used for marking packets.
|
|
conformed
|
Displays the action to be taken on packets conforming to a specified rate. Displays the number of packets and bytes on which
the action was taken.
|
|
exceeded
|
Displays the action to be taken on packets exceeding a specified rate. Displays the number of packets and bytes on which
the action was taken.
|
|
violated
|
Displays the action to be taken on packets violating a specified rate. Displays the number of packets and bytes on which
the action was taken.
|
Examples
The following is sample output from the
show policy-map command when the Policer Enhancement—Multiple Actions feature has been configured. The sample output from the
show policy-map interface command displays the statistics for the serial 3/2 interface, to which a service policy called “police” (configured as shown
below) is attached.
policy-map police
class class-default
police cir 1000000 pir 2000000
conform-action transmit
exceed-action set-prec-transmit 4
exceed-action set-frde-transmit
violate-action set-prec-transmit 2
violate-action set-frde-transmit
Router# show policy-map interface serial3/2
Serial3/2: DLCI 100 -
Service-policy output: police
Class-map: class-default (match-any)
172984 packets, 42553700 bytes
5 minute offered rate 960000 bps, drop rate 277000 bps
Match: any
police:
cir 1000000 bps, bc 31250 bytes, pir 2000000 bps, be 31250 bytes
conformed 59679 packets, 14680670 bytes; actions:
transmit
exceeded 59549 packets, 14649054 bytes; actions:
set-prec-transmit 4
set-frde-transmit
violated 53758 packets, 13224468 bytes; actions:
set-prec-transmit 2
set-frde-transmit
conformed 340000 bps, exceed 341000 bps, violate 314000 bps
The sample output from
show policy-map interface command shows the following:
-
59679 packets were marked as conforming packets (that is, packets conforming to the CIR) and were transmitted unaltered.
-
59549 packets were marked as exceeding packets (that is, packets exceeding the CIR but not exceeding the PIR). Therefore,
the IP Precedence value of these packets was changed to an IP Precedence level of 4, the discard eligibility (DE) bit was
set to 1, and the packets were transmitted with these changes.
-
53758 packets were marked as violating packets (that is, exceeding the PIR). Therefore, the IP Precedence value of these
packets was changed to an IP Precedence level of 2, the DE bit was set to 1, and the packets were transmitted with these changes.
Note
|
Actions are specified by using the
action argument of the
police command. For more information about the available actions, see the
police command reference page.
|
The table below describes the significant fields shown in the display.
Table 31. show policy-map interface Field Descriptions—Configured for Multiple Traffic Policing Actions
|
Field
|
Description
|
|
police
|
Indicates that the
police command has been configured to enable traffic policing. Also, displays the specified CIR, conform burst size (BC), PIR, and
peak burst size (BE) used for marking packets.
|
|
conformed, packets, bytes, actions
|
Displays the number of packets (also shown in bytes) marked as conforming to a specified rate and the actions taken on the
packet. If there are multiple actions, each action is listed separately.
|
|
exceeded, packets, bytes, actions
|
Displays the number of packets (also shown in bytes) marked as exceeding a specified rate and the actions taken on the packet.
If there are multiple actions, each action is listed separately.
|
|
violated, packets, bytes, actions
|
Displays the number of packets (also shown in bytes) marked as violating a specified rate and the actions taken on the packet.
If there are multiple actions, each action is listed separately.
|
Examples
The following is sample output from the
show policy-map interface command when the WRED — Explicit Congestion Notification (ECN) feature has been configured. The words “explicit congestion
notification” included in the output indicate that ECN has been enabled.
Router# show policy-map interface Serial4/1
Serial4/1
Service-policy output:policy_ecn
Class-map:prec1 (match-all)
1000 packets, 125000 bytes
30 second offered rate 14000 bps, drop rate 5000 bps
Match:ip precedence 1
Weighted Fair Queueing
Output Queue:Conversation 42
Bandwidth 20 (%)
Bandwidth 100 (kbps)
(pkts matched/bytes matched) 989/123625
(depth/total drops/no-buffer drops) 0/455/0
exponential weight:9
explicit congestion notification
mean queue depth:0
class Transmitted Random drop Tail drop Minimum Maximum Mark
pkts/bytes pkts/bytes pkts/bytes threshold threshold probability
0 0/0 0/0 0/0 20 40 1/10
1 545/68125 0/0 0/0 22 40 1/10
2 0/0 0/0 0/0 24 40 1/10
3 0/0 0/0 0/0 26 40 1/10
4 0/0 0/0 0/0 28 40 1/10
5 0/0 0/0 0/0 30 40 1/10
6 0/0 0/0 0/0 32 40 1/10
7 0/0 0/0 0/0 34 40 1/10
rsvp 0/0 0/0 0/0 36 40 1/10
class ECN Mark
pkts/bytes
0 0/0
1 43/5375
2 0/0
3 0/0
4 0/0
5 0/0
6 0/0
7 0/0
rsvp 0/0
The table below describes the significant fields shown in the display.
Table 32. show policy-map interface Field Descriptions—Configured for ECN
|
Field
|
Description
|
|
explicit congestion notification
|
Indication that Explicit Congestion Notification is enabled.
|
|
mean queue depth
|
Average queue depth based on the actual queue depth on the interface and the exponential weighting constant. It is a moving
average. The minimum and maximum thresholds are compared against this value to determine drop decisions.
|
|
class
|
IP precedence value.
|
|
Transmitted pkts/bytes
|
Number of packets (also shown in bytes) passed through WRED and not dropped by WRED.
|
Note
|
If there is insufficient memory in the buffer to accommodate the packet, the packet can be dropped
after the packet passes through WRED. Packets dropped because of insufficient memory in the buffer (sometimes referred to as “no-buffer
drops”) are not taken into account by the WRED packet counter.
|
|
|
Random drop pkts/bytes
|
Number of packets (also shown in bytes) randomly dropped when the mean queue depth is between the minimum threshold value
and the maximum threshold value for the specified IP precedence value.
|
|
Tail drop pkts/bytes
|
Number of packets dropped when the mean queue depth is greater than the maximum threshold value for the specified IP precedence
value.
|
|
Minimum threshold
|
Minimum WRED threshold in number of packets.
|
|
Maximum threshold
|
Maximum WRED threshold in number of packets.
|
|
Mark probability
|
Fraction of packets dropped when the average queue depth is at the maximum threshold.
|
|
ECN Mark pkts/bytes
|
Number of packets (also shown in bytes) marked by ECN.
|
Examples
The following sample output from the
show policy-map interface command shows the RTP header compression has been configured for a class called “prec2” in the policy map called “p1”.
The
show policy-map interface command output displays the type of header compression configured (RTP), the interface to which the policy map called “p1”
is attached (Serial 4/1), the total number of packets, the number of packets compressed, the number of packets saved, the
number of packets sent, and the rate at which the packets were compressed (in bits per second (bps)).
In this example, User Datagram Protocol (UDP)/RTP header compressions have been configured, and the compression statistics
are included at the end of the display.
Router# show policy-map interface Serial4/1
Serial4/1
Service-policy output:p1
Class-map:class-default (match-any)
1005 packets, 64320 bytes
30 second offered rate 16000 bps, drop rate 0 bps
Match:any
compress:
header ip rtp
UDP/RTP Compression:
Sent:1000 total, 999 compressed,
41957 bytes saved, 17983 bytes sent
3.33 efficiency improvement factor
99% hit ratio, five minute miss rate 0 misses/sec, 0 max
rate 5000 bps
The table below describes the significant fields shown in the display.
Table 33. show policy-map interface Field Descriptions—Configured for Class-Based RTP and TCP Header Compression
|
Field
|
Description
|
|
Service-policy output
|
Name of the output service policy applied to the specified interface or VC.
|
|
Class-map
|
Class of traffic being displayed. Output is displayed for each configured class in the policy. The choice for implementing
class matches (for example, match-all or match-any) can also appear next to the traffic class.
|
|
packets, bytes
|
Number of packets (also shown in bytes) identified as belonging to the class of traffic being displayed.
|
|
offered rate
|
Rate, in kbps, of packets coming in to the class.
|
Note
|
If the packets are compressed over an outgoing interface, the improved packet rate achieved by packet compression is not
reflected in the offered rate. Also, if the packets are classified
before they enter a combination of tunnels (for example, a generic routing encapsulation (GRE) tunnel and an IP Security (IPSec)
tunnel), the offered rate does not include all the extra overhead associated with tunnel encapsulation in general. Depending
on the configuration, the offered rate may include no overhead, may include the overhead for only
one tunnel encapsulation, or may include the overhead for
all tunnel encapsulations. In most of the GRE and IPSec tunnel configurations, the offered rate includes the overhead for GRE
tunnel encapsulation only.
|
|
|
UDP/RTP Compression
|
Indicates that RTP header compression has been configured for the class.
|
|
Sent total
|
Count of every packet sent, both compressed packets and full-header packets.
|
|
Sent compressed
|
Count of number of compressed packets sent.
|
|
bytes saved
|
Total number of bytes saved (that is, bytes not needing to be sent).
|
|
bytes sent
|
Total number of bytes sent for both compressed and full-header packets.
|
|
efficiency improvement factor
|
The percentage of increased bandwidth efficiency as a result of header compression. For example, with RTP streams, the efficiency
improvement factor can be as much as 2.9 (or 290 percent).
|
|
hit ratio
|
Used mainly for troubleshooting purposes, this is the percentage of packets found in the context database. In most instances,
this percentage should be high.
|
|
five minute miss rate
|
The number of new traffic flows found in the last five minutes.
|
|
misses/sec max
|
The average number of new traffic flows found per second, and the highest rate of new traffic flows to date.
|
|
rate
|
The actual traffic rate (in bits per second) after the packets are compressed.
|
Note
|
A number in parentheses may appear next to the service-policy output name and the class-map name. The number is for Cisco
internal use only and can be disregarded.
|
Examples
The following sample output from the
show policy-map interface command displays the statistics for the Serial2/0 interface, to which a policy map called “policy1” is attached. The discarding
action has been specified for all the packets belonging to a class called “c1.” In this example, 32000 bps of traffic is sent
(“offered”) to the class and all of them are dropped. Therefore, the drop rate shows 32000 bps.
Router# show policy-map interface
Serial2/0
Serial2/0
Service-policy output: policy1
Class-map: c1 (match-all)
10184 packets, 1056436 bytes
5 minute offered rate 32000 bps, drop rate 32000 bps
Match: ip precedence 0
drop
The table below describes the significant fields shown in the display.
Table 34. show policy-map interface Field Descriptions—Configured for MQC Unconditional Packet Discard
|
Field
|
Description
|
|
Service-policy output
|
Name of the output service policy applied to the specified interface or VC.
|
|
Class-map
|
Class of traffic being displayed. Output is displayed for each configured class in the policy. The choice for implementing
class matches (for example, match-all or match-any) can also appear next to the traffic class.
|
|
packets, bytes
|
Number of packets (also shown in bytes) identified as belonging to the class of traffic being displayed.
|
|
offered rate
|
Rate, in kbps, of packets coming in to the class.
|
Note
|
If the packets are compressed over an outgoing interface, the improved packet rate achieved by packet compression is not
reflected in the offered rate. Also, if the packets are classified
before they enter a combination of tunnels (for example, a generic routing encapsulation (GRE) tunnel and an IP Security (IPSec)
tunnel), the offered rate does not include all the extra overhead associated with tunnel encapsulation in general. Depending
on the configuration, the offered rate may include no overhead, may include the overhead for only
one tunnel encapsulation, or may include the overhead for
all tunnel encapsulations. In most of the GRE and IPSec tunnel configurations, the offered rate includes the overhead for GRE
tunnel encapsulation only.
|
|
|
drop rate
|
Rate, in kbps, at which packets are dropped from the class. The drop rate is calculated by subtracting the number of successfully
transmitted packets from the offered rate.
|
|
Note
|
In distributed architecture platforms (such as the Cisco 7500), the value of the transfer rate, calculated as the difference
between the offered rate and the drop rate counters, can sporadically deviate from the average by up to 20 percent or more.
This can occur while no corresponding burst is registered by independent traffic analyser equipment.
|
|
|
Match
|
Match criteria specified for the class of traffic. Choices include criteria such as the Layer 3 packet length, IP precedence,
IP DSCP value, MPLS experimental value, access groups, and QoS groups. For more information about the variety of match criteria
that are available, see the “Classifying Network Traffic” module in the
Cisco IOS Quality of Service Solutions Configuration Guide .
|
|
drop
|
Indicates that the packet discarding action for all the packets belonging to the specified class has been configured.
|
Note
|
A number in parentheses may appear next to the service-policy output name and the class-map name. The number is for Cisco
internal use only and can be disregarded.
|
Examples
The following sample output from the
show policy-map interface command shows traffic policing configured using a CIR based on a bandwidth of 20 percent. The CIR and committed burst (Bc)
in milliseconds (ms) are included in the display.
Router# show policy-map interface Serial3/1
Service-policy output: mypolicy
Class-map: gold (match-any)
0 packets, 0 bytes
5 minute offered rate 0 bps, drop rate 0 bps
Match: any
police:
cir 20 % bc 10 ms
cir 2000000 bps, bc 2500 bytes
pir 40 % be 20 ms
pir 4000000 bps, be 10000 bytes
conformed 0 packets, 0 bytes; actions:
transmit
exceeded 0 packets, 0 bytes; actions:
drop
violated 0 packets, 0 bytes; actions:
drop
conformed 0 bps, exceed 0 bps, violate 0 bps
The table below describes the significant fields shown in the display. A number in parentheses may appear next to the service-policy
output name and the class-map name. The number is for Cisco internal use only and can be disregarded.
Table 35. show policy-map interface Field Descriptions—Configured for Percentage-Based Policing and Shaping.
|
Field
|
Description
|
|
Service-policy output
|
Name of the output service policy applied to the specified interface or VC.
|
|
Class-map
|
Class of traffic being displayed. Output is displayed for each configured class in the policy. The choice for implementing
class matches (for example, match-all or match-any) can also appear next to the traffic class.
|
|
packets, bytes
|
Number of packets (also shown in bytes) identified as belonging to the class of traffic being displayed.
|
|
offered rate
|
Rate, in kbps, of packets coming in to the class.
|
Note
|
If the packets are compressed over an outgoing interface, the improved packet rate achieved by packet compression is not
reflected in the offered rate. Also, if the packets are classified
before they enter a combination of tunnels (for example, a generic routing encapsulation (GRE) tunnel and an IP Security (IPSec)
tunnel), the offered rate does not include all the extra overhead associated with tunnel encapsulation in general. Depending
on the configuration, the offered rate may include no overhead, may include the overhead for only
one tunnel encapsulation, or may include the overhead for
all tunnel encapsulations. In most of the GRE and IPSec tunnel configurations, the offered rate includes the overhead for GRE
tunnel encapsulation only.
|
|
|
police
|
Indicates that traffic policing based on a percentage of bandwidth has been enabled. Also, displays the bandwidth percentage,
the CIR, and the committed burst (Bc) size in ms.
|
|
conformed, actions
|
Displays the number of packets and bytes marked as conforming to the specified rates, and the action to be taken on those
packets.
|
|
exceeded, actions
|
Displays the number of packets and bytes marked as exceeding the specified rates, and the action to be taken on those packets.
|
Examples
The following sample output from the
show policy-map interface command (shown below) displays the statistics for the serial 3/2 interface. Traffic shaping has been enabled on this interface,
and an average rate of 20 percent of the bandwidth has been specified.
Note
|
In HQF images for Cisco IOS Releases 12.4(20)T and later, the packets delayed and bytes delayed counters were removed for
traffic shaping classes.
|
Router# show policy-map interface Serial3/2
Serial3/2
Service-policy output: p1
Class-map: c1 (match-all)
0 packets, 0 bytes
5 minute offered rate 0 bps, drop rate 0 bps
Match: any
Traffic Shaping
Target/Average Byte Sustain Excess Interval Increment Adapt
Rate Limit bits/int bits/int (ms) (bytes) Active
20 % 10 (ms) 20 (ms)
201500/201500 1952 7808 7808 38 976 -
Queue Packets Bytes Packets Bytes Shaping
Depth Delayed Delayed Active
0 0 0 0 0 no
The table below describes the significant fields shown in the display. A number in parentheses may appear next to the service-policy
output name, class-map name, and match criteria information. The number is for Cisco internal use only and can be disregarded.
Table 36. show policy-map interface Field Descriptions—Configured for Percentage-Based Policing and Shaping (with Traffic Shaping Enabled).
|
Field
|
Description
|
|
Service-policy output
|
Name of the output service policy applied to the specified interface or VC.
|
|
Class-map
|
Class of traffic being displayed. Output is displayed for each configured class in the policy. The choice for implementing
class matches (for example, match-all or match-any) can also appear next to the traffic class.
|
|
packets, bytes
|
Number of packets (also shown in bytes) identified as belonging to the class of traffic being displayed.
|
|
offered rate
|
Rate, in kbps, of packets coming in to the class.
|
Note
|
If the packets are compressed over an outgoing interface, the improved packet rate achieved by packet compression is not
reflected in the offered rate. Also, if the packets are classified
before they enter a combination of tunnels (for example, a generic routing encapsulation (GRE) tunnel and an IP Security (IPSec)
tunnel), the offered rate does not include all the extra overhead associated with tunnel encapsulation in general. Depending
on the configuration, the offered rate may include no overhead, may include the overhead for only
one tunnel encapsulation, or may include the overhead for
all tunnel encapsulations. In most of the GRE and IPSec tunnel configurations, the offered rate includes the overhead for GRE
tunnel encapsulation only.
|
|
|
drop rate
|
Rate, in kbps, at which packets are dropped from the class. The drop rate is calculated by subtracting the number of successfully
transmitted packets from the offered rate.
|
|
Match
|
Match criteria specified for the class of traffic. Choices include criteria such as the Layer 3 packet length, IP precedence,
IP DSCP value, MPLS experimental value, access groups, and quality of service (QoS) groups. For more information about the
variety of match criteria that are available, see the “Classifying Network Traffic” module in the
Quality of Service Solutions Configuration Guide.
|
|
Traffic Shaping
|
Indicates that traffic shaping based on a percentage of bandwidth has been enabled.
|
|
Target/Average Rate
|
Rate (percentage) used for shaping traffic and the number of packets meeting that rate.
|
|
Byte Limit
|
Maximum number of bytes that can be transmitted per interval. Calculated as follows:
((Bc+Be) /8 ) x 1
|
|
Sustain bits/int
|
Committed burst (Bc) rate.
|
|
Excess bits/int
|
Excess burst (Be) rate.
|
|
Interval (ms)
|
Time interval value in milliseconds (ms).
|
|
Increment (bytes)
|
Number of credits (in bytes) received in the token bucket of the traffic shaper during each time interval.
|
|
Adapt Active
|
Indicates whether adaptive shaping is enabled.
|
|
Queue Depth
|
Current queue depth of the traffic shaper.
|
|
Packets
|
Total number of packets that have entered the traffic shaper system.
|
|
Bytes
|
Total number of bytes that have entered the traffic shaper system.
|
|
Packets Delayed
|
Total number of packets delayed in the queue of the traffic shaper before being transmitted.
|
Note
|
In Cisco IOS Release 12.4(20)T, this counter was removed.
|
|
|
Bytes Delayed
|
Total number of bytes delayed in the queue of the traffic shaper before being transmitted.
|
Note
|
In Cisco IOS Release 12.4(20)T, this counter was removed.
|
|
|
Shaping Active
|
Indicates whether the traffic shaper is active. For example, if a traffic shaper is active, and the traffic being sent exceeds
the traffic shaping rate, a “yes” appears in this field.
|
Examples
The following sample output from the
show policy-map interface command displays the packet statistics for the Ethernet4/1 interface, to which a service policy called “mypolicy” is attached.
The Layer 3 packet length has been specified as a match criterion for the traffic in the class called “class1”.
Router# show policy-map interface Ethernet4/1
Ethernet4/1
Service-policy input: mypolicy
Class-map: class1 (match-all)
500 packets, 125000 bytes
5 minute offered rate 4000 bps, drop rate 0 bps
Match: packet length min 100 max 300
QoS Set
qos-group 20
Packets marked 500
The table below describes the significant fields shown in the display. A number in parentheses may appear next to the service-policy
input name, class-map name, and match criteria information. The number is for Cisco internal use only and can be disregarded.
Table 37. show policy-map interface Field Descriptions—Configured for Packet Classification Based on Layer 3 Packet Length.
|
Field
|
Description
|
|
Service-policy input
|
Name of the input service policy applied to the specified interface or VC.
|
|
Class-map
|
Class of traffic being displayed. Output is displayed for each configured class in the policy. The choice for implementing
class matches (for example, match-all or match-any) can also appear next to the traffic class.
|
|
packets, bytes
|
Number of packets (also shown in bytes) identified as belonging to the class of traffic being displayed.
|
|
offered rate
|
Rate, in kbps, of packets coming in to the class.
|
Note
|
If the packets are compressed over an outgoing interface, the improved packet rate achieved by packet compression is not
reflected in the offered rate. Also, if the packets are classified
before they enter a combination of tunnels (for example, a generic routing encapsulation (GRE) tunnel and an IP Security (IPSec)
tunnel), the offered rate does not include all the extra overhead associated with tunnel encapsulation in general. Depending
on the configuration, the offered rate may include no overhead, may include the overhead for only
one tunnel encapsulation, or may include the overhead for
all tunnel encapsulations. In most of the GRE and IPSec tunnel configurations, the offered rate includes the overhead for GRE
tunnel encapsulation only.
|
|
|
drop rate
|
Rate, in kbps, at which packets are dropped from the class. The drop rate is calculated by subtracting the number of successfully
transmitted packets from the offered rate.
|
|
Match
|
Match criteria specified for the class of traffic. Choices include criteria such as the Layer 3 packet length, IP precedence,
IP DSCP value, MPLS experimental value, access groups, and QoS groups.
|
|
QoS Set, qos-group, Packets marked
|
Indicates that class-based packet marking based on the QoS group has been configured. Includes the qos-group number and the
number of packets marked.
|
Examples
The following sample output of the
show policy-map interface command shows the service policies attached to a FastEthernet subinterface. In this example, a service policy called “policy1”
has been attached. In “policy1”, a table map called “table-map1” has been configured. The values in “table-map1” will be used
to map the precedence values to the corresponding class of service (CoS) values.
Router# show policy-map interface
FastEthernet1/0.1
Service-policy input: policy1
Class-map: class-default (match-any)
0 packets, 0 bytes
5 minute offered rate 0 bps, drop rate 0 bps
Match: any
QoS Set
precedence cos table table-map1
Packets marked 0
The table below describes the fields shown in the display. A number in parentheses may appear next to the service-policy
input name and the class-map name. The number is for Cisco internal use only and can be disregarded.
Table 38. show policy-map interface Field Descriptions—Configured for Enhanced Packet Marking.
|
Field
|
Description
|
|
Service-policy input
|
Name of the input service policy applied to the specified interface or VC.
|
|
Class-map
|
Class of traffic being displayed. Output is displayed for each configured class in the policy. The choice for implementing
class matches (for example, match-all or match-any) can also appear next to the traffic class.
|
|
packets, bytes
|
Number of the packets (also shown in bytes) identified as belonging to the class of traffic being displayed.
|
|
offered rate
|
Rate, in kbps, of the packets coming into the class.
|
|
Match
|
Match criteria specified for the class of traffic. Choices include criteria such as Precedence, IP differentiated services
code point (DSCP) value, Multiprotocol Label Switching (MPLS) experimental value, access groups, and quality of service (QoS)
group (set). For more information about the variety of match criteria that are available, see the “Classifying Network Traffic”
module in the
Quality of Service Solutions Configuration Guide.
|
|
QoS Set
|
Indicates that QoS group (set) has been configured for the particular class.
|
|
precedence cos table table-map1
|
Indicates that a table map (called “table-map1”) has been used to determine the precedence value. The precedence value will
be set according to the CoS value defined in the table map.
|
|
Packets marked
|
Total number of packets marked for the particular class.
|
Examples
The following is sample output from the
show policy-map interface command. This sample displays the statistics for the serial 2/0 interface on which traffic policing has been enabled. The
committed (conform) burst (bc) and excess (peak) burst (be) are specified in milliseconds (ms).
Router# show policy-map interface serial2/0
Serial2/0
Service-policy output: policy1 (1050)
Class-map: class1 (match-all) (1051/1)
0 packets, 0 bytes
5 minute offered rate 0 bps, drop rate 0 bps
Match: ip precedence 0 (1052)
police:
cir 20 % bc 300 ms
cir 409500 bps, bc 15360 bytes
pir 40 % be 400 ms
pir 819000 bps, be 40960 bytes
conformed 0 packets, 0 bytes; actions:
transmit
exceeded 0 packets, 0 bytes; actions:
drop
violated 0 packets, 0 bytes; actions:
drop
conformed 0 bps, exceed 0 bps, violate 0 bps
Class-map: class-default (match-any) (1054/0)
0 packets, 0 bytes
5 minute offered rate 0 bps, drop rate 0 bps
Match: any (1055)
0 packets, 0 bytes
5 minute rate 0 bps
In this example, the CIR and PIR are displayed in bps, and both the committed burst (bc) and excess burst (be) are displayed
in bits.
The CIR, PIR bc, and be are calculated on the basis of the formulas described below.
Examples
When calculating the CIR, the following formula is used:
According to the output from the
show interfaces command for the serial 2/0 interface, the interface has a bandwidth (BW) of 2048 kbps.
Router# show interfaces serial2/0
Serial2/0 is administratively down, line protocol is down
Hardware is M4T
MTU 1500 bytes, BW 2048 Kbit, DLY 20000 usec, rely 255/255, load 1/255
The following values are used for calculating the CIR:
20 % * 2048 kbps = 409600 bps
Examples
When calculating the PIR, the following formula is used:
According to the output from the
show interfaces command for the serial 2/0 interface, the interface has a bandwidth (BW) of 2048 kbps.
Router# show interfaces serial2/0
Serial2/0 is administratively down, line protocol is down
Hardware is M4T
MTU 1500 bytes, BW 2048 Kbit, DLY 20000 usec, rely 255/255, load 1/255
The following values are used for calculating the PIR:
40 % * 2048 kbps = 819200 bps
Note
|
Discrepancies between this total and the total shown in the output from the
show policy-map interface command can be attributed to a rounding calculation or to differences associated with the specific interface configuration.
|
Examples
When calculating the bc, the following formula is used:
The following values are used for calculating the bc:
300 ms * 409600 bps = 15360 bytes
Examples
When calculating the bc and the be, the following formula is used:
The following values are used for calculating the be:
400 ms * 819200 bps = 40960 bytes
The table below describes the significant fields shown in the display.
Table 39. show policy-map interface Field Descriptions
|
Field
|
Description
|
|
Service-policy output
|
Name of the output service policy applied to the specified interface or VC.
|
|
Class-map
|
Class of traffic being displayed. Output is displayed for each configured class in the policy. The choice for implementing
class matches (for example, match-all or match-any) can also appear next to the traffic class.
|
|
packets and bytes
|
Number of packets (also shown in bytes) identified as belonging to the class of traffic being displayed.
|
|
offered rate
|
Rate, in kbps, of packets coming in to the class.
|
|
drop rate
|
Rate, in kbps, at which packets are dropped from the class. The drop rate is calculated by subtracting the number of successfully
transmitted packets from the offered rate.
|
|
Match
|
Match criteria specified for the class of traffic. Choices include criteria such as the Layer 3 packet length, IP precedence,
IP differentiated services code point (DSCP) value, Multiprotocol Label Switching (MPLS) experimental value, access groups,
and quality of service (QoS) groups. For more information about the variety of match criteria that are available, see the
“Classifying Network Traffic” module in the
Quality of Service Solutions Configuration Guide .
|
|
police
|
Indicates that traffic policing has been enabled. Display includes the CIR, PIR (in both a percentage of bandwidth and in
bps) and the bc and be in bytes and milliseconds. Also displays the optional conform, exceed, and violate actions, if any,
and the statistics associated with these optional actions.
|
Examples
The following sample output from the
show policy-map interface command displays statistics for the Fast Ethernet 0/1 interface on which bandwidth estimates for quality of service (QoS)
targets have been generated.
The Bandwidth Estimation section indicates that bandwidth estimates for QoS targets have been defined. These targets include
the packet loss rate, the packet delay rate, and the timeframe in milliseconds. Confidence refers to the drop-one-in value
(as a percentage) of the targets. Corvil Bandwidth means the bandwidth estimate in kilobits per second.
When no drop or delay targets are specified, “none specified, falling back to drop no more than one packet in 500” appears
in the output.
Router# show policy-map interface FastEthernet0/1
FastEthernet0/1
Service-policy output: my-policy
Class-map: icmp (match-all)
199 packets, 22686 bytes
30 second offered rate 0 bps, drop rate 0 bps
Match: access-group 101
Bandwidth Estimation:
Quality-of-Service targets:
drop no more than one packet in 1000 (Packet loss < 0.10%)
delay no more than one packet in 100 by 40 (or more) milliseconds
(Confidence: 99.0000%)
Corvil Bandwidth: 1 kbits/sec
Class-map: class-default (match-any)
112 packets, 14227 bytes
30 second offered rate 0 bps, drop rate 0 bps
Match: any
Bandwidth Estimation:
Quality-of-Service targets:
<none specified, falling back to drop no more than one packet in 500
Corvil Bandwidth: 1 kbits/sec
Examples
The following sample output from the
show policy-mapinterface command shows that shaping is active (as seen in the queue depth field) with HQF enabled on the serial 4/3 interface. All
traffic is classified to the class-default queue.
Note
|
In HQF images for Cisco IOS Releases 12.4(20)T and later, the packets delayed and bytes delayed counters were removed for
traffic shaping classes.
|
Router# show policy-map interface serial4/3
Serial4/3
Service-policy output: shape
Class-map: class-default (match-any)
2203 packets, 404709 bytes
30 second offered rate 74000 bps, drop rate 14000 bps
Match: any
Queueing
queue limit 64 packets
(queue depth/total drops/no-buffer drops) 64/354/0
(pkts output/bytes output) 1836/337280
shape (average) cir 128000, bc 1000, be 1000
target shape rate 128000
lower bound cir 0, adapt to fecn 0
Service-policy : LLQ
queue stats for all priority classes:
queue limit 64 packets
(queue depth/total drops/no-buffer drops) 0/0/0
(pkts output/bytes output) 0/0
Class-map: c1 (match-all)
0 packets, 0 bytes
30 second offered rate 0 bps, drop rate 0 bps
Match: ip precedence 1
Priority: 32 kbps, burst bytes 1500, b/w exceed drops: 0
Class-map: class-default (match-any)
2190 packets, 404540 bytes
30 second offered rate 74000 bps, drop rate 14000 bps
Match: any
queue limit 64 packets
(queue depth/total drops/no-buffer drops) 63/417/0
(pkts output/bytes output) 2094/386300
Examples
Note
|
As of Cisco IOS Release 12.2(31)SB2, matching packets on the basis of VLAN ID numbers is supported on the Catalyst 1000 platform
only.
|
The following is a sample configuration in which packets are matched and classified on the basis of the VLAN ID number. In
this sample configuration, packets that match VLAN ID number 150 are placed in a class called “class1.”
Router# show class-map
Class Map match-all class1 (id 3)
Match vlan 150
Class1 is then configured as part of the policy map called “policy1.” The policy map is attached to Fast Ethernet subinterface
0/0.1.
The following sample output of the
show policy-map interface command displays the packet statistics for the policy maps attached to Fast Ethernet subinterface 0/0.1. It displays the
statistics for policy1, in which class1 has been configured.
Router# show policy-map interface
FastEthernet0/0.1
! Policy-map name.
Service-policy input: policy1
! Class configured in the policy map.
Class-map: class1 (match-all)
0 packets, 0 bytes
5 minute offered rate 0 bps, drop rate 0 bps
! VLAN ID 150 is the match criterion for the class.
Match: vlan 150
police:
cir 8000000 bps, bc 512000000 bytes
conformed 0 packets, 0 bytes; actions:
transmit
exceeded 0 packets, 0 bytes; actions:
drop
conformed 0 bps, exceed 0 bps
Class-map: class-default (match-any)
10 packets, 1140 bytes
5 minute offered rate 0 bps, drop rate 0 bps
Match: any
10 packets, 1140 bytes
5 minute rate 0 bps
The table below describes the significant fields shown in the display. A number in parentheses may appear next to the service-policy
input name and the class-map name. The number is for Cisco internal use only and can be disregarded.
Table 40. show policy-map interface Field Descriptions—Packets Matched on the Basis of VLAN ID Number.
|
Field
|
Description
|
|
Service-policy input
|
Name of the input service policy applied to the specified interface or VC.
|
|
Class-map
|
Class of traffic being displayed. Output is displayed for each configured class in the policy. The choice for implementing
class matches (for example, match-all or match-any) can also appear next to the traffic class.
|
|
packets, bytes
|
Number of the packets (also shown in bytes) identified as belonging to the class of traffic being displayed.
|
|
offered rate
|
Rate, in kbps, of the packets coming into the class.
|
|
Match
|
Match criteria specified for the class of traffic. Choices include criteria such as VLAN ID number, precedence, IP differentiated
services code point (DSCP) value, Multiprotocol Label Switching (MPLS) experimental value, access groups, and quality of service
(QoS) group (set). For more information about the variety of match criteria that are available, see the “Classifying Network
Traffic” module in the
Cisco IOS Quality of Service Solutions Configuration Guide .
|
Examples
The following example shows how to display the statistics and the configurations of all the input and output policies that
are attached to an interface on a Cisco 7600 series router:
Router# show policy-map interface
FastEthernet5/36
service-policy input: max-pol-ipp5
class-map: ipp5 (match-all)
0 packets, 0 bytes
5 minute rate 0 bps
match: ip precedence 5
class ipp5
police 2000000000 2000000 conform-action set-prec-transmit 6 exceed-action p
policed-dscp-transmit
The following example shows how to display the input-policy statistics and the configurations for a specific interface on
a Cisco 7600 series router:
Router# show policy-map interface fastethernet 5/36 input
FastEthernet5/36
service-policy input: max-pol-ipp5
class-map: ipp5 (match-all)
0 packets, 0 bytes
5 minute rate 0 bps
match: ip precedence 5
class ipp5
police 2000000000 2000000 conform-action set-prec-transmit 6 exceed-action p
policed-dscp-transmit
The table below describes the significant fields shown in the display.
Table 41. show policy-map interface Field Descriptions—Cisco 7600 Series Routers
|
Field
|
Description
|
|
service-policy input
|
Name of the input service policy applied to the specified interface.
|
|
class-map
|
Class of traffic being displayed. Output is displayed for each configured class in the policy. The choice for implementing
class matches (for example, match-all or match-any) can also appear next to the traffic class.
|
|
packets, bytes
|
Number of the packets (also shown in bytes) identified as belonging to the class of traffic being displayed.
|
|
minute rate
|
Rate, in kbps, of the packets coming into the class.
|
|
match
|
Match criteria specified for the class of traffic. Choices include criteria such as VLAN ID number, precedence, IP differentiated
services code point (DSCP) value, Multiprotocol Label Switching (MPLS) experimental value, access groups, and quality of service
(QoS) group (set). For more information about the variety of match criteria that are available, see the “Classifying Network
Traffic” module in the
Cisco IOS Quality of Service Solutions Configuration Guide .
|
|
class
|
Precedence value.
|
|
police
|
Indicates that the
police command has been configured to enable traffic policing.
|
Examples
The following example shows the automatic rounding-off of the
bc and
be values, in the MQC police policy-map, to the interface’s MTU size in a Cisco 7200 series router. The rounding-off is done
only when the bc and be values are lesser than the interface’s MTU size.
Router# show policy-map interface
Service-policy output: p2
Service-policy output: p2
Class-map: class-default (match-any)
2 packets, 106 bytes
30 second offered rate 0000 bps, drop rate 0000 bps
Match: any
2 packets, 106 bytes
30 second rate 0 bps
police:
cir 10000 bps, bc 4470 bytes
pir 20000 bps, be 4470 bytes
conformed 0 packets, 0 bytes; actions:
transmit
exceeded 0 packets, 0 bytes; actions:
drop
violated 0 packets, 0 bytes; actions:
drop
conformed 0000 bps, exceed 0000 bps, violate 0000 bps
Examples
The following sample output from the show policy-map interface command shows the types of statistical information that displays
when multiple priority queues are configured. Depending upon the interface in use and the options enabled, the output that
you see may vary slightly from the output shown below.
Router# show policy-map interface
Serial2/1/0
Service-policy output: P1
Queue statistics for all priority classes:
.
.
.
Class-map: Gold (match-all)
0 packets, 0 bytes /*Updated for each priority level configured.*/
5 minute offered rate 0 bps, drop rate 0 bps
Match: ip precedence 2
Priority: 0 kbps, burst bytes 1500, b/w exceed drops: 0
Priority Level 4:
0 packets, 0 bytes
Examples
The following sample output from the show policy-map interface command indicates that bandwidth-remaining ratios are configured
for class queues. As shown in the example, the classes precedence_0, precedence_1, and precedence_2 have bandwidth-remaining
ratios of 20, 40, and 60, respectively.
Router# show policy-map interface GigabitEthernet1/0/0.10
Service-policy output: vlan10_policy
Class-map: class-default (match-any)
0 packets, 0 bytes
30 second offered rate 0 bps, drop rate 0 bps
Match: any
0 packets, 0 bytes
30 second rate 0 bps
Queueing
queue limit 250 packets
(queue depth/total drops/no-buffer drops) 0/0/0
(pkts output/bytes output) 0/0
shape (average) cir 1000000, bc 4000, be 4000
target shape rate 1000000
bandwidth remaining ratio 10
Service-policy : child_policy
Class-map: precedence_0 (match-all)
0 packets, 0 bytes
30 second offered rate 0 bps, drop rate 0 bps
Match: ip precedence 0
Queueing
queue limit 62 packets
(queue depth/total drops/no-buffer drops) 0/0/0
(pkts output/bytes output) 0/0
shape (average) cir 500000, bc 2000, be 2000
target shape rate 500000
bandwidth remaining ratio 20
Class-map: precedence_1 (match-all)
0 packets, 0 bytes
30 second offered rate 0 bps, drop rate 0 bps
Match: ip precedence 1
Queueing
queue limit 62 packets
(queue depth/total drops/no-buffer drops) 0/0/0
(pkts output/bytes output) 0/0
shape (average) cir 500000, bc 2000, be 2000
target shape rate 500000
bandwidth remaining ratio 40
Class-map: precedence_2 (match-all)
0 packets, 0 bytes
30 second offered rate 0 bps, drop rate 0 bps
Match: ip precedence 2
Queueing
queue limit 62 packets
(queue depth/total drops/no-buffer drops) 0/0/0
(pkts output/bytes output) 0/0
shape (average) cir 500000, bc 2000, be 2000
target shape rate 500000
bandwidth remaining ratio 60
Class-map: class-default (match-any)
0 packets, 0 bytes
30 second offered rate 0 bps, drop rate 0 bps
Match: any
0 packets, 0 bytes
30 second rate 0 bps
queue limit 62 packets
(queue depth/total drops/no-buffer drops) 0/0/0
(pkts output/bytes output) 0/0
The table below describes the significant fields shown in the display.
Table 42. show policy-map interface Field Descriptions—Configured for Bandwidth-Remaining Ratios
|
Field
|
Description
|
|
Service-policy output
|
Name of the output service policy applied to the specified interface.
|
|
Class-map
|
Class of traffic being displayed. Output is displayed for each configured class in the policy. The choice for implementing
class matches (for example, match-all or match-any) can also appear next to the traffic class.
|
|
packets, bytes
|
Number of the packets (also shown in bytes) identified as belonging to the class of traffic being displayed.
|
|
bandwidth remaining ratio
|
Indicates the ratio used to allocate excess bandwidth.
|
Examples
In this sample output of the
show policy-map interface command, the character string “ip dscp tunnel 3” indicates that L2TPv3 tunnel marking has been configured to set the DSCP
value to 3 in the header of a tunneled packet.
Router# show policy-map interface
Serial0
Service-policy input: tunnel
Class-map: frde (match-all)
0 packets, 0 bytes
30 second offered rate 0 bps, drop rate 0 bps
Match: fr-de
QoS Set
ip dscp tunnel 3
Packets marked 0
Class-map: class-default (match-any)
13736 packets, 1714682 bytes
30 second offered rate 0 bps, drop rate 0 bps
Match: any
13736 packets, 1714682 bytes
30 second rate 0 bps
The table below describes the significant fields shown in the display.
Table 43. show policy-map interface Field Descriptions—Configured for Tunnel Marking
|
Field
|
Description
|
|
service-policy input
|
Name of the input service policy applied to the specified interface.
|
|
class-map
|
Class of traffic being displayed. Output is displayed for each configured class in the policy. The choice for implementing
class matches (for example, match-all or match-any) can also appear next to the traffic class.
|
|
packets, bytes
|
Number of the packets (also shown in bytes) identified as belonging to the class of traffic being displayed.
|
|
offered rate
|
Rate, in kbps, of packets coming in to the class.
|
|
drop rate
|
Rate, in kbps, at which packets are dropped from the class. The drop rate is calculated by subtracting the number of successfully
transmitted packets from the offered rate.
|
|
match
|
Match criteria specified for the class of traffic. In this example, the Frame Relay Discard Eligible (DE) bit has been specified
as the match criterion.
For more information about the variety of match criteria that are available, see the “Classifying Network Traffic” module
in the
Cisco IOS Quality of Service Solutions Configuration Guide.
|
|
ip dscp tunnel
|
Indicates that tunnel marking has been configured to set the DSCP in the header of a tunneled packet to a value of 3.
|
Examples
The following output from the show policy-map interface command indicates that ATM overhead accounting is enabled for shaping
and disabled for bandwidth:
Router# show policy-map interface
Service-policy output:unit-test
Class-map: class-default (match-any)
100 packets, 1000 bytes
30 second offered rate 800 bps, drop rate 0 bps
Match: any
shape (average) cir 154400, bc 7720, be 7720
target shape rate 154400
overhead accounting: enabled
bandwidth 30% (463 kbps)
overhead accounting: disabled
queue limit 64 packets
(queue depth/total drops/no-buffer drops) 0/0/0
(packets output/bytes output) 100/1000
The table below describes the significant fields shown in the display.
Table 44. show policy-map interface Field Descriptions—Configured for Traffic Shaping Overhead Accounting for ATM
|
Field
|
Description
|
|
service-policy output
|
Name of the output service policy applied to the specified interface.
|
|
class-map
|
Class of traffic being displayed. Output is displayed for each configured class in the policy. The choice for implementing
class matches (for example, match-all or match-any) can also appear next to the traffic class.
|
|
packets, bytes
|
Number of the packets (also shown in bytes) identified as belonging to the class of traffic being displayed.
|
|
offered rate
|
Rate, in kbps, of packets coming in to the class.
|
|
drop rate
|
Rate, in kbps, at which packets are dropped from the class. The drop rate is calculated by subtracting the number of successfully
transmitted packets from the offered rate.
|
|
match
|
Match criteria specified for the class of traffic. In this example, the Frame Relay Discard Eligible (DE) bit has been specified
as the match criterion.
For more information about the variety of match criteria that are available, see the “Classifying Network Traffic” module
in the
Cisco IOS Quality of Service Solutions Configuration Guide.
|
|
target shape rate
|
Indicates that traffic shaping is enabled at the specified rate.
|
|
overhead accounting
|
Indicates whether overhead accounting is enabled or disabled for traffic shaping.
|
|
bandwidth
|
Indicates the percentage of bandwidth allocated for traffic queueing.
|
|
overhead accounting:
|
Indicates whether overhead accounting is enabled or disabled for traffic queueing.
|
Examples
The following output from the show policy-map interface command displays the configuration for Fast Ethernet interface 0/0:
Note
|
In HQF images for Cisco IOS Releases 12.4(20)T and later releases, the packets delayed and bytes delayed counters were removed
for traffic shaping classes.
|
Router# show policy-map interface FastEthernet0/0
FastEthernet0/0
Service-policy output: test1
Class-map: class-default (match-any)
129 packets, 12562 bytes
30 second offered rate 0 bps, drop rate 0 bps
Match: any
Queueing
queue limit 64 packets
(queue depth/total drops/no-buffer drops) 0/0/0
(pkts output/bytes output) 129/12562
shape (average) cir 1536000, bc 6144, be 6144
target shape rate 1536000
Service-policy : test2
queue stats for all priority classes:
queue limit 64 packets
(queue depth/total drops/no-buffer drops) 0/0/0
(pkts output/bytes output) 0/0
Class-map: RT (match-all)
0 packets, 0 bytes
30 second offered rate 0 bps, drop rate 0 bps
Match: ip dscp ef (46)
Priority: 20% (307 kbps), burst bytes 7650, b/w exceed drops: 0
Class-map: BH (match-all)
0 packets, 0 bytes
30 second offered rate 0 bps, drop rate 0 bps
Match: ip dscp af41 (34)
Queueing
queue limit 128 packets
(queue depth/total drops/no-buffer drops) 0/0/0
(pkts output/bytes output) 0/0
bandwidth 40% (614 kbps)
Class-map: BL (match-all)
0 packets, 0 bytes
30 second offered rate 0 bps, drop rate 0 bps
Match: ip dscp af21 (18)
Queueing
queue limit 64 packets
(queue depth/total drops/no-buffer drops) 0/0/0
(pkts output/bytes output) 0/0
bandwidth 35% (537 kbps)
Exp-weight-constant: 9 (1/512)
Mean queue depth: 0 packets
dscp Transmitted Random drop Tail drop Minimum Maximum Mark
pkts/bytes pkts/bytes pkts/bytes thresh thresh prob
af21 0/0 0/0 0/0 100 400 1/10
Class-map: class-default (match-any)
129 packets, 12562 bytes
30 second offered rate 0 bps, drop rate 0 bps
Match: any
queue limit 64 packets
(queue depth/total drops/no-buffer drops) 0/0/0
(pkts output/bytes output) 129/12562
The table below describes the significant fields shown in the display.
Table 45. show policy-map interface Field Descriptions—Configured for HQF
|
Field
|
Description
|
|
FastEthernet
|
Name of the interface.
|
|
service-policy output
|
Name of the output service policy applied to the specified interface.
|
|
class-map
|
Class of traffic being displayed. Output is displayed for each configured class in the policy. The choice for implementing
class matches (for example, match-all or match-any) can also appear next to the traffic class.
|
|
packets, bytes
|
Number of the packets (also shown in bytes) identified as belonging to the class of traffic being displayed.
|
|
offered rate
|
Rate, in kbps, of packets coming in to the class.
|
|
drop rate
|
Rate, in kbps, at which packets are dropped from the class. The drop rate is calculated by subtracting the number of successfully
transmitted packets from the offered rate.
|
|
Match
|
Match criteria specified for the class of traffic.
|
Note
|
For more information about the variety of match criteria that are available, see the “Classifying Network Traffic” module
in the
Cisco IOS Quality of Service Solutions Configuration Guide.
|
|
|
Queueing
|
Indicates that queueing is enabled.
|
|
queue limit
|
Maximum number of packets that a queue can hold for a class policy configured in a policy map.
|
|
bandwidth
|
Indicates the percentage of bandwidth allocated for traffic queueing.
|
|
dscp
|
Differentiated services code point (DSCP). Values can be the following:
-
0 to 63—Numerical DSCP values. The default value is 0.
-
af1 to af43—Assured forwarding (AF) DSCP values.
-
cs1 to cs7—Type of service (ToS) precedence values.
-
default—Default DSCP value.
-
ef—Expedited forwarding (EF) DSCP values.
|
Examples
The following example shows the new output fields associated with the QoS: Policies Aggregation Enhancements feature beginning
in Cisco IOS XE Release 2.6 for subscriber statistics. The new output fields begin with the label “Account QoS Statistics.”
Router# show policy-map interface port-channel 1.1
Port-channel1.1
Service-policy input: input_policy
Class-map: class-default (match-any)
0 packets, 0 bytes
5 minute offered rate 0000 bps, drop rate 0000 bps
Match: any
QoS Set
dscp default
No packet marking statistics available
Service-policy output: Port-channel_1_subscriber
Class-map: EF (match-any)
105233 packets, 6734912 bytes
5 minute offered rate 134000 bps, drop rate 0000 bps
Match: dscp ef (46)
Match: access-group name VLAN_REMARK_EF
Match: qos-group 3
Account QoS statistics
Queueing
Packets dropped 0 packets/0 bytes
QoS Set
cos 5
No packet marking statistics available
dscp ef
No packet marking statistics available
Class-map: AF4 (match-all)
105234 packets, 6734976 bytes
5 minute offered rate 134000 bps, drop rate 0000 bps
Match: dscp cs4 (32)
Account QoS statistics
Queueing
Packets dropped 0 packets/0 bytes
QoS Set
cos 4
No packet marking statistics available
Class-map: AF1 (match-any)
315690 packets, 20204160 bytes
5 minute offered rate 402000 bps, drop rate 0000 bps
Match: dscp cs1 (8)
Match: dscp af11 (10)
Match: dscp af12 (12)
Account QoS statistics
Queueing
Packets dropped 0 packets/0 bytes
QoS Set
cos 1
No packet marking statistics available
Class-map: class-default (match-any) fragment Port-channel_BE
315677 packets, 20203328 bytes
5 minute offered rate 402000 bps, drop rate 0000 bps
Match: any
Queueing
queue limit 31250 bytes
(queue depth/total drops/no-buffer drops) 0/0/0
(pkts output/bytes output) 315679/20203482
bandwidth remaining ratio 1
Examples
The following example shows how to display the policer statistics (the packet and byte count). The output displays only the
applicable count (either packets or bytes) with the actual number.
Router# show policy-map interface GigabitEthernet 3/1 input
GigabitEthernet3/1
Service-policy input: in1
Class-map: p1 (match-all)
0 packets
Match: precedence 1
QoS Set
ip precedence 7
police:
cir 20 %
cir 200000000 bps, bc 6250000 bytes
conformed 0 bytes; actions:
transmit
exceeded 0 bytes; actions:
drop
conformed 0000 bps, exceed 0000 bps
Class-map: class-default (match-any)
10000000 packets
Match: any
police:
cir 20 %
cir 200000000 bps, bc 6250000 bytes
conformed 174304448 bytes; actions:
transmit
exceeded 465695552 bytes; actions:
drop
conformed 4287000 bps, exceed 11492000 bps
Examples
The following example shows how to display the statistics and the configurations of the input and output service policies
that are attached to an interface:
Router# show policy-map interface GigabitEthernet 1/2/0
Load for five secs: 1%/0%; one minute: 1%; five minutes: 1%
Time source is hardware calendar, *23:02:40.857 pst Thu Mar 3 2011
GigabitEthernet1/2/0
Service-policy input: policy-in
Class-map: class-exp-0 (match-all)
6647740 packets, 9304674796 bytes
30 second offered rate 3234000 bps, drop rate 0 bps
Match: mpls experimental topmost 0
QoS Set
precedence 3
Packets marked 6647740
Class-map: class-default (match-any)
1386487 packets, 1903797872 bytes
30 second offered rate 658000 bps, drop rate 0 bps
Match: any
Service-policy output: policy-out
Class-map: class-pre-1 (match-all)
2041355 packets, 2857897000 bytes
30 second offered rate 986000 bps, drop rate 0 bps
Match: ip precedence 1
QoS Set
mpls experimental topmost 1
Packets marked 2041355
Class-map: class-default (match-any)
6129975 packets, 8575183331 bytes
30 second offered rate 2960000 bps, drop rate 0 bps
Match: any
The table below describes the significant fields shown in the display.
Table 46. show policy-map interface Field Descriptions—Cisco Catalyst 4000 Series Routers
|
Field
|
Description
|
|
class-map
|
Displays the class of traffic. Output is displayed for each configured class in the policy. The choice for implementing class
matches (for example, match-all or match-any) can also appear next to the traffic class.
|
|
conformed
|
Displays the action to be taken on packets conforming to a specified rate. Also displays the number of packets and bytes
on which the action was taken.
|
|
drop
|
Indicates that the packet discarding action for all the packets belonging to the specified class has been configured.
|
|
exceeded
|
Displays the action to be taken on packets exceeding a specified rate. Displays the number of packets and bytes on which
the action was taken.
|
|
match
|
Match criteria specified for the class of traffic.
|
|
packets, bytes
|
Number of the packets (also shown in bytes) identified as belonging to the class of traffic being displayed.
|
|
police
|
Indicates that the
police command has been configured to enable traffic policing. Also displays the specified CIR, conform burst size, peak information
rate (PIR), and peak burst size used for marking packets.
|
|
QoS Set
|
Indicates that QoS group (set) has been configured for the particular class.
|
|
service-policy input
|
Name of the input service policy applied to the specified interface.
|
Examples
The following example shows how to display the class maps configured for a pseudowire interface:
Router# show policy-map interface pseudowire2
pseudowire2
Service-policy output: pw_brr
Class-map: prec1 (match-all)
0 packets, 0 bytes
30 second offered rate 0000 bps, drop rate 0000 bps
Match: ip precedence 1
Queueing
queue limit 4166 packets
(queue depth/total drops/no-buffer drops) 0/0/0
(pkts output/bytes output) 0/0
bandwidth remaining ratio 1
Class-map: prec2 (match-all)
0 packets, 0 bytes
30 second offered rate 0000 bps, drop rate 0000 bps
Match: ip precedence 2
Queueing
queue limit 4166 packets
(queue depth/total drops/no-buffer drops) 0/0/0
(pkts output/bytes output) 0/0
bandwidth remaining ratio 2
Class-map: prec3 (match-all)
0 packets, 0 bytes
30 second offered rate 0000 bps, drop rate 0000 bps
Match: ip precedence 3
Queueing
queue limit 4166 packets
(queue depth/total drops/no-buffer drops) 0/0/0
(pkts output/bytes output) 0/0
bandwidth remaining ratio 3
Class-map: class-default (match-any)
0 packets, 0 bytes
30 second offered rate 0000 bps, drop rate 0000 bps
Match: any
Queueing
queue limit 4166 packets
(queue depth/total drops/no-buffer drops) 0/0/0
(pkts output/bytes output) 0/0
bandwidth remaining ratio 4
Device#
The table below describes the significant fields shown in the display.
Table 47. show policy-map interface Field Descriptions—Pseudowire Policy Map Information
|
Field
|
Description
|
|
bandwidth
|
Indicates the percentage of bandwidth allocated for traffic queueing.
|
|
Class-map
|
Displays the class of traffic. Output is displayed for each configured class in the policy. The choice for implementing class
matches (for example, match-all or match-any) can also appear next to the traffic class.
|
|
Match
|
Match criteria specified for the class of traffic.
|
|
packets, bytes
|
Number of the packets (also shown in bytes) identified as belonging to the class of traffic being displayed.
|
|
Queueing
|
Indicates that queueing is enabled.
|
|
queue limit
|
Maximum number of packets that a queue can hold for a class policy configured in a policy map.
|
|
service-policy output
|
Name of the output service policy applied to the specified interface.
|
Feedback