Examples

The following is sample output from the show metadata application table command:

Device# show metadata application table

ID     Name                  Vendor                Vendor id           
--------------------------------------------------------------------------------
113    telepresence-media    -                     -                   
114    telepresence-contr$   -                     -                   
478    telepresence-data     -                     -                   
414    webex-meeting         -                     -                   
56     citrix                -                     -                   
81     cisco-phone           -                     -                   
472    vmware-view           -                     -                   
473    wyze-zero-client      -                     -                   
61     rtp                   -                     -                   
64     h323                  -                     -                   
5060   sip                   -                     -                   
554    rtsp                  -                     -                   
496    jabber                -                     -                   
5222   xmpp-client           -                     -
         
      

The table below describes the significant fields shown in the display.

Examples

The following is sample output from the show metadata flow classification table command:

Device# show metadata flow classification table

Policy Type Codes:
QOS     : QOS                            PM      : Performance Monitor            
PMD     : Performance Monitor Dynamic    MACE    : MACE                           
--------------------------------------------------------------------------------
Target          Flow ID    Dir   Policy     Filter(s)                
                                 Type      
---------------+----------+-----+----------+------------------------------------

Se2/0           1          OUT  
Se2/0           2          OUT  
Se2/0           3          OUT  
Se2/0           4          OUT   QOS        application telepresence-media
Se2/0           5          OUT   QOS        application telepresence-media
Se2/0           6          OUT  
Se2/0           7          OUT  
Se2/0           8          OUT   QOS        application telepresence-media
Se2/0           9          OUT  
                                                                      
      

The table below describes the significant fields shown in the display.

The following is sample output from the command:

Device# show metadata flow local-flow-id 22

To                                      From                                   

Protocol SPort   DPort   Ingress I/F              Egress I/F               
2012:33:1:2::2                          2012:33:1:2::1                         
UDP      49002   49003   n/a                      Serial2/0               

Metadata Attributes :

Global Session Id           :   74657374-2D54-502D-3100-000000000000-00000000-00000000 
Clock Frequency             :   123456 
End Point Model             :   Test-TP-Model 
Application Signaling Type  :   sip
Application Transport Type  :   rtp
Application Traffic Type    :   realtime
Application Device Class    :   room-conferencing
Application Category        :   voice-and-video
Application Group           :   telepresence-group
Application Media Type      :   video
Application Tag             :   218103921 (telepresence-media)
Application Name            :   telepresence-media 

Matched filters :

 Direction: IN: 
 Direction: OUT:  

The table below describes the significant fields shown in the display.

The following is sample output from the show metadata flow statistics command:

Device# show metadata flow statistics

Interface specific report :

Serial2/0: Classified flows : Ingress 0, Egress 0

Chunk statistics : 

Type               Allocated       Returned        Failed         

IP Flow             9                0                0              
Flow Key            29               20               0              
Source List         4                0                0              
Flow Info           29               29               0              
Attribute Data      29               29               0              
Feature Object      2                0                0              

Event Statistics: 

Add Flow                 : 9         Delete Flow              : 0       
Received                 : 30        Rejected                 : 0       
Transient                : 0         Posted                   : 29      
Ingress Change           : 0         Egress Change            : 11      
Unknown                   : 0         Source Limit Exceeded    : 0       

The table below describes the significant fields shown in the displays.

The following is sample output from the show metadata flow table command:

Device# show metadata flow table

Total number of IPV4 metadata flows 6

Flow  To              From            Proto DPort SPort Ingress      Egress     

4     10.0.0.1        10.0.0.2        UDP   49008 49007              Se2/0      
6     10.0.0.3        10.0.0.4        UDP   49004 49003              Se2/0      
5     10.2.0.3        10.2.0.6        UDP   49010 49009              Se2/0      
2     10.2.1.6        10.2.2.6        UDP   49004 49003              Se2/0      
1     10.2.2.6        10.2.3.6        UDP   49002 49001              Se2/0      
3     10.2.3.6        10.2.3.7        UDP   49006 49005              Se2/0      


Total number of IPV6 metadata flows 3

To                                      From                                   
Flow  Proto DPort SPort Ingress      Egress     

2001:DB8:1::1                          2001:DB8:1::2                          
9     UDP   49001 49000              Se2/0      
2001:DB8:1::3                          2001:DB8:1::4                         
7     UDP   49001 49000              Se2/0      
2001:DB8:1::12                        2001:DB8:1::13                         
8     UDP   49003 49002              Se2/0                         

