-
Cisco IOS Quality of Service Solutions Command Reference
-
A through C
-
D through F
-
identity policy (policy-map) through ip rsvp pq-profile
-
ip rsvp precedence through load protocol
-
match access-group through mls ip pbr
-
mls qos (global configuration mode) through mpls experimental
-
N through P
-
Q through R
-
send qdm message through show atm bundle svc statistics
-
show auto discovery qos through show ip rsvp hello client lsp detail
-
show ip rsvp hello client lsp summary through show lane qos database
-
show mls qos through wrr-queue threshold
-
Table Of Contents
show mls qos aggregate policer
show mls qos statistics-export info
show policy-map interface brief
show policy-map interface service instance
show mls qos
To display multilayer switching (MLS) quality of service (QoS) information, use the show mls qos command in privileged EXEC mode.
show mls qos [{arp | ipv6 | ip | ipx | last | mac | module [module-number]} [interface interface-number | slot slot | null 0 | port-channel number | vlan vlan-id]] [detailed]
Syntax Description
Command Modes
Privileged EXEC (#)
Command History
Usage Guidelines
The ge-wan, pos, and atm interfaces are not supported on systems that are configured with a Supervisor Engine 720.
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.
The port-channel number values from 257 to 282 are supported on the Content Switching Module (CSM) and the Firewall Services Module (FWSM) only.
Catalyst 6500 Series Switches
In Cisco IOS Release 12.2(33)SXI and later releases, the following information is included in the output of the show mls qos command:
•
Display of last 30-second counters.
•
•
The peak rates are monitored with 10-second resolution. Releases prior to Cisco IOS Release 12.2(33)SXI are monitored at 30-second resolution.
Examples
Last Logged Packet Example
This example shows how to display information about the last logged packet:
Router# show mls qos lastQoS engine last packet information:Packet was transmittedOutput TOS/DSCP: 0xC0/48[unchanged] Output COS: 0[unchanged]Aggregate policer index: 0(none)Microflow policer index: 0(none)IPv6 Example
This example shows how to display IPv6 information:
Router# show mls qos ipv6QoS Summary [IPv6]: (* - shared aggregates, Mod - switch module)Int Mod Dir Class-map DSCP Agg Trust Fl AgForward-By AgPoliced-ById Id------------------------------------------------------------------------------All 7 - Default 0 0* No 0 189115356 0Supervisor Engine 720 Example
This example shows how to display QoS information:
Router# show mls qosQoS is enabled globallyMicroflow policing is enabled globallyQoS ip packet dscp rewrite enabled globallyQoS is disabled on the following interfaces:Fa6/3 Fa6/4QoS DSCP-mutation map is enabled on the following interfaces:Fa6/5Vlan or Portchannel(Multi-Earl) policies supported: YesEgress policies supported: Yes----- Module [5] -----QoS global counters:Total packets: 164IP shortcut packets: 0Packets dropped by policing: 0IP packets with TOS changed by policing: 0IP packets with COS changed by policing: 0Non-IP packets with COS changed by policing: 0MPLS packets with EXP changed by policing: 0Supervisor Engine 2 Example
This example shows the output if you do not enter any keywords:
Router# show mls qosQoS is enabled globallyMicroflow QoS is enabled globallyQoS global counters:Total packets: 217500IP shortcut packets: 344Packets dropped by policing: 344IP packets with TOS changed by policing 18323IP packets with COS changed by policing 1602Non-IP packets with COS changed by policing 0Catalyst 6500 Series Switches Example
The show mls qos command output in Cisco IOS Release 12.2(33)SXI and later releases contains more packet counter information than in previous releases.
This example shows the Cisco IOS Release 12.2(33)SXI output with the detailed keyword:
Router# show mls qos detailedQoS is enabled globallyPolicy marking depends on port_trustQoS ip packet dscp rewrite enabled globallyInput mode for GRE Tunnel is Pipe modeInput mode for MPLS is Pipe modeVlan or Portchannel(Multi-Earl) policies supported: YesEgress policies supported: Yes----- Module [5] -----Traffic: Total pkt's 30-s pkt's peak pkts 5-min avg pps peak pps-----------------------------------------------------------------------------------Total packets: 775606 46 22 2 5IP shortcut packets: 5465402 33 16 1 1Packets dropped bypolicing: 0 0 0 0 0IP packets with TOSchanged by policing: 41 10 4 0 0IP packets with COSchanged by policing: 2 0 0 0 0Non-IP packets with COSchanged by policing: 0 0 0 0 0MPLS packets with EXPchanged by policing: 0 0 0 0 0Table 157 describes the significant fields added when you enter the detailed keyword.
Related Commands
show mls qos aggregate policer
To display information about the aggregate policer for multilayer switching (MLS) quality of service (QoS), use the show mls qos aggregate policer command in EXEC mode.
show mls qos aggregate policer [aggregate-name]
Syntax Description
Command Default
This command has no default settings.
Command Modes
EXEC
Command History
Usage Guidelines
Aggregate policing works independently on each Distributed Forwarding Card (DFC)-equipped switching module and independently on the Policy Feature Card 2 (PFC2), which supports any non-DFC-equipped switching modules. Aggregate policing does not combine flow statistics from different DFC-equipped switching modules. You can display aggregate-policing statistics for each DFC-equipped switching module, the PFC2, and any non-DFC-equipped switching modules that are supported by the PFC2.
Examples
This example shows how to display information about the aggregate policer for MLS QoS:
Router# show mls qos aggregate-policerag1 (undefined)AgId=0 [ pol1 pol2 ]ag2 64000 64000 conform-action set-dscp-transmit 56 exceed-action dropAgId=0 [ pol3 ]ag3 32000 32000 conform-action set-dscp-transmit 34 exceed-action dropIn the output, the following applies:
•
•
•
•
Related Commands
mls qos aggregate-policer
Defines a named aggregate policer for use in policy maps.
show mls qos free-agram
To display the number of free aggregate RAM indexes on the switch processor and the Distributed Forwarding Cards (DFCs), use the show mls qos free-agram command in EXEC mode.
show mls qos free-agram
Syntax Description
This command has no arguments or keywords.
Command Default
This command has no default settings.
Command Modes
EXEC
Command History
Examples
This example shows how to display the number of free aggregate RAM indexes on the switch processor and the DFCs:
Router# show mls qos free-agramTotal Number of Available AG RAM indices : 1023Module [1]Free AGIDs : 1023Module [6]Free AGIDs : 1023show mls qos maps
To display multilayer switching (MLS) quality of service (QoS) mapping information, use the show mls qos maps command in privileged EXEC mode.
Cisco 2600, 3660, 3700, 3845, 7200, 7400, and 7500 Series Routers
show mls qos maps [cos-dscp | dscp-cos]
Cisco 7600 Series Router and Catalyst 6500 Series Switch
show mls qos maps [cos-dscp | cos-mutation | dscp-cos | dscp-exp | dscp-mutation | exp-dscp | exp-mutation | ip-prec-dscp | policed-dscp]
Syntax Description
Command Default
All MLS QoS maps are displayed.
Command Modes
Privileged EXEC (#)
Command History
Usage Guidelines
Maps are used to generate an internal DSCP value, which represents the priority of the traffic. Use the show mls qos maps command without keywords to display all maps.
Examples
The following is sample output from the show mls qos maps cos-dscp command displaying the DSCP values to which each CoS value will be mapped:
Router# show mls qos maps cos-dscpCos-dscp map:cos: 0 1 2 3 4 5 6 7--------------------------------dscp: 8 8 8 8 24 32 56 56The following is sample output from the show mls qos maps dscp-cos command displaying the CoS values to which each DSCP value will be mapped:
Router# show mls qos maps dscp-cosDscp-cos map:dscp: 0 8 10 16 18 24 26 32 34 40 46 48 56-----------------------------------------------cos: 0 1 1 1 2 2 3 3 4 4 5 6 7This example shows how to display the QoS-map settings:
Router# show mls qos mapsPoliced-dscp map:0 1 2 3 4 5 6 7 8 9----------------------------------00: 00 01 02 03 04 05 06 07 08 0910: 10 11 12 13 14 15 16 17 18 1920: 20 21 22 23 24 25 26 27 28 2930: 30 31 32 33 34 35 36 37 38 3940: 40 41 42 43 44 45 46 47 48 4950: 50 51 52 53 54 55 56 57 58 5960: 60 61 62 63Dscp-cos map:0 1 2 3 4 5 6 7 8 9----------------------------------00: 00 00 00 00 00 00 00 00 01 0110: 01 01 01 01 01 01 02 02 02 0220: 02 02 02 02 03 03 03 03 03 0330: 03 03 04 04 04 04 04 04 04 0440: 05 05 05 05 05 05 05 05 06 0650: 06 06 06 06 06 06 07 07 07 0760: 07 07 07 07Cos-dscp map:cos: 0 1 2 3 4 5 6 7----------------------------------dscp: 0 8 16 24 32 40 48 56IpPrecedence-dscp map:ipprec: 0 1 2 3 4 5 6 7----------------------------------dscp: 0 8 16 24 32 40 48 56Router#In the policed DSCP and DSCP-CoS map displays, the new DSCP or CoS values are shown in the body of the table. The decade of the original DSCP value is shown in the left-side vertical column, and the units digit is in the top row. For example, the DSCP-CoS map indicates that if the original DSCP value is between 32 and 39, the CoS will be set to 4.
The CoS-DSCP and IP precedence-DSCP maps display the DSCP values to which each CoS or IP precedence value will be mapped. For example, the IP precedence-DSCP map indicates that if the original IP precedence value is 3, the DSCP will be set to 24.
This example shows how to verify the configuration of DSCP-mutation mapping:
Router# show mls qos maps | begin DSCP mutationDSCP mutation map mutmap1: (dscp= d1d2)d1 : d2 0 1 2 3 4 5 6 7 8 9-------------------------------------0 : 00 01 02 03 04 05 06 07 08 091 : 10 11 12 13 14 15 16 17 18 192 : 20 21 22 23 24 25 26 27 28 293 : 08 31 32 33 34 35 36 37 38 394 : 40 41 42 43 44 45 46 47 48 49<...Output Truncated...>Router#In the DSCP mutation map display, the marked-down DSCP values are shown in the body of the table. The first digit (d1) of the original DSCP value is in the left-side vertical column labeled d1, and the second digit (d2) is in the top row. For example, a DSCP value of 30 maps to a new DSCP value of 08.
Related Commands
show mls qos mpls
To display an interface summary for Multiprotocol Label Switching (MPLS) quality of service (QoS) classes in policy maps, use the show mls qos mpls command in user EXEC or privileged EXEC mode.
show mls qos mpls [interface-type interface-number | module slot]
Syntax Description
Command Modes
User EXEC
Privileged EXECCommand History
12.2(17a)SX
This command was introduced on the Supervisor Engine 720.
12.2(33)SRB
This command was integrated into Cisco IOS Release 12.2(33)SRB.
Usage Guidelines
This command is supported in PFC3BXL or PFC3B mode only.
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.
Examples
The following example shows an interface summary for MPLS QoS classes in policy maps:
Router# show mls qos mplsQoS Summary [MPLS]: (* - shared aggregates, Mod - switch module)Int Mod Dir Class-map DSCP Agg Trust Fl AgForward-By AgPoliced-ById Id------------------------------------------------------------------------------------------ ----------------------------Fa3/38 5 In exp2 0 1 dscp 0 378900 0Fa3/41 5 In exp4 0 3 dscp 0 0 0All 5 - Default 0 0* No 0 1191011240 0Table 158 describes the significant fields shown in the display.
Related Commands
show mls qos protocol
To display protocol pass-through information, use the show mls qos protocol command in EXEC mode.
show mls qos protocol [module number]
Syntax Description
Command Default
This command has no default settings.
Command Modes
EXEC
Command History
Examples
This example shows how to display protocol pass-through information:
Router# show mls qos protocolRIP : Passthru modeOSPF : Passthru modeND : Policing mode Cir = 32000 Burst = 1000----- Module [5] -----Routing protocol RIP is using AgId 0*Routing protocol OSPF is using AgId 0*Routing protocol ND is using AgId 1----- Module [6] -----Routing protocol RIP is using AgId 0*Routing protocol OSPF is using AgId 0*Related Commands
show mls qos statistics-export info
To display information about the multilayer switching (MLS)-statistics data-export status and configuration, use the show mls qos statistics-export info command in EXEC mode
show mls qos statistics-export info
Syntax Description
This command has no keywords or arguments.
Command Default
This command has no default settings.
Command Modes
EXEC
Command History
Usage Guidelines
Quality of service (QoS)-statistics data export is not supported on Optical Service Module (OSM) interfaces.
Examples
This example shows how to display information about the MLS-statistics data-export status and configuration:
Router# show mls qos statistics-export infoQoS Statistics Data Export Status and Configuration information---------------------------------------------------------------Export Status : enabledExport Interval : 250 secondsExport Delimiter : @Export Destination : 172.20.52.3, UDP port 514 Facility local6, Severity debugQoS Statistics Data Export is enabled on following ports:---------------------------------------------------------FastEthernet5/24QoS Statistics Data export is enabled on following shared aggregate policers:-----------------------------------------------------------------------------aggr1MQoS Statistics Data Export is enabled on following class-maps:---------------------------------------------------------------class3Related Commands
show platform qos policy-map
To display the type and number of policy maps that are configured on the router, use the show platform qos policy-map command in privileged EXEC mode.
show platform qos policy-map
Syntax Description
This command has no arguments or keywords.
Command Modes
Privileged EXEC
Command History
Usage Guidelines
On Cisco Catalyst 6500 series switches and Cisco 7600 series routers, you cannot attach a quality of service (QoS) policy map with match input vlan to an interface if you have already attached a QoS policy map to a VLAN interface (a logical interface that has been created with the interface vlan command). If you attempt to use both types of service policies, you must remove both types of service policies before you can add the policy maps.
The show platform qos policy-map command shows whether the router is currently configured for interface vlan and match input vlan service policies. It also shows the number of policy maps for each type.
Examples
The following example shows a router that has service policies configured only on VLAN interfaces:
Router# show platform qos policy-mapservice policy configured on int vlan: TRUE# of int vlan service policy instances: 3match input vlan service policy configured: FALSE# of match input vlan service policy instances: 0The following example shows a router that has service policies configured on VLAN interfaces and that has a service policy configured with match input vlan. In this configuration, you must remove all service policies from their interfaces, and then configure only one type or another.
Router# show platform qos policy-mapservice policy configured on int vlan: TRUE# of int vlan service policy instances: 1match input vlan service policy configured: TRUE# of match input vlan service policy instances: 1Table 159 describes each field shown in the show platform qos policy-map command:
Related Commands
show policy-map
To display the configuration of all classes for a specified service policy map or of all classes for all existing policy maps, use the show policy-map command in user EXEC or privileged EXEC mode.
show policy-map [policy-map]
Syntax Description
policy-map
(Optional) Name of the service policy map whose complete configuration is to be displayed. The name can be a maximum of 40 characters.
Command Default
All existing policy map configurations are displayed.
Command Modes
User EXEC (>)
Privileged EXEC (#)Command History
Usage Guidelines
The show policy-map command displays the configuration of a policy map created using the policy-map command. You can use the show policy-map command to display all class configurations comprising any existing service policy map, whether or not that policy map has been attached to an interface. The command displays:
•
•
Cisco 10000 Series Router
In Cisco IOS Release 12.2(33)SB, the output of the show policy-map command is slightly different from previous releases when the policy is an hierarchical policy.
For example, in Cisco IOS Release 12.2(33)SB output similar to the following displays when you specify a hierarchical policy in the show policy-map command:
Router# show policy-map Bronzepolicy-map bronzeclass class-defaultshape average 34386000service-policy ChildIn Cisco IOS Release 12.2(31)SB, output similar to the following displays when you specify a hierarchical policy in the show policy-map command:
Router# show policy-map Goldpolicy-map GoldClass class-defaultAverage Rate Traffic Shapingcir 34386000 (bps)service-policy Child2In Cisco IOS Release 12.2(33)SB, the output from the show policy-map command displays police actions on separate lines as shown in the following sample output:
Router# show policy-map PremiumPolicy Map PremiumClass P1prioritypolice percent 50 25 ms 0 msconform-action transmitexceed-action transmitviolate-action dropIn Cisco IOS Release 12.2(31)SB, the output from the show policy-map command displays police actions on one line as shown in the following sample output:
Router# show policy-map PremiumPolicy Map PremiumClass P2prioritypolice percent 50 25 ms 0 ms conform-action transmit exceed-action transmit violate- action dropExamples
This section provides sample output from typical show policy-map commands. Depending upon the interface or platform in use and the options enabled (for example, Weighted Fair Queueing [WFQ]), the output you see may vary slightly from the ones shown below.
•
•
•
•
•
•
•
•
•
•
Weighted Fair Queueing: Example
The following example displays the contents of the service policy map called po1. In this example, WFQ is enabled.
Router# show policy-map po1Policy Map po1 Weighted Fair Queueing Class class1 Bandwidth 937 (kbps) Max thresh 64 (packets) Class class2 Bandwidth 937 (kbps) Max thresh 64 (packets)Class class3 Bandwidth 937 (kbps) Max thresh 64 (packets) Class class4 Bandwidth 937 (kbps) Max thresh 64 (packets) Class class5 Bandwidth 937 (kbps) Max thresh 64 (packets) Class class6 Bandwidth 937 (kbps) Max thresh 64 (packets) Class class7 Bandwidth 937 (kbps) Max thresh 64 (packets) Class class8 Bandwidth 937 (kbps) Max thresh 64 (packets)The following example displays the contents of all policy maps on the router. Again, WFQ is enabled.
Router# show policy-mapPolicy Map poH1 Weighted Fair Queueing Class class1 Bandwidth 937 (kbps) Max thresh 64 (packets) Class class2 Bandwidth 937 (kbps) Max thresh 64 (packets)Class class3 Bandwidth 937 (kbps) Max thresh 64 (packets) Class class4 Bandwidth 937 (kbps) Max thresh 64 (packets) Class class5 Bandwidth 937 (kbps) Max thresh 64 (packets) Class class6 Bandwidth 937 (kbps) Max thresh 64 (packets) Class class7 Bandwidth 937 (kbps) Max thresh 64 (packets) Class class8 Bandwidth 937 (kbps) Max thresh 64 (packets)Policy Map policy2 Weighted Fair Queueing Class class1 Bandwidth 300 (kbps) Max thresh 64 (packets) Class class2 Bandwidth 300 (kbps) Max thresh 64 (packets)Class class3 Bandwidth 300 (kbps) Max thresh 64 (packets) Class class4 Bandwidth 300 (kbps) Max thresh 64 (packets) Class class5 Bandwidth 300 (kbps) Max thresh 64 (packets) Class class6 Bandwidth 300 (kbps) Max thresh 64 (packets)Table 160 describes the significant fields shown in the display.
Frame Relay Voice-Adaptive Traffic-Shaping: Example
The following sample output for the show-policy map command indicates that Frame Relay voice-adaptive traffic-shaping is configured in the class-default class in the policy map "MQC-SHAPE-LLQ1" and that the deactivation timer is set to 30 seconds.
Router# show policy-mapPolicy Map VSD1Class VOICE1Strict PriorityBandwidth 10 (kbps) Burst 250 (Bytes)Class SIGNALS1Bandwidth 8 (kbps) Max Threshold 64 (packets)Class DATA1Bandwidth 15 (kbps) Max Threshold 64 (packets)Policy Map MQC-SHAPE-LLQ1Class class-defaultTraffic ShapingAverage Rate Traffic ShapingCIR 63000 (bps) Max. Buffers Limit 1000 (Packets)Adapt to 8000 (bps)Voice Adapt Deactivation Timer 30 Secservice-policy VSD1Table 161 describes the significant fields shown in the display.
Traffic Policing: Example
The following is sample output from the show policy-map command. This sample output displays the contents of a policy map called "policy1." In policy 1, traffic policing on the basis of a committed information rate (CIR) of 20 percent has been configured, and the bc and be have been specified in milliseconds. As part of the traffic policing configuration, optional conform, exceed, and violate actions have been specified.
Router# show policy-map policy1Policy Map policy1Class class1police cir percent 20 bc 300 ms pir percent 40 be 400 msconform-action transmitexceed-action dropviolate-action dropTable 162 describes the significant fields shown in the display.
Two-Rate Traffic Policing: Example
The following is sample output from the show policy-map command when two-rate traffic policing has been configured. As shown below, two-rate traffic policing has been configured for a class called "police." In turn, the class called police has been configured in a policy map called "policy1." Two-rate traffic policing has been configured to limit traffic to an average committed rate of 500 kbps and a peak rate of 1 Mbps.
Router(config)# class-map policeRouter(config-cmap)# match access-group 101Router(config-cmap)# policy-map policy1Router(config-pmap)# class policeRouter(config-pmap-c)# police cir 500000 bc 10000 pir 1000000 be 10000 conform-action transmit exceed-action set-prec-transmit 2 violate-action dropRouter(config-pmap-c)# interface serial3/0Router(config-pmap-c)# exitRouter(config-pmap)# exitRouter(config)# interface serial3/0Router(config-if)# service-policy output policy1Router(config-if)# endThe following sample output shows the contents of the policy map called "policy1":Router# show policy-map policy1Policy Map policy1Class policepolice cir 500000 conform-burst 10000 pir 1000000 peak-burst 10000 conform-actiontransmit exceed-action set-prec-transmit 2 violate-action dropTraffic marked as conforming to the average committed rate (500 kbps) will be sent as is. Traffic marked as exceeding 500 kbps, but not exceeding 1 Mbps, will be marked with IP Precedence 2 and then sent. All traffic exceeding 1 Mbps will be dropped. The burst parameters are set to 10000 bytes.
Table 163 describes the significant fields shown in the display.
Multiple Traffic Policing Actions: Example
The following is sample output from the show policy-map command when the Policer Enhancement—Multiple Actions feature has been configured. The following sample output from the show policy-map command displays the configuration for a service policy called "police." In this service policy, traffic policing has been configured to allow multiple actions for packets marked as conforming to, exceeding, or violating the CIR or the PIR shown in the example.
Router# show policy-map policePolicy Map policeClass class-defaultpolice cir 1000000 bc 31250 pir 2000000 be 31250conform-action transmitexceed-action set-prec-transmit 4exceed-action set-frde-transmitviolate-action set-prec-transmit 2violate-action set-frde-transmitPackets conforming to the specified CIR (1000000 bps) are marked as conforming packets. These are transmitted unaltered.
Packets exceeding the specified CIR (but not the specified PIR, 2000000 bps) are marked as exceeding packets. For these packets, the IP Precedence level is set to 4, the discard eligibility (DE) bit is set to 1, and the packet is transmitted.
Packets exceeding the specified PIR are marked as violating packets. For these packets, the IP Precedence level is set to 2, the DE bit is set to 1, and the packet is transmitted.
Note
Table 164 describes the significant fields shown in the display.
Explicit Congestion Notification: Example
The following is sample output from the show policy-map command when the WRED—Explicit Congestion Notification (ECN) feature has been configured. The words "explicit congestion notification" (along with the ECN marking information) included in the output indicate that ECN has been enabled.
Router# show policy-mapPolicy Map pol1Class class-defaultWeighted Fair QueueingBandwidth 70 (%)exponential weight 9explicit congestion notificationclass min-threshold max-threshold mark-probability--------------------------------------------------------------------------------------------------------------------0 - - 1/101 - - 1/102 - - 1/103 - - 1/104 - - 1/105 - - 1/106 - - 1/107 - - 1/10rsvp - - 1/10Table 165 describes the significant fields shown in the display.
Modular QoS CLI (MQC) Unconditional Packet Discard: Example
The following example displays the contents of the policy map called "policy1." All the packets belonging to the class called "c1" are discarded.
Router# show policy-map policy1Policy Map policy1Class c1dropTable 166 describes the significant fields shown in the display.
Percentage-Based Policing and Shaping: Example
The following example displays the contents of two service policy maps—one called "policy1" and one called "policy2." In policy1, traffic policing based on a CIR of 50 percent has been configured. In policy 2, traffic shaping based on an average rate of 35 percent has been configured.
Router# show policy-map policy1Policy Map policy1 class class1 police cir percent 50Router# show policy-map policy2Policy Map policy2 class class2 shape average percent 35The following example displays the contents of the service policy map called "po1":
Router# show policy-map po1Policy Map po1 Weighted Fair Queueing Class class1 Bandwidth 937 (kbps) Max thresh 64 (packets) Class class2 Bandwidth 937 (kbps) Max thresh 64 (packets)Class class3
Bandwidth 937 (kbps) Max thresh 64 (packets)
Class class4
Bandwidth 937 (kbps) Max thresh 64 (packets)
The following example displays the contents of all policy maps on the router:Router# show policy-mapPolicy Map poH1 Weighted Fair Queueing Class class1 Bandwidth 937 (kbps) Max thresh 64 (packets) Class class2 Bandwidth 937 (kbps) Max thresh 64 (packets)Class class3 Bandwidth 937 (kbps) Max thresh 64 (packets) Class class4 Bandwidth 937 (kbps) Max thresh 64 (packets) Policy Map policy2 Weighted Fair Queueing Class class1 Bandwidth 300 (kbps) Max thresh 64 (packets) Class class2 Bandwidth 300 (kbps) Max thresh 64 (packets)Class class3 Bandwidth 300 (kbps) Max thresh 64 (packets) Class class4 Bandwidth 300 (kbps) Max thresh 64 (packets)Table 167 describes the significant fields shown in the display.
Enhanced Packet Marking: Example
The following sample output from the show policy-map command displays the configuration for policy maps called "policy1" and "policy2".
In "policy1", a table map called "table-map-cos1" has been configured to determine the precedence based on the class of service (CoS) value. Policy map "policy 1" converts and propagates the packet markings defined in the table map called "table-map-cos1".
The following sample output from the show policy-map command displays the configuration for service polices called "policy1" and "policy2". In "policy1", a table map called "table-map1" has been configured to determine the precedence according to the CoS value. In "policy2", a table map called "table-map2" has been configured to determine the CoS value according to the precedence value.
Router# show policy-map policy1Policy Map policy1Class class-defaultset precedence cos table table-map1Router# show policy-map policy2Policy Map policy2Class class-defaultset cos precedence table table-map2Table 168 describes the fields shown in the display.
Bandwidth-Remaining Ratio: Example
The following sample output for the show policy-map command indicates that the class-default class of the policy map named vlan10_policy has a bandwidth-remaining ratio of 10. When congestion occurs, the scheduler allocates class-default traffic 10 times the unused bandwidth allocated in relation to other subinterfaces.
Router# show policy-map vlan10_policyPolicy Map vlan10_policyClass class-defaultAverage Rate Traffic Shapingcir 1000000 (bps)bandwidth remaining ratio 10service-policy child_policyTable 169 describes the fields shown in the display.
ATM Overhead Accounting: Example
The following sample output for the show policy-map command indicates that ATM overhead accounting is enabled for the class-default class. The BRAS-DSLAM encapsulation is dot1q and the subscriber encapsulation is snap-rbe for the AAL5 service.
Policy Map unit-testClass class-defaultAverage Rate Traffic Shapingcir 10% account dot1q aal5 snap-rbeTable 170 describes the significant fields shown in the display.
Tunnel Marking: Example
In this sample output of the show policy-map command, the character string "ip precedence tunnel 4" indicates that tunnel marking (either L2TPv3 or GRE) has been configured to set the IP precedence value to 4 in the header of a tunneled packet.
Note
Router# show policy-mapPolicy Map TUNNEL_MARKINGClass MATCH_FRDEset ip precedence tunnel 4Table 171 describes the fields shown in the display.
HQF: Example 1
The following sample output from the show policy-map command displays the configuration for a policy map called "test1":
Router# show policy-map test1Policy Map test1Class class-defaultAverage Rate Traffic Shapingcir 1536000 (bps)service-policy test2Table 172 describes the fields shown in the display.
HQF: Example 2
The following sample output from the show policy-map command displays the configuration for a policy map called "test2":
Router# show policy-map test2Policy Map test2Class RTpriority 20 (%)Class BHbandwidth 40 (%)queue-limit 128 packetsClass BLbandwidth 35 (%)packet-based wred, exponential weight 9dscp min-threshold max-threshold mark-probablity----------------------------------------------------------af21 (18) 100 400 1/10default (0) - - 1/10Table 173 describes the fields shown in the display.
Related Commands
show policy-map class
To display the configuration for the specified class of the specified policy map, use the show policy-map class command in user EXEC or privileged EXEC mode.
show policy-map policy-map class class-name
Syntax Description
policy-map
The name of a policy map that contains the class configuration to be displayed.
class-name
The name of the class whose configuration is to be displayed.
Command Modes
User EXEC (>)
Privileged EXEC (#)Command History
Usage Guidelines
You can use the show policy-map class command to display any single class configuration for any service policy map, whether or not the specified service policy map has been attached to an interface.
Examples
The following example displays configurations for the class called class7 that belongs to the policy map called po1:
Router# show policy-map po1 class class7Class class7 Bandwidth 937 (kbps) Max Thresh 64 (packets)Related Commands
show policy-map control-plane
To display the configuration and statistics for a traffic class or all traffic classes in the policy maps attached to the control plane for aggregate or distributed control plane services, use the show policy-map control-plane command in privileged EXEC mode.
Cisco 3660, 3800, 7200, 7400, and 7500 Series Routers
show policy-map control-plane [type policy-type] [all | slot slot-number] [host | transit | cef-exception] [input [class class-name] | output [class class-name]]
Cisco 7600 and ASR 1000 Series Routers
show policy-map control-plane [all] [input [class class-name] | output [class class-name]]
Syntax Description
Command Default
Information displays for all classes of the policy map of the control plane.
Command Modes
Privileged EXEC (#)
Command History
Usage Guidelines
The show policy-map control-plane command displays information for aggregate and distributed control-plane policing services that manage the number or rate of control-plane (CP) packets sent to the process level of the route processor.
Information for distributed control-plane service is displayed for a specified line card. Distributed CP services are performed on a line card's distributed switch engine and manage CP traffic sent from all interfaces on the line card to the route processor, where aggregate CP services (for CP packets received from all line cards on the router) are performed.
Examples
The following example shows that the policy map TEST is associated with the control plane. This policy map polices traffic that matches the class map TEST, while allowing all other traffic (that matches the class map called "class-default") to go through as is.
Router# show policy-map control-planeControl PlaneService-policy input:TESTClass-map:TEST (match-all)20 packets, 11280 bytes5 minute offered rate 0 bps, drop rate 0 bpsMatch:access-group 101police:8000 bps, 1500 limit, 1500 extended limitconformed 15 packets, 6210 bytes; action:transmitexceeded 5 packets, 5070 bytes; action:dropviolated 0 packets, 0 bytes; action:dropconformed 0 bps, exceed 0 bps, violate 0 bpsClass-map:class-default (match-any)105325 packets, 11415151 bytes5 minute offered rate 0 bps, drop rate 0 bpsMatch:anyTable 174 describes the significant fields shown in the display.
Related Commands
show policy-map interface
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.
Cisco 3660, 3845, 7200, 7400, 7500, and ASR 1000 Series Routers
show policy-map interface [type access-control] type number [vc [vpi/] vci] [dlci dlci] [input | output]
ATM Shared Port Adapters
show policy-map interface slot/subslot/port[.subinterface]
Cisco 7600 Series Routers
show policy-map interface [interface-type interface-number | null 0 | vlan vlan-id] [input | output]
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]]
Syntax Description
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.
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.
ATM Shared Port Adapter
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
Usage Guidelines
Cisco 3660, 3845, 7200, 7400, 7500, and 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 you attach a service policy to the interface or the PVC.
The counters displayed after you enter the show policy-map interface command 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 you enable Frame Relay Traffic Shaping (FRTS) on the interface.
The show policy-map interface command displays ECN marking information only if you enable ECN 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.
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
Weighted Fair Queueing (WFQ) on Serial Interface: Example
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 Table 175 for an explanation of the significant fields that commonly appear in the command output.
policy-map mypolicyclass voicepriority 128class goldbandwidth 100class silverbandwidth 80random-detectRouter# show policy-map interface serial3/1 outputSerial3/1Service-policy output: mypolicyClass-map: voice (match-all)0 packets, 0 bytes5 minute offered rate 0 bps, drop rate 0 bpsMatch: ip precedence 5Weighted Fair QueueingStrict PriorityOutput Queue: Conversation 264Bandwidth 128 (kbps) Burst 3200 (Bytes)(pkts matched/bytes matched) 0/0(total drops/bytes drops) 0/0Class-map: gold (match-all)0 packets, 0 bytes5 minute offered rate 0 bps, drop rate 0 bpsMatch: ip precedence 2Weighted Fair QueueingOutput Queue: Conversation 265Bandwidth 100 (kbps) Max Threshold 64 (packets)(pkts matched/bytes matched) 0/0(depth/total drops/no-buffer drops) 0/0/0Class-map: silver (match-all)0 packets, 0 bytes5 minute offered rate 0 bps, drop rate 0 bpsMatch: ip precedence 1Weighted Fair QueueingOutput Queue: Conversation 266Bandwidth 80 (kbps)(pkts matched/bytes matched) 0/0(depth/total drops/no-buffer drops) 0/0/0exponential weight: 9mean queue depth: 0class Transmitted Random drop Tail drop Minimum Maximum Markpkts/bytes pkts/bytes pkts/bytes thresh thresh prob0 0/0 0/0 0/0 20 40 1/101 0/0 0/0 0/0 22 40 1/102 0/0 0/0 0/0 24 40 1/103 0/0 0/0 0/0 26 40 1/104 0/0 0/0 0/0 28 40 1/105 0/0 0/0 0/0 30 40 1/106 0/0 0/0 0/0 32 40 1/107 0/0 0/0 0/0 34 40 1/10rsvp 0/0 0/0 0/0 36 40 1/10Class-map: class-default (match-any)0 packets, 0 bytes5 minute offered rate 0 bps, drop rate 0 bpsMatch: anyTraffic Shaping on Serial Interface: Example
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 Table 175 for an explanation of the significant fields that commonly appear in the command output.
Note
policy-map p1class c1shape average 320000Router# show policy-map interface serial3/2 outputSerial3/2Service-policy output: p1Class-map: c1 (match-all)0 packets, 0 bytes5 minute offered rate 0 bps, drop rate 0 bpsMatch: ip precedence 0Traffic ShapingTarget Byte Sustain Excess Interval Increment AdaptRate Limit bits/int bits/int (ms) (bytes) Active320000 2000 8000 8000 25 1000 -Queue Packets Bytes Packets Bytes ShapingDepth Delayed Delayed Active0 0 0 0 0 noClass-map: class-default (match-any)0 packets, 0 bytes5 minute offered rate 0 bps, drop rate 0 bpsMatch: anyTable 175 describes significant fields commonly shown in the displays. The fields in the table are grouped according to the relevant QoS feature.
Table 175 show policy-map interface Field Descriptions1
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
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
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.
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.
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
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.
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.
Note
Bytes Delayed
Total number of bytes delayed in the queue of the traffic shaper before being transmitted.
Note
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.
1 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.
Precedence-Based Aggregate WRED on ATM Shared Port Adapter: Example
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 Table 176 for an explanation of the significant fields that commonly appear in the command output.
Router(config)# policy-map prec-aggr-wredRouter(config-pmap)# class class-defaultRouter(config-pmap-c)# random-detect aggregateRouter(config-pmap-c)# random-detect precedence values 0 1 2 3 minimum thresh 10 maximum-thresh 100 mark-prob 10Router(config-pmap-c)# random-detect precedence values 4 5 minimum-thresh 40 maximum-thresh 400 mark-prob 10Router(config-pmap-c)# random-detect precedence values 6 minimum-thresh 60 maximum-thresh 600 mark-prob 10Router(config-pmap-c)# random-detect precedence values 7 minimum-thresh 70 maximum-thresh 700 mark-prob 10Router(config-pmap-c)# exitRouter(config-pmap)# exitRouter(config)# interface ATM4/1/0.10 point-to-pointRouter(config-if)# ip address 10.0.0.2 255.255.255.0Router(config-if)# pvc 10/110Router(config-if)# service-policy output prec-aggr-wred
Router# show policy-map interface atm4/1/0.10ATM4/1/0.10: VC 10/110 -Service-policy output: prec-aggr-wredClass-map: class-default (match-any)0 packets, 0 bytes5 minute offered rate 0 bps, drop rate 0 bpsMatch: anyExp-weight-constant: 9 (1/512)Mean queue depth: 0class Transmitted Random drop Tail drop Minimum Maximum Markpkts/bytes pkts/bytes pkts/bytes thresh thresh prob0 1 2 3 0/0 0/0 0/0 10 100 1/104 5 0/0 0/0 0/0 40 400 1/106 0/0 0/0 0/0 60 600 1/107 0/0 0/0 0/0 70 700 1/10DSCP-Based Aggregate WRED on ATM Shared Port Adapter: Example
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 Table 176 for an explanation of the significant fields that commonly appear in the command output.
Router(config)# policy-map dscp-aggr-wredRouter(config-pmap)# class class-defaultRouter(config-pmap-c)# random-detect dscp-based aggregate minimum-thresh 1 maximum-thresh 10 mark-prob 10Router(config-pmap-c)# random-detect dscp values 0 1 2 3 4 5 6 7 minimum-thresh 10 maximum-thresh 20 mark-prob 10Router(config-pmap-c)# random-detect dscp values 8 9 10 11 minimum-thresh 10 maximum-thresh 40 mark-prob 10Router(config-pmap-c)# exitRouter(config-pmap)# exitRouter(config)# interface ATM4/1/0.11 point-to-pointRouter(config-subif)# ip address 10.0.0.2 255.255.255.0Router(config-subif)# pvc 11/101Router(config-subif)# service-policy output dscp-aggr-wredRouter# show policy-map interface atm4/1/0.11ATM4/1/0.11: VC 11/101 -Service-policy output: dscp-aggr-wredClass-map: class-default (match-any)0 packets, 0 bytes5 minute offered rate 0 bps, drop rate 0 bpsMatch: anyExp-weight-constant: 0 (1/1)Mean queue depth: 0class Transmitted Random drop Tail drop Minimum Maximum Markpkts/bytes pkts/bytes pkts/bytes thresh thresh probdefault 0/0 0/0 0/0 1 10 1/100 1 2 34 5 6 7 0/0 0/0 0/0 10 20 1/108 9 10 11 0/0 0/0 0/0 10 40 1/10Table 176 describes the significant fields shown in the display when aggregate WRED is configured for an ATM shared port adapter.
Frame Relay Voice-Adaptive Traffic-Shaping: Example
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
Router# show policy interface Serial3/1.1Serial3/1.1:DLCI 201 -Service-policy output:MQC-SHAPE-LLQ1Class-map:class-default (match-any)1434 packets, 148751 bytes30 second offered rate 14000 bps, drop rate 0 bpsMatch:anyTraffic ShapingTarget/Average Byte Sustain Excess Interval IncrementRate Limit bits/int bits/int (ms) (bytes)63000/63000 1890 7560 7560 120 945Adapt Queue Packets Bytes Packets Bytes ShapingActive Depth Delayed Delayed ActiveBECN 0 1434 162991 26 2704 yesVoice Adaptive Shaping active, time left 29 secsTable 177 describes the significant fields shown in the display. Significant fields that are not described in Table 177 are described in Table 175, "show policy-map interface Field Descriptions."
Two-Rate Traffic Policing: Example
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/0Serial3/0Service-policy output: policy1Class-map: police (match all)148803 packets, 36605538 bytes30 second offered rate 1249000 bps, drop rate 249000 bpsMatch: access-group 101police:cir 500000 bps, conform-burst 10000, pir 1000000, peak-burst 100000conformed 59538 packets, 14646348 bytes; action: transmitexceeded 59538 packets, 14646348 bytes; action: set-prec-transmit 2violated 29731 packets, 7313826 bytes; action: dropconformed 499000 bps, exceed 500000 bps violate 249000 bpsClass-map: class-default (match-any)19 packets, 1990 bytes30 seconds offered rate 0 bps, drop rate 0 bpsMatch: anyThe 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.
Table 178 describes the significant fields shown in the display.
Multiple Traffic Policing Actions: Example
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 policeclass class-defaultpolice cir 1000000 pir 2000000conform-action transmitexceed-action set-prec-transmit 4exceed-action set-frde-transmitviolate-action set-prec-transmit 2violate-action set-frde-transmitRouter# show policy-map interface serial3/2Serial3/2: DLCI 100 -Service-policy output: policeClass-map: class-default (match-any)172984 packets, 42553700 bytes5 minute offered rate 960000 bps, drop rate 277000 bpsMatch: anypolice:cir 1000000 bps, bc 31250 bytes, pir 2000000 bps, be 31250 bytesconformed 59679 packets, 14680670 bytes; actions:transmitexceeded 59549 packets, 14649054 bytes; actions:set-prec-transmit 4set-frde-transmitviolated 53758 packets, 13224468 bytes; actions:set-prec-transmit 2set-frde-transmitconformed 340000 bps, exceed 341000 bps, violate 314000 bpsThe sample output from show policy-map interface command shows the following:
•
•
•
Note
Table 179 describes the significant fields shown in the display.
Explicit Congestion Notification: Example
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/1Serial4/1Service-policy output:policy_ecnClass-map:prec1 (match-all)1000 packets, 125000 bytes30 second offered rate 14000 bps, drop rate 5000 bpsMatch:ip precedence 1Weighted Fair QueueingOutput Queue:Conversation 42Bandwidth 20 (%)Bandwidth 100 (kbps)(pkts matched/bytes matched) 989/123625(depth/total drops/no-buffer drops) 0/455/0exponential weight:9explicit congestion notificationmean queue depth:0class Transmitted Random drop Tail drop Minimum Maximum Markpkts/bytes pkts/bytes pkts/bytes threshold threshold probability0 0/0 0/0 0/0 20 40 1/101 545/68125 0/0 0/0 22 40 1/102 0/0 0/0 0/0 24 40 1/103 0/0 0/0 0/0 26 40 1/104 0/0 0/0 0/0 28 40 1/105 0/0 0/0 0/0 30 40 1/106 0/0 0/0 0/0 32 40 1/107 0/0 0/0 0/0 34 40 1/10rsvp 0/0 0/0 0/0 36 40 1/10class ECN Markpkts/bytes0 0/01 43/53752 0/03 0/04 0/05 0/06 0/07 0/0rsvp 0/0Table 180 describes the significant fields shown in the display.
Class-Based RTP and TCP Header Compression: Example
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/1Serial4/1Service-policy output:p1Class-map:class-default (match-any)1005 packets, 64320 bytes30 second offered rate 16000 bps, drop rate 0 bpsMatch:anycompress:header ip rtpUDP/RTP Compression:Sent:1000 total, 999 compressed,41957 bytes saved, 17983 bytes sent3.33 efficiency improvement factor99% hit ratio, five minute miss rate 0 misses/sec, 0 maxrate 5000 bpsTable 181 describes the significant fields shown in the display.
Table 181 show policy-map interface Field Descriptions—Configured for Class-Based RTP and TCP Header Compression1
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
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
maxThe 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.
1 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.
Modular QoS CLI (MQC) Unconditional Packet Discard: Example
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/0Serial2/0Service-policy output: policy1Class-map: c1 (match-all)10184 packets, 1056436 bytes5 minute offered rate 32000 bps, drop rate 32000 bpsMatch: ip precedence 0dropTable 182 describes the significant fields shown in the display.
Table 182 show policy-map interface Field Descriptions—Configured for MQC Unconditional Packet Discard1
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
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
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.
1 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.
Percentage-Based Policing and Shaping: Example
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/1Serial3/1Service-policy output: mypolicyClass-map: gold (match-any)0 packets, 0 bytes5 minute offered rate 0 bps, drop rate 0 bpsMatch: anypolice:cir 20 % bc 10 mscir 2000000 bps, bc 2500 bytespir 40 % be 20 mspir 4000000 bps, be 10000 bytesconformed 0 packets, 0 bytes; actions: transmit exceeded 0 packets, 0 bytes; actions: dropviolated 0 packets, 0 bytes; actions:dropconformed 0 bps, exceed 0 bps, violate 0 bpsTable 183 describes the significant fields shown in the display.
Table 183 show policy-map interface Field Descriptions—Configured for Percentage-Based Policing and Shaping1
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
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.
1 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.
Traffic Shaping: Example
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
Router# show policy-map interface Serial3/2Serial3/2Service-policy output: p1Class-map: c1 (match-all)0 packets, 0 bytes5 minute offered rate 0 bps, drop rate 0 bpsMatch: anyTraffic ShapingTarget/Average Byte Sustain Excess Interval Increment AdaptRate 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 ShapingDepth Delayed Delayed Active0 0 0 0 0 noTable 184 describes the significant fields shown in the display.
Table 184 show policy-map interface Field Descriptions—Configured for Percentage-Based Policing and Shaping (with Traffic Shaping Enabled)1
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
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 Cisco IOS 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
Bytes Delayed
Total number of bytes delayed in the queue of the traffic shaper before being transmitted.
Note
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.
1 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.
Packet Classification Based on Layer 3 Packet Length: Example
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/1Ethernet4/1Service-policy input: mypolicyClass-map: class1 (match-all)500 packets, 125000 bytes5 minute offered rate 4000 bps, drop rate 0 bpsMatch: packet length min 100 max 300QoS Setqos-group 20Packets marked 500Table 185 describes the significant fields shown in the display.
Table 185 show policy-map interface Field Descriptions—Configured for Packet Classification Based on Layer 3 Packet Length1
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
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.
1 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.
Enhanced Packet Marking: Example
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 interfaceFastEthernet1/0.1Service-policy input: policy1Class-map: class-default (match-any)0 packets, 0 bytes5 minute offered rate 0 bps, drop rate 0 bpsMatch: anyQoS Setprecedence cos table table-map1Packets marked 0Table 186 describes the fields shown in the display.
Table 186 show policy-map interface Field Descriptions—Configured for Enhanced Packet Marking1
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 Cisco IOS 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.
1 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.
Traffic Policing: Example
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/0Serial2/0Service-policy output: policy1 (1050)Class-map: class1 (match-all) (1051/1)0 packets, 0 bytes5 minute offered rate 0 bps, drop rate 0 bpsMatch: ip precedence 0 (1052)police:cir 20 % bc 300 mscir 409500 bps, bc 15360 bytespir 40 % be 400 mspir 819000 bps, be 40960 bytesconformed 0 packets, 0 bytes; actions:transmitexceeded 0 packets, 0 bytes; actions:dropviolated 0 packets, 0 bytes; actions:dropconformed 0 bps, exceed 0 bps, violate 0 bpsClass-map: class-default (match-any) (1054/0)0 packets, 0 bytes5 minute offered rate 0 bps, drop rate 0 bpsMatch: any (1055)0 packets, 0 bytes5 minute rate 0 bpsIn 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.
Formula for Calculating the CIR: Example
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/0Serial2/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/255The following values are used for calculating the CIR:
20 % * 2048 kbps = 409600 bps
Formula for Calculating the PIR: Example
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/0Serial2/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/255The following values are used for calculating the PIR:
40 % * 2048 kbps = 819200 bps
Note
Formula for Calculating the Committed Burst (bc): Example
When calculating the bc, the following formula is used:
•
The following values are used for calculating the bc:
300 ms * 409600 bps = 15360 bytes
Formula for Calculating the Excess Burst (be): Example
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
Table 187 describes the significant fields shown in the display.
Bandwidth Estimation: Example
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/1FastEthernet0/1Service-policy output: my-policyClass-map: icmp (match-all)199 packets, 22686 bytes30 second offered rate 0 bps, drop rate 0 bpsMatch: access-group 101Bandwidth 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/secClass-map: class-default (match-any)112 packets, 14227 bytes30 second offered rate 0 bps, drop rate 0 bpsMatch: anyBandwidth Estimation:Quality-of-Service targets:<none specified, falling back to drop no more than one packet in 500Corvil Bandwidth: 1 kbits/secShaping with HQF Enabled: Example
The following sample output from the show policy-map interface 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
Router# show policy-map interface serial4/3Serial4/3Service-policy output: shapeClass-map: class-default (match-any)2203 packets, 404709 bytes30 second offered rate 74000 bps, drop rate 14000 bpsMatch: anyQueueingqueue limit 64 packets(queue depth/total drops/no-buffer drops) 64/354/0(pkts output/bytes output) 1836/337280shape (average) cir 128000, bc 1000, be 1000target shape rate 128000lower bound cir 0, adapt to fecn 0Service-policy : LLQqueue stats for all priority classes:queue limit 64 packets(queue depth/total drops/no-buffer drops) 0/0/0(pkts output/bytes output) 0/0Class-map: c1 (match-all)0 packets, 0 bytes30 second offered rate 0 bps, drop rate 0 bpsMatch: ip precedence 1Priority: 32 kbps, burst bytes 1500, b/w exceed drops: 0Class-map: class-default (match-any)2190 packets, 404540 bytes30 second offered rate 74000 bps, drop rate 14000 bpsMatch: anyqueue limit 64 packets(queue depth/total drops/no-buffer drops) 63/417/0(pkts output/bytes output) 2094/386300Packets Matched on the Basis of VLAN ID Number: Example
Note
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-mapClass Map match-all class1 (id 3)Match vlan 150Class1 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 interfaceFastEthernet0/0.1! Policy-map name.Service-policy input: policy1! Class configured in the policy map.Class-map: class1 (match-all)0 packets, 0 bytes5 minute offered rate 0 bps, drop rate 0 bps! VLAN ID 150 is the match criterion for the class.Match: vlan 150police:cir 8000000 bps, bc 512000000 bytesconformed 0 packets, 0 bytes; actions:transmitexceeded 0 packets, 0 bytes; actions:dropconformed 0 bps, exceed 0 bpsClass-map: class-default (match-any)10 packets, 1140 bytes5 minute offered rate 0 bps, drop rate 0 bpsMatch: any10 packets, 1140 bytes5 minute rate 0 bpsTable 188 describes the significant fields shown in the display.
Table 188 show policy-map interface Field Descriptions—Packets Matched on the Basis of VLAN ID Number1
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.
1 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.
Cisco 7600 Series Routers: Example
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 interfaceFastEthernet5/36service-policy input: max-pol-ipp5class-map: ipp5 (match-all)0 packets, 0 bytes5 minute rate 0 bpsmatch: ip precedence 5class ipp5police 2000000000 2000000 conform-action set-prec-transmit 6 exceed-action ppoliced-dscp-transmitThe 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 inputFastEthernet5/36service-policy input: max-pol-ipp5class-map: ipp5 (match-all)0 packets, 0 bytes5 minute rate 0 bpsmatch: ip precedence 5class ipp5police 2000000000 2000000 conform-action set-prec-transmit 6 exceed-action ppoliced-dscp-transmitTable 189 describes the significant fields shown in the display.
Multiple Priority Queues on Serial Interface: Example
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 interfaceSerial2/1/0Service-policy output: P1Queue 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 bpsMatch: ip precedence 2Priority: 0 kbps, burst bytes 1500, b/w exceed drops: 0Priority Level 4:0 packets, 0 bytesBandwidth-Remaining Ratios: Example
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.10Service-policy output: vlan10_policyClass-map: class-default (match-any)0 packets, 0 bytes30 second offered rate 0 bps, drop rate 0 bpsMatch: any0 packets, 0 bytes30 second rate 0 bpsQueueingqueue limit 250 packets(queue depth/total drops/no-buffer drops) 0/0/0(pkts output/bytes output) 0/0shape (average) cir 1000000, bc 4000, be 4000target shape rate 1000000bandwidth remaining ratio 10Service-policy : child_policyClass-map: precedence_0 (match-all)0 packets, 0 bytes30 second offered rate 0 bps, drop rate 0 bpsMatch: ip precedence 0Queueingqueue limit 62 packets(queue depth/total drops/no-buffer drops) 0/0/0(pkts output/bytes output) 0/0shape (average) cir 500000, bc 2000, be 2000target shape rate 500000bandwidth remaining ratio 20Class-map: precedence_1 (match-all)0 packets, 0 bytes30 second offered rate 0 bps, drop rate 0 bpsMatch: ip precedence 1Queueingqueue limit 62 packets(queue depth/total drops/no-buffer drops) 0/0/0(pkts output/bytes output) 0/0shape (average) cir 500000, bc 2000, be 2000target shape rate 500000bandwidth remaining ratio 40Class-map: precedence_2 (match-all)0 packets, 0 bytes30 second offered rate 0 bps, drop rate 0 bpsMatch: ip precedence 2Queueingqueue limit 62 packets(queue depth/total drops/no-buffer drops) 0/0/0(pkts output/bytes output) 0/0shape (average) cir 500000, bc 2000, be 2000target shape rate 500000bandwidth remaining ratio 60Class-map: class-default (match-any)0 packets, 0 bytes30 second offered rate 0 bps, drop rate 0 bpsMatch: any0 packets, 0 bytes30 second rate 0 bpsqueue limit 62 packets(queue depth/total drops/no-buffer drops) 0/0/0(pkts output/bytes output) 0/0Table 190 describes the significant fields shown in the display.
Tunnel Marking: Example
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 interfaceSerial0Service-policy input: tunnelClass-map: frde (match-all)0 packets, 0 bytes30 second offered rate 0 bps, drop rate 0 bpsMatch: fr-deQoS Setip dscp tunnel 3Packets marked 0Class-map: class-default (match-any)13736 packets, 1714682 bytes30 second offered rate 0 bps, drop rate 0 bpsMatch: any13736 packets, 1714682 bytes30 second rate 0 bpsTable 191 describes the significant fields shown in the display.
Traffic Shaping Overhead Accounting for ATM: Example
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 interfaceService-policy output:unit-testClass-map: class-default (match-any)100 packets, 1000 bytes30 second offered rate 800 bps, drop rate 0 bpsMatch: anyshape (average) cir 154400, bc 7720, be 7720target shape rate 154400overhead accounting: enabledbandwidth 30% (463 kbps)overhead accounting: disabledqueue limit 64 packets(queue depth/total drops/no-buffer drops) 0/0/0(packets output/bytes output) 100/1000Table 192 describes the significant fields shown in the display.
HQF: Example
The following output from the show policy-map interface command displays the configuration for Fast Ethernet interface 0/0.
Note
Router# show policy-map interface f0/0FastEthernet0/0Service-policy output: test1Class-map: class-default (match-any)129 packets, 12562 bytes30 second offered rate 0 bps, drop rate 0 bpsMatch: anyQueueingqueue limit 64 packets(queue depth/total drops/no-buffer drops) 0/0/0(pkts output/bytes output) 129/12562shape (average) cir 1536000, bc 6144, be 6144target shape rate 1536000Service-policy : test2queue stats for all priority classes:queue limit 64 packets(queue depth/total drops/no-buffer drops) 0/0/0(pkts output/bytes output) 0/0Class-map: RT (match-all)0 packets, 0 bytes30 second offered rate 0 bps, drop rate 0 bpsMatch: ip dscp ef (46)Priority: 20% (307 kbps), burst bytes 7650, b/w exceed drops: 0Class-map: BH (match-all)0 packets, 0 bytes30 second offered rate 0 bps, drop rate 0 bpsMatch: ip dscp af41 (34)Queueingqueue limit 128 packets(queue depth/total drops/no-buffer drops) 0/0/0(pkts output/bytes output) 0/0bandwidth 40% (614 kbps)Class-map: BL (match-all)0 packets, 0 bytes30 second offered rate 0 bps, drop rate 0 bpsMatch: ip dscp af21 (18)Queueingqueue limit 64 packets(queue depth/total drops/no-buffer drops) 0/0/0(pkts output/bytes output) 0/0bandwidth 35% (537 kbps)Exp-weight-constant: 9 (1/512)Mean queue depth: 0 packetsdscp Transmitted Random drop Tail drop Minimum Maximum Markpkts/bytes pkts/bytes pkts/bytes thresh thresh probaf21 0/0 0/0 0/0 100 400 1/10Class-map: class-default (match-any)129 packets, 12562 bytes30 second offered rate 0 bps, drop rate 0 bpsMatch: anyqueue limit 64 packets(queue depth/total drops/no-buffer drops) 0/0/0(pkts output/bytes output) 129/12562Table 193 describes the significant fields shown in the display.
Related Commands
show policy-map interface brief
To display information about only the active policy maps attached to an interface, use the show policy-map interface brief command in privileged EXEC mode.
show policy-map interface [input | output] brief [policy-map-name] [vrf [vrf-id]] [timestamp]
Syntax Description
Command Default
If no optional keywords or arguments are specified, all policy maps (even those that are not active) are displayed.
Command Modes
Privileged EXEC (#)
Command History
Usage Guidelines
The show policy-map interface brief command displays the name of the active policy maps and the interfaces to which those policy maps are attached. An active policy map is one that is attached to an interface.
The optional keywords and arguments allow you to tailor the information displayed about VPNs, time stamps, and user IDs.
If you do not specify any optional keywords or arguments, all policy maps (even those that are not active) are displayed.
VPN Information Reported
The show policy-map interface brief command can be used for VRF interfaces in applications that use VPNs. To specify VRF interfaces, use the vrf keyword with the vrf-id argument.
Time-stamp and User ID Information Reported
If the optional timestamp keyword is used with the show policy-map interface brief command, the time and date when a policy map was attached to an interface appear in the display. In addition to the time and date information, the name (that is, the user ID) of the person who attached the policy map to the interface will be displayed.
Note
Method for Obtaining User Information
The user information included in the display is obtained from the information that you enter when you log in to the router. For example, if you are using the SSH Secure Shell utility to log in to a router, you would typically enter your username and password. However, it is not always possible to obtain the user information. Instances where user information cannot be obtained include the following:
•
•
•
If the user information cannot be obtained, the words "by unknown" will be displayed.
Hierarchical Policy Map Information
For a hierarchical policy map structure, only the information about the parent policy maps is displayed. Information about child policy maps is not displayed.
ATM PVCs
For ATM permanent virtual circuits (PVCs), policy maps do not remain associated with the interface if the ATM PVC is not working properly (that is, the ATM PVC is "down"). Therefore, if an ATM PVC is down, and a policy map is attached to an interface, the show policy-map interface brief command does not include information about the policy maps in the command output.
Examples
The information that is displayed by the show policy-map interface brief command varies according to the optional keywords and arguments that you specify.
The following sections list the significant keyword and argument combinations used with the command and describe the corresponding information displayed.
show policy-map interface brief Command Example
The show policy-map interface brief command displays all the attached policy maps (both input policy maps and output policy maps) along with the information about the interfaces to which the policy maps are attached. The input policy maps are displayed first, followed by the output policy maps.
Service-policy input: policyname1interface s2/0/1interface s6/0/0Service-policy output: policyname1interface s2/0/1 interface s6/0/0show policy-map interface brief timestamp Command Example
The show policy-map interface brief timestamp command displays all the attached policy maps (both input policy maps and output policy maps) along with the information about the interfaces to which the policy maps are attached. The input policy maps are displayed first, followed by the output policy maps.
The timestamp keyword displays the time and date when the policy map was attached to the specific interface, along with the user ID of the person who attached the policy map to the interface.
Service-policy input: parentpolicy1Service-policy input: childpolicy1interface s2/0/1 - applied 20:43:04 on 25/12/01 by user1interface s6/0/1 - applied 19:43:04 on 25/12/01 by user1Service-policy output: policyname2interface s2/0/2 - applied 21:47:04 on 24/12/01 by user1interface s6/0/1 - applied 19:43:04 on 25/12/01 by user1show policy-map interface brief policy-map-name Command Example
The show policy-map interface brief policy-map-name command displays the policy map attached as either an input policy map or an output policy map, along with the information about the interface to which the policy map is attached. Only the policy map specified by the policy-map-name argument is displayed.
For example, the display for the show policy-map interface brief policyname1 command is as follows:
Service-policy input: policyname1interface s2/0/1interface s6/0/0Service-policy output: policyname1interface s1/0/2interface s3/0/0show policy-map interface brief policy-map-name timestamp Command Example
The show policy-map interface brief policy-map-name timestamp command displays the policy map attached as either an input policy map or an output policy map, along with the information about the interface to which it is attached. Only the policy map specified by the policy-map-name argument is displayed.
The timestamp keyword displays the time and date when the policy map was attached to the specific interface, along with the user ID of the person who attached the policy map to the interface.
For example, the display for the show policy-map interface brief policyname2 timestamp command is as follows:
Service-policy input: policyname2interface s2/0/2 - applied 21:47:04 on 24/12/01 by user1interface s6/0/1 - applied 19:43:04 on 25/12/01 by user1Service-policy output: policyname2interface s4/0/2 - applied 12:47:04 on 24/12/01 by user1interface s7/0/1 - applied 14:43:04 on 25/12/01 by user1show policy-map interface output brief Command Example
The show policy-map interface output brief command displays the attached output policy maps, along with the information about the interfaces to which they are attached.
Service-policy output: policyname1show policy-map interface output brief timestamp Command Example
The show policy-map interface output brief timestamp command displays the attached output policy maps, along with the information about the interfaces to which they are attached.
The timestamp keyword displays the time and date when the policy map was attached to the specific interface, along with the user ID of the person who attached the policy map to the interface.
Service-policy output: policyname2interface s2/0/2 - applied 21:47:04 on 24/12/01 by user1interface s6/0/1 - applied 19:43:04 on 25/12/01 by user1show policy-map interface input brief Command Example
The show policy-map interface input brief command displays the attached input policy maps, along with the information about the interfaces to which they are attached.
Service-policy input: policyname2interface s2/0/2interface s6/0/1show policy-map interface input brief timestamp Command Example
The show policy-map interface input brief timestamp command displays the attached input policy maps, along with the information about the interfaces to which they are attached.
The timestamp keyword displays the time and date when the policy map was attached to the specific interface, along with the user ID of the person who attached the policy map to the interface.
Service-policy input: policyname2interface s2/0/2 - applied 21:47:04 on 24/12/01 by user1interface s6/0/1 - applied 19:43:04 on 25/12/01 by user1show policy-map interface output brief policy-map-name Command Example
The show policy-map interface output brief policy-map-name command displays the attached output policy map, along with the information about the interface to which it is attached. Only the policy map specified by the policy-map-name argument is displayed.
For example, the display for the show policy-map interface output brief policyname1 command is as follows:
Service-policy output: policyname1interface s2/0/1interface s6/0/0show policy-map interface output brief policy-map-name timestamp Command Example
The show policy-map interface output brief policy-map-name timestamp command displays the attached output policy map, along with the information about the interface to which it is attached. Only the policy map specified by the policy-map-name argument is displayed.
The timestamp keyword displays the time and date when the policy map was attached to the specific interface, along with the user ID of the person who attached the policy map to the interface.
For example, the display for the show policy-map interface output brief policyname2 timestamp command is as follows:
Service-policy output: policyname2interface s2/0/2 - applied 21:47:04 on 24/12/01 by user1interface s6/0/1 - applied 19:43:04 on 25/12/01 by user1show policy-map interface input brief policy-map-name Command Example
The show policy-map interface input brief policy-map-name command displays the attached input policy map, along with the information about the interface to which it is attached. Only the policy map specified by the policy-map-name argument is displayed.
For example, the display for the show policy-map interface input brief policyname1 command is as follows:
Service-policy input: policyname1interface s2/0/1interface s6/0/0show policy-map interface input brief policy-map-name timestamp Command Example
The show policy-map interface input brief policy-map-name timestamp command displays the attached input policy map, along with the information about the interface to which it is attached. Only the policy map specified by the policy-map-name argument is displayed.
The timestamp keyword displays the time and date when the policy map was attached to the specific interface, along with the user ID of the person who attached the policy map to the interface.
For example, the display for the show policy-map interface input brief policyname2 timestamp command is as follows:
Service-policy input: policyname2interface s2/0/2 - applied 21:47:04 on 24/12/01 by user1interface s6/0/1 - applied 19:43:04 on 25/12/01 by user1show policy-map interface brief vrf Command Example
The show policy-map interface brief vrf command displays all the policy maps (both input policy maps and output policy maps), along with information about the interfaces and the VRFs to which the policy maps are attached.
Service-policy input: policyname1VRFA interface s2/0/1VRFB interface s6/0/0Service-policy output: policyname2VRFC interface s2/0/2VRFB interface s6/0/1show policy-map interface brief vrf timestamp Command Example
The show policy-map interface brief vrf timestamp command displays all the policy maps (both input policy maps and output policy maps), along with information about the interfaces and the VRFs to which the policy maps are attached.
The timestamp keyword displays the time and date when the policy map was attached to the specific interface, along with the user ID of the person who attached the policy map to the interface.
Service-policy input: policyname1VRFA interface s2/0/1 - applied 21:47:04 on 23/12/01 by user1VRFB interface s6/0/0 - applied 21:47:04 on 23/12/01 by user1Service-policy output: policyname2VRFC interface s2/0/3 - applied 20:47:04 on 23/12/01 by user1VRFD interface s6/0/2 - applied 20:49:04 on 21/12/01 by user1In some network configurations, the policy map may be attached to the interface initially, and then at a later time, the interface can be configured to act as a VRF interface. In this kind of network configuration, the time-stamp information displays the time when the policy map was attached to the interface. The display does not include the time when the interface was configured to act as a VRF interface. Displaying only the time when the policy map is attached to the interface also applies to the scenarios that are described in the following paragraph for other network configurations.
In other network configurations, a VRF may be attached to multiple interfaces as described in the following scenarios:
•
Service-policy input: policyname1VRF1 interface s2/0/1 - applied 21:47:37 on 23/12/01 by user1interface atm0/0 - applied 11:37:57 on 21/11/01 by user1•
show policy-map interface brief policy-map-name vrf timestamp Command Example
The show policy-map interface brief policy-map-name vrf timestamp command displays the policy maps attached as either an input policy map or an output policy map, along with information about the interface and VRF to which the policy map is attached. Only the policy map specified by the policy-map-name argument is displayed.
The timestamp keyword displays the time and date when the policy map was attached to the specific interface, along with the user ID of the person who attached the policy map to the interface.
For example, the display for the show policy-map interface brief policyname1 vrf timestamp command is as follows:
Service-policy input: policyname1VRF1 interface s2/0/1 - applied 21:47:04 on 23/12/01 by user1Service-policy output: policyname1VRF2 interface s6/0/1 - applied 21:47:04 on 23/12/01 by user1show policy-map interface brief policy-map-name vrf vrf-id timestamp Command Example
The show policy-map interface brief policy-map-name vrf vrf-id timestamp command displays all the policy maps (both the input policy maps and the output policy maps), along with information about the interface and VRF to which the policy maps are attached. Only the policy map and VRF specified by the policy-map-name argument and the vrf-id argument are displayed.
The timestamp keyword displays the time and date when the policy map was attached to the specific interface, along with the user ID of the person who attached the policy map to the interface.
For example, the display for show policy-map interface brief policyname1 vrf VRFA timestamp command is as follows:
Service-policy input: policyname1VRFA interface s2/0/1 - applied 21:47:04 on 23/12/01 by user1Service-policy output: policyname1VRFA interface s6/0/1 - applied 21:47:04 on 23/12/01 by user1show policy-map interface output brief vrf Command Example
The show policy-map interface output brief vrf command displays the attached output policy maps, along with information about the interface and VRF to which the policy maps are attached.
Service-policy output: policyname2VRFC interface s2/0/2VRFA interface s6/0/1show policy-map interface output brief vrf timestamp Command Example
The show policy-map interface output brief vrf timestamp command displays the attached output policy maps, along with information about the interface and VRF to which the policy maps are attached.
The timestamp keyword displays the time and date when the policy map was attached to the specific interface, along with the user ID of the person who attached the policy map to the interface.
Service-policy output: policyname2VRFC interface s2/0/2 - applied 21:47:04 on 23/12/01 by user1VRFA interface s6/0/1 - applied 21:47:04 on 23/12/01 by user1show policy-map interface input brief vrf Command Example
The show policy-map interface input brief vrf command displays the attached input policy maps, along with information about the interface and VRF to which the policy maps are attached.
Service-policy input: policyname1VRFA interface s2/0/1VRFB interface s6/0/0Service-policy input: policyname2VRFC interface s2/0/2VRFB interface s6/0/1show policy-map interface input brief vrf timestamp Command Example
The show policy-map interface input brief vrf timestamp command displays the attached input policy maps, along with information about the interface and VRF to which the policy maps are attached.
The timestamp keyword displays the time and date when the policy map was attached to the specific interface, along with the user ID of the person who attached the policy map to the interface.
Service-policy input: policyname1VRFA interface s2/0/1 - applied 21:47:04 on 23/12/01 by user1VRFB interface s6/0/0 - applied 21:47:04 on 23/12/01 by user1Service-policy input: policyname2VRFC interface s2/0/3 - applied 20:47:04 on 23/12/01 by user1VRFD interface s6/0/2 - applied 20:49:04 on 21/12/01 by user1show policy-map interface input brief vrf vrf-id Command Example
The show policy-map interface input brief vrf vrf-id command displays the attached input policy maps, along with information about the interface and VRF to which the policy maps are attached. Only the policy maps attached to the VRF specified by the vrf-id argument are displayed.
For example, the display for the show policy-map interface input brief vrf VRFA command is as follows:
Service-policy input: policyname1VRFA interface s2/0/1Service-policy input: policyname2VRFA interface s6/0/1show policy-map interface output brief vrf vrf-id Command Example
The show policy-map interface output brief vrf vrf-id command displays the attached output policy maps, along with information about the interface and VRF to which the policy maps are attached. Only the policy maps attached to the VRF specified by the vrf-id argument are displayed.
For example, the display for the show policy-map interface output brief vrf VRFB command is as follows:
Service-policy output: policyname1VRFB interface s2/0/1Service-policy output: policyname2VRFB interface s6/0/1show policy-map interface input brief vrf vrf-id timestamp Command Example
The show policy-map interface input brief vrf vrf-id timestamp command displays the attached input policy maps, along with information about the interface and VRF to which the policy maps are attached. Only the policy maps attached to the VRF specified by the vrf-id argument are displayed.
The timestamp keyword displays the time and date when the policy map was attached to the specific interface, along with the user ID of the person who attached the policy map to the interface.
For example, the display for the show policy-map interface input brief vrf VRFA timestamp command is as follows:
Service-policy input: policyname1VRFA interface s2/0/1 - applied 21:47:04 on 23/12/01 by user1Service-policy input: policyname2VRFA interface s6/0/1 - applied 21:47:04 on 23/12/01 by user1show policy-map interface output brief vrf vrf-id timestamp Command Example
The show policy-map interface output brief vrf vrf-id timestamp command displays the attached output policy maps, along with information about the interface and VRF to which the policy maps are attached. Only the policy maps attached to the VRF specified by the vrf-id argument are displayed.
The timestamp keyword displays the time and date when the policy map was attached to the specific interface, along with the user ID of the person who attached the policy map to the interface.
For example, the display for the show policy-map interface output brief vrf VRFB timestamp command is as follows:
Service-policy output: policyname1VRFB interface s2/0/1 - applied 21:47:04 on 23/12/01 by user1Service-policy output: policyname2VRFB interface s6/0/1 - applied 21:47:04 on 23/12/01 by user1Table 194 describes the significant fields shown in the various displays.
Related Commands
show policy-map interface service instance
To display the policy-map information for a given service instance under a port channel, use the show policy-map interface service instance command in user EXEC or privileged EXEC mode.
show policy-map interface x service instance y
Syntax Description
Command Modes
User EXEC
Privileged EXECCommand History
Examples
The following example shows the policy-map output for a hierarchical policy on a given service instance 1 under port channel 1:
Router# show policy-map interface port-channel 1 service instance 1Port-channel1: EFP 1Service-policy output: hqos-pc-brrClass-map: class-default (match-any)0 packets, 0 bytes5 minute offered rate 0 bps, drop rate 0 bpsMatch: anyQueueingqueue limit 5000 packets(queue depth/total drops/no-buffer drops) 0/0/0(pkts output/bytes output) 0/0shape (average) cir 20000000, bc 80000, be 80000target shape rate 20000000bandwidth remaining ratio 2Service-policy : flat-pc-brrClass-map: cos5 (match-all)0 packets, 0 bytes5 minute offered rate 0 bps, drop rate 0 bpsMatch: cos 5Queueingqueue limit 2500 packets(queue depth/total drops/no-buffer drops) 0/0/0(pkts output/bytes output) 0/0shape (average) cir 10000000, bc 40000, be 40000target shape rate 10000000Class-map: class-default (match-any)0 packets, 0 bytes5 minute offered rate 0 bps, drop rate 0 bpsMatch: anyQueueingqueue limit 2500 packets(queue depth/total drops/no-buffer drops) 0/0/0(pkts output/bytes output) 0/0shape (average) cir 10000000, bc 40000, be 40000target shape rate 10000000Table 195 describes the significant fields shown in the display.
Table 195 show policy-map interface service instance Field Descriptions1
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
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 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.
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.
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