Note	The output for the IPv6 metadata flow table appears in two lines as the IPv6 addresses can be long.

The following is sample output from the show metadata flow table application name sip ip command:

Device#  show metadata flow table application name sip ip

Flow  To        						From     					 Protocol  DPort  SPort  Ingress   Egress  SSRC

2     209.165.201.14  209.165.201.18  UDP      70    80       Eth1/1 		Eth1/2  3000
  

The following is sample output from the show metadata flow table application name sip ipv6 command:

Device# show metadata flow table application name sip ipv6

To                                      From                                   
Flow  Proto DPort SPort Ingress      Egress     

2001:DB8:1::3                          2001:DB8:1::4                          
9     UDP   49001 49000              Se2/0      
2001:DB8:1::5                          2001:DB8:1::6                         
7     UDP   49001 49000              Se2/0      
2001:DB8:1::12                        2001:DB8:1::14                         
8     UDP   49003 49002              Se2/0        
    

The following is sample output from the show metadata flow table filter destination command. You can specify the source or destination IPv4 address as the filter criterion.

Device# show metadata flow table filter destination 209.165.201.1

Entries To: 209.165.201.1         

Flow ID    From             Protocol DPort   SPort   Ingress I/F    Egress I/F     
1          209.165.201.3    UDP      1000    1000    Et0/0          Et0/1         
2          209.165.201.3    UDP      1001    1001    Et0/0          Et0/1         
Total Flows: 2

The following is sample output from the show metadata flow table ipv6 command:

Device# show metadata flow table ipv6

To                                      From                                   
Flow  Proto DPort SPort Ingress      Egress     

2001:DB8:1::1                          2001:DB8:1::2                          
9     UDP   49001 49000              Se2/0      
2001:DB8:1::3                          2001:DB8:1::4                         
7     UDP   49001 49000              Se2/0      
2001:DB8:1::12                        2001:DB8:1::13                         
8     UDP   49003 49002              Se2/0        

Examples

Examples

This example shows how to display information about the aggregate policer for MLS QoS:

Router# show mls qos aggregate-policer
ag1 (undefined)
    AgId=0 [ pol1 pol2 ]
ag2 64000 64000 conform-action set-dscp-transmit 56 exceed-action drop
    AgId=0 [ pol3 ]
ag3 32000 32000 conform-action set-dscp-transmit 34 exceed-action drop

In the output, the following applies:

• The AgId parameter displays the hardware-policer ID and is nonzero if assigned.

• The policy maps using the policer, if any, are listed in the square brackets ([]).

• If there are no policies using the policer, no AgId line is displayed.

• If the policer is referred to in policy maps, but has not been defined, [undefined ] is displayed.

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-agram 
Total Number of Available AG RAM indices : 1023
 Module [1]
 Free AGIDs : 1023
 Module [6]
 Free AGIDs : 1023

Examples

The following is sample output from the showmlsqosinterface fastethernet0/1 command:

Router# show mls qos interface fastethernet0/1
FastEthernet0/1
trust state: trust cos
COS override: dis
default COS: 0

The following example shows that there is no mls QoS command configured on the interface. the CoS/IP Precidence/DSCP values of incoming traffic will not be remarked as it passes through the switch.

Router# show mls qos interface f1/1
FastEthernet1/1
trust state: none  <<<
trust mode: none  <<<
COS override: dis
default COS: 0
pass-through: none

Examples

The following is sample output from the showmlsqosmapscos-dscp command displaying the DSCP values to which each CoS value will be mapped:

Router# show mls qos maps cos-dscp
Cos-dscp map:
        cos:  0  1  2  3  4  5  6  7
     --------------------------------
       dscp:  8  8  8  8 24 32 56 56

The following is sample output from the showmlsqosmapsdscp-cos command displaying the CoS values to which each DSCP value will be mapped:

Router# show mls qos maps dscp-cos
Dscp-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  7

This example shows how to display the QoS-map settings:

Router# show mls qos maps
   Policed-dscp map:
            0  1  2  3  4  5  6  7  8  9
   ----------------------------------
      00:  00 01 02 03 04 05 06 07 08 09
      10:  10 11 12 13 14 15 16 17 18 19
      20:  20 21 22 23 24 25 26 27 28 29
      30:  30 31 32 33 34 35 36 37 38 39
      40:  40 41 42 43 44 45 46 47 48 49
      50:  50 51 52 53 54 55 56 57 58 59
      60:  60 61 62 63
   Dscp-cos map:
            0  1  2  3  4  5  6  7  8  9
   ----------------------------------
      00:  00 00 00 00 00 00 00 00 01 01
      10:  01 01 01 01 01 01 02 02 02 02
      20:  02 02 02 02 03 03 03 03 03 03
      30:  03 03 04 04 04 04 04 04 04 04
      40:  05 05 05 05 05 05 05 05 06 06
      50:  06 06 06 06 06 06 07 07 07 07
      60:  07 07 07 07
   Cos-dscp map:
          cos:   0  1  2  3  4  5  6  7
       ----------------------------------
        dscp:   0  8 16 24 32 40 48 56
   IpPrecedence-dscp map:
       ipprec:   0  1  2  3  4  5  6  7
       ----------------------------------
        dscp:   0  8 16 24 32 40 48 56
Router# 

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 mutation
 
DSCP 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 09 
      1 :    10 11 12 13 14 15 16 17 18 19 
      2 :    20 21 22 23 24 25 26 27 28 29 
      3 :    08 31 32 33 34 35 36 37 38 39 
      4 :    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.

Examples

The following example shows an interface summary for MPLS QoS classes in policy maps:

Router# show mls qos mpls
QoS Summary [MPLS]: (* - shared aggregates, Mod - switch module)
Int Mod Dir Class-map DSCP Agg Trust Fl AgForward-By AgPoliced-By 
Id Id 
---------------------------------------------------------------------------------------------------------------------- 
Fa3/38 5 In exp2 0 1 dscp 0 378900 0 
Fa3/41 5 In exp4 0 3 dscp 0 0 0
All 5 - Default 0 0* No 0 1191011240 0 

The table below describes the significant fields shown in the display.

Examples

This example shows how to display protocol pass-through information:

Router# show mls qos protocol
RIP : Passthru mode 
OSPF : Passthru mode
ND : 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*

Examples

The following example shows sample output from the showmlsqosqueuinginterface gigabitethernet5/1 command on the Endor (RSP720-10G) card.

Router# show mls qos queuing interface gig5/1
Weighted Round-Robin
  Port QoS is enabled
  Port is untrusted
  Extend trust state: not trusted [COS = 0]
  Default COS is 0
    Queueing Mode In Tx direction: mode-cos
    Transmit queues [type = 1p3q8t]:
    Queue Id    Scheduling  Num of thresholds
    -----------------------------------------
       01         WRR                 08
       02         WRR                 08
       03         WRR                 08
       04         Priority            01
WRR bandwidth ratios:  100[queue 1] 150[queue 2] 200[queue 3] 
    queue-limit ratios:     50[queue 1]  20[queue 2]  15[queue 3]  15[Pri Queue]
    queue tail-drop-thresholds
    --------------------------
    1     70[1] 100[2] 100[3] 100[4] 100[5] 100[6] 100[7] 100[8] 
    2     70[1] 100[2] 100[3] 100[4] 100[5] 100[6] 100[7] 100[8] 
    3     100[1] 100[2] 100[3] 100[4] 100[5] 100[6] 100[7] 100[8] 
    queue random-detect-min-thresholds
    ----------------------------------
      1    40[1] 70[2] 70[3] 70[4] 70[5] 70[6] 70[7] 70[8] 
      2    40[1] 70[2] 70[3] 70[4] 70[5] 70[6] 70[7] 70[8] 
      3    70[1] 70[2] 70[3] 70[4] 70[5] 70[6] 70[7] 70[8] 
    queue random-detect-max-thresholds
    ----------------------------------
      1    70[1] 100[2] 100[3] 100[4] 100[5] 100[6] 100[7] 100[8] 
      2    70[1] 100[2] 100[3] 100[4] 100[5] 100[6] 100[7] 100[8] 
      3    100[1] 100[2] 100[3] 100[4] 100[5] 100[6] 100[7] 100[8] 
    WRED disabled queues:    
    queue thresh cos-map
    ---------------------------------------
    1     1      0 
    1     2      1 
    1     3      
    1     4      
    1     5      
    1     6      
    1     7      
    1     8      
    2     1      2 
    2     2      3 4 
    2     3      
    2     4      
    2     5      
    2     6      
    2     7      
    2     8      
    3     1      6 7 
    3     2      
    3     3      
    3     4      
    3     5      
    3     6      
    3     7      
    3     8      
    4     1      5 
    Queueing Mode In Rx direction: mode-cos
    Receive queues [type = 2q8t]:
    Queue Id    Scheduling  Num of thresholds
    -----------------------------------------
       01         WRR                 08
       02         WRR                 08
    WRR bandwidth ratios:  100[queue 1]   0[queue 2] 
    queue-limit ratios:    100[queue 1]   0[queue 2] 
    queue tail-drop-thresholds
    --------------------------
    1     100[1] 100[2] 100[3] 100[4] 100[5] 100[6] 100[7] 100[8] 
    2     100[1] 100[2] 100[3] 100[4] 100[5] 100[6] 100[7] 100[8] 
    queue random-detect-min-thresholds
    ----------------------------------
      1    40[1] 40[2] 50[3] 50[4] 50[5] 50[6] 50[7] 50[8] 
      2    100[1] 100[2] 100[3] 100[4] 100[5] 100[6] 100[7] 100[8] 
    queue random-detect-max-thresholds
    ----------------------------------
      1    70[1] 80[2] 90[3] 100[4] 100[5] 100[6] 100[7] 100[8] 
      2    100[1] 100[2] 100[3] 100[4] 100[5] 100[6] 100[7] 100[8] 
    queue thresh cos-map
    ---------------------------------------
    1     1      0 1 2 3 4 5 6 7 
    1     2      
    1     3      
    1     4      
    1     5      
    1     6      
    1     7      
    1     8      
    2     1      
    2     2      
    2     3      
    2     4      
    2     5      
    2     6      
    2     7      
    2     8      
  Packets dropped on Transmit:
    queue     dropped  [cos-map]
    ---------------------------------------------
    1                        0  [0 1 ]
    2                        0  [2 3 4 ]
    3                        0  [6 7 ]
    4                        0  [5 ]
  Packets dropped on Receive:
    BPDU packets:  0
    queue              dropped  [cos-map]
    ---------------------------------------------------
    1                        0  [0 1 2 3 4 5 6 7 ]
    2                        0  []
.
.
.

Examples

This example shows how to display information about the MLS-statistics data-export status and configuration:

Router# show mls qos statistics-export info 
QoS Statistics Data Export Status and Configuration information
---------------------------------------------------------------
Export Status : enabled
Export Interval : 250 seconds
Export Delimiter : @
Export Destination : 172.20.52.3, UDP port 514 Facility local6, Severity debug
 
QoS Statistics Data Export is enabled on following ports:
---------------------------------------------------------
FastEthernet5/24
 
QoS Statistics Data export is enabled on following shared aggregate policers:
-----------------------------------------------------------------------------
aggr1M
 
QoS Statistics Data Export is enabled on following class-maps:
---------------------------------------------------------------
class3

Examples

The following sample output from the showplatformhardwareaclentryglobal-qos command displays one result for inbound Address Resolution Protocol entries:

Switch# show platform hardware acl entry global-qos in arp
 
0x0000000000000003 arp ip any any mac any 

The following sample output from the showplatformhardwareaclentryglobal-qos command displays the detailed results for inbound Address Resolution Protocol entries (the legend provides definitions for abbreviations that may appear in the output):

Switch# show platform hardware acl entry global-qos in arp detail
------------------------------------------------------------------------------------------
ENTRY TYPE: A - ARP I - IPv4 M - MPLS O - MAC Entry S - IPv6(Six) C - Compaction L - L2V4 Suffix: D - dynamic entry E - exception entry R - reserved entry 
FIELDS: FS - first_seen/from_rp ACOS - acos/group_id F - ip_frag FF - frag_flag DPORT - dest_port SPORT - src_port LM - L2_miss GP - gpid_present ETYPE - enc_etype CEVLD - ce_vlan_valid MM - mpls_mcast FN - exp_from_null IV - ip_hdr_vld MV - mpls_valid E_CAU - exception_cause UK - U_key ACO - acos A/R - arp_rarp RR - req_repl GM - global_acl_fmt_match D-S-S-A - dest_mac_bcast, src_snd_mac_same, snd_tar_mac_same, arp_rarp_vld OM - ofe_mode SVLAN - Src_vlan
------------------------------------------------------------------------------------------

A

INDEX

LABEL

A/R

RR

IP SA

IP DA

SRC MAC

D-S-S-A

GM

LM

OM

RSLT

CNT

AR V

963

8191

1

7

0.0.0.0

0.0.0.0

FFFF.
FFFF.
FFFF

1-1-1-1

1

1

0

0x0000000000000003

0

AR M

963

0x0000

0

0x0

0.0.0.0

0.0.0.0

0000.
0000.
0000

0-0-0-1

0

0

1

Examples

The following is sample output from the show platform hardware pp active infrastructure pi npd rx policer command:

            
Router# show platform hardware pp active infrastructure pi npd rx policer 

PUNT POLICER
Ring |          Queue Name |           Punt rate |          Burst rate
-----+---------------------+---------------------+--------------------
 0   |     SW FORWARDING Q |                 500 |                1000 
 1   |  ROUTING PROTOCOL Q |                 500 |                1000 
 2   |              ICMP Q |                 500 |                1000 
 3   |              HOST Q |                1000 |                2000 
 4   |       ACL LOGGING Q |                 500 |                1000 
 5   |               STP Q |                3000 |                6000 
 6   |       L2 PROTOCOL Q |                1000 |                2000 
 7   |     MCAST CONTROL Q |                1000 |                2000 
 8   |         BROADCAST Q |                 500 |                1000 
 9   |               REP Q |                3000 |                6000 
10   |               CFM Q |                3000 |                6000 
11   |           CONTROL Q |                1000 |                2000 
12   |       IP MPLS TTL Q |                1000 |                2000 
13   |     DEFAULT MCAST Q |                 500 |                1000 
14   |  MCAST ROUTE DATA Q |                 500 |                1000 
15   |    MCAST MISMATCH Q |                 500 |                1000 
16   |          RPF FAIL Q |                 500 |                1000 
17   |  ROUTING THROTTLE Q |                 500 |                1000 
18   |             MCAST Q |                 500 |                1000 
19   |          MPLS OAM Q |                1000 |                2000 
20   |       IP MPLS MTU Q |                 500 |                1000 
21   |               PTP Q |                3000 |                6000 
22   |          LINUX ND Q |                 500 |                1000 
23   |         KEEPALIVE Q |                1000 |                2000 
24   |              ESMC Q |                3000 |                6000 
25   |          FPGA BFD Q |                3000 |                6000 
26   |          FPGA CCM Q |                3000 |                6000 
27   |          FPGA CFE Q |                3000 |                6000 
28   |          L2PT DUP Q |                4000 |                8000                   

      

The table below describes the significant fields shown in the display.

Examples

The following example shows how to see if the QoS: Packet Marking Statistics or QoS: Packet Matching Statistics feature is enabled:

Router# 
show platform hardware qfp active feature qos config global

Marker statistics are: enabled
Match per filter statistics are: enabled

The table below describes the significant fields shown in the display.

Examples

The following is a sample output of the showplatformlowq command.

Router# show platform lowq
TenGigabitEthernet10/1
Input Queue count:8     Output Queue count:8    Total Queue count:16

The following table describes the fields in the command:

Examples

The following example shows a router that has service policies configured only on VLAN interfaces:

Router# show platform qos policy-map
 
 service policy configured on int vlan: TRUE 
 # of int vlan service policy instances: 3 
 match input vlan service policy configured: FALSE 
 # of match input vlan service policy instances: 0 

The following example shows a router that has service policies configured on VLAN interfaces and that has a service policy configured with matchinputvlan . 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-map
 
 service policy configured on int vlan: TRUE 
 # of int vlan service policy instances: 1 
 match input vlan service policy configured: TRUE 
 # of match input vlan service policy instances: 1 

The table below describes each field shown in the showplatformqospolicy-map command:

Examples

The following is sample output from the show platform software infrastructure punt statistics command:

        Router# show platform software infrastructure punt statistics             
UEA Punt Statistics

Global drops : 0

 Queue Name             | Rx count                  |  Drop count
------------------------+---------------------------+-----------------------
 SW FORWARDING Q        | 0                         | 0                        
 ROUTING PROTOCOL Q     | 0                         | 0                        
 ICMP Q                 | 0                         | 0                        
 HOST Q                 | 57115                     | 0                        
 ACL LOGGING Q          | 0                         | 0                        
 STP Q                  | 0                         | 0                        
 L2 PROTOCOL Q          | 6571                      | 0                        
 MCAST CONTROL Q        | 208839                    | 0                        
 BROADCAST Q            | 4                         | 0                        
 REP Q                  | 0                         | 0                        
 CFM Q                  | 0                         | 0                        
 CONTROL Q              | 0                         | 0                        
 IP MPLS TTL Q          | 0                         | 0                        
 DEFAULT MCAST Q        | 0                         | 0                        
 MCAST ROUTE DATA Q     | 0                         | 0                        
 MCAST MISMATCH Q       | 0                         | 0                        
 RPF FAIL Q             | 0                         | 0                        
 ROUTING THROTTLE Q     | 87                        | 0                        
 MCAST Q                | 0                         | 0                        
 MPLS OAM Q             | 0                         | 0                        
 IP MPLS MTU Q          | 0                         | 0                        
 PTP Q                  | 0                         | 0                        
 LINUX ND Q             | 0                         | 0                        
 KEEPALIVE Q            | 0                         | 0                        
 ESMC Q                 | 0                         | 0                        
 FPGA BFD Q             | 0                         | 0                        
 FPGA CCM Q             | 0                         | 0                        
 FPGA CFE Q             | 0                         | 0                        
 L2PT DUP Q             | 0                         | 0                        

      

The table below describes the significant fields shown in the display.

Examples

The following is sample output from the showpolicy-managerevents command:

Router# show policy-manager events
Event Statistics
0          catastrophic
0          critical
0          high
0          medium
0          low
0          positive
The following events were discarded
0          unknown
Event buffer pool
Number of free event buffers = 300
Number of events awaiting processing by Policy Manager process = 0

The table below describes the significant fields shown in the display.

Examples

The following is sample output from the showpolicy-managerpolicy command. The field descriptions are self-explanatory.

Router# show policy-manager policy 
Status (S) codes:
A = active
D = deactivated
S ID    Subsystem                 Name

Examples

This section provides sample output from typical showpolicy-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 po1
Policy 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-map
 
Policy 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) 

The table below describes the significant fields shown in the display.

Frame Relay Voice-Adaptive Traffic-Shaping: Example

The following sample output for the show-policymap 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-map
  Policy Map VSD1
    Class VOICE1
      Strict Priority
      Bandwidth 10 (kbps) Burst 250 (Bytes)
    Class SIGNALS1
      Bandwidth 8 (kbps) Max Threshold 64 (packets)
    Class DATA1
      Bandwidth 15 (kbps) Max Threshold 64 (packets)
  Policy Map MQC-SHAPE-LLQ1
    Class class-default
      Traffic Shaping
         Average Rate Traffic Shaping
                 CIR 63000 (bps) Max. Buffers Limit 1000 (Packets)
                 Adapt to 8000 (bps)
                 Voice Adapt Deactivation Timer 30 Sec 
      service-policy VSD1

Note	In Cisco IOS Release 12.4(20)T, if an interface configured with a policy map is full of heavy traffic, the implicit policer allows the traffic as defined in the bandwidth statement of each traffic class.

The table below describes the significant fields shown in the display.

Traffic Policing: Example

The following is sample output from the showpolicy-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 policy1
  Policy Map policy1
    Class class1
     police cir percent 20 bc 300 ms pir percent 40 be 400 ms
       conform-action transmit 
       exceed-action drop 
       violate-action drop 

The table below describes the significant fields shown in the display.

Two-Rate Traffic Policing: Example

The following is sample output from the showpolicy-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 police
Router(config-cmap)# match access-group 101
Router(config-cmap)# policy-map policy1
Router(config-pmap)# class police
Router(config-pmap-c)# police cir 500000 bc 10000 pir 1000000 be 10000 conform-action
transmit exceed-action set-prec-transmit 2 violate-action drop
Router(config-pmap-c)# interface serial3/0
Router(config-pmap-c)# exit
Router(config-pmap)# exit
Router(config)# interface serial3/0
Router(config-if)# service-policy output policy1
Router(config-if)# end
The following sample output shows the contents of the policy map called policy1 :
Router# show policy-map policy1

 Policy Map policy1
  Class police
   police cir 500000 conform-burst 10000 pir 1000000 peak-burst 10000 conform-action
   transmit exceed-action set-prec-transmit 2 violate-action drop

Traffic 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.

The table below describes the significant fields shown in the display.

Multiple Traffic Policing Actions: Example

The following is sample output from the showpolicy-map command when the Policer Enhancement--Multiple Actions feature has been configured. The following sample output from the showpolicy-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 police
  Policy Map police
    Class class-default
     police cir 1000000 bc 31250 pir 2000000 be 31250
       conform-action transmit 
       exceed-action set-prec-transmit 4
       exceed-action set-frde-transmit 
       violate-action set-prec-transmit 2
       violate-action set-frde-transmit 

Packets 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	Actions are specified by using the action argument of the police command. For more information about the available actions, see the police command reference page.

The table below describes the significant fields shown in the display.

Explicit Congestion Notification: Example

The following is sample output from the showpolicy-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-map
   Policy Map pol1
     Class class-default
       Weighted Fair Queueing
             Bandwidth 70 (%)
             exponential weight 9
             explicit congestion notification
             class    min-threshold    max-threshold    mark-probability
             ----------------------------------------------------------
             ----------------------------------------------------------
 
             0        -                -                1/10
             1        -                -                1/10
             2        -                -                1/10
             3        -                -                1/10
             4        -                -                1/10
             5        -                -                1/10
             6        -                -                1/10
             7        -                -                1/10
             rsvp     -                -                1/10

The table below 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
 policy1
 Policy Map policy1
  Class c1
   drop

The table below 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 policy1
Policy Map policy1
 class class1
    police cir percent 50
Router# show policy-map policy2
Policy Map policy2
 class class2
    shape average percent 35

The following example displays the contents of the service policy map called po1 :

Router# show policy-map po1
Policy 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-map
 
Policy 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)

The table below describes the significant fields shown in the display.

Enhanced Packet Marking: Example

The following sample output from the showpolicy-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 showpolicy-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 policy1
  Policy Map policy1
    Class class-default
      set precedence cos table table-map1
Router# show policy-map policy2
   Policy Map policy2
    Class class-default
      set cos precedence table table-map2

The table below 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_policy
  Policy Map vlan10_policy
    Class class-default
      Average Rate Traffic Shaping
      cir 1000000 (bps)
      bandwidth remaining ratio 10
      service-policy child_policy

The table below 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-test
Class class-default
Average Rate Traffic Shaping
cir 10% account dot1q aal5 snap-rbe

The table below describes the significant fields shown in the display.

Tunnel-Marking: Example

In this sample output of theshowpolicy-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	In Cisco IOS Release 12.4(15)T2, GRE-tunnel marking is supported on the RPM-XF platform only .

Router# show policy-map
Policy Map TUNNEL_MARKING
    Class MATCH_FRDE
      set ip precedence tunnel 4

The table below describes the fields shown in the display.

HQF: Example 1

The following sample output from the showpolicy-map command displays the configuration for a policy map called test1:

Router# show policy-map test1
  Policy Map test1
    Class class-default
      Average Rate Traffic Shaping
      cir 1536000 (bps)
      service-policy test2

The table below describes the fields shown in the display.

HQF: Example 2

The following sample output from the showpolicy-map command displays the configuration for a policy map called test2:

Router# show policy-map test2
  Policy Map test2
    Class RT
      priority 20 (%)
    Class BH
      bandwidth 40 (%)
      queue-limit 128 packets
    Class BL
      bandwidth 35 (%)
       packet-based wred, exponential weight 9
 
      dscp    min-threshold    max-threshold    mark-probablity
      ----------------------------------------------------------
      af21 (18)     100              400              1/10
      default (0)   -                -                1/10

The table below describes the fields shown in the display.

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 class7


Class class7
 Bandwidth 937 (kbps) Max Thresh 64 (packets)

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-plane
 
Control Plane 
Service-policy input:TEST
Class-map:TEST (match-all)
      20 packets, 11280 bytes
      5 minute offered rate 0 bps, drop rate 0 bps
      Match:access-group 101
      police:
        8000 bps, 1500 limit, 1500 extended limit
        conformed 15 packets, 6210 bytes; action:transmit
        exceeded 5 packets, 5070 bytes; action:drop
        violated 0 packets, 0 bytes; action:drop
        conformed 0 bps, exceed 0 bps, violate 0 bps
Class-map:class-default (match-any)
      105325 packets, 11415151 bytes
      5 minute offered rate 0 bps, drop rate 0 bps
      Match:any

The table below describes the significant fields shown in the display.

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.