Table of Contents
Advertisement
show policy-map interface
Class-map: class-default (match-any)
0 packets, 0 bytes
5 minute offered rate 0 bps, drop rate 0 bps
Match: any
Table 50
according to the relevant QoS feature.
Table 50
Field
Fields Associated with Classes or Service Policies
Service-policy output
Class-map
packets and bytes
offered rate
drop rate
Note
Match
Cisco MWR 2941 Router Command Reference, Release 15.0(1)MR
582
describes significant fields commonly shown in the displays. The fields in the table are grouped
show policy-map interface Field Descriptions
Description
Name of the output service policy applied to the specified interface or VC.
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.
Number of packets (also shown in bytes) identified as belonging to the
class of traffic being displayed.
Rate, in kbps, of packets coming in to the class.
Note
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.
In distributed architecture platforms (such as the Cisco 7500 series platform), the value of the
transfer rate, calculated as the difference between the offered rate and the drop rate counters,
can sporadically deviate from the average by up to 20 percent or more. This can occur while
no corresponding burst is registered by independent traffic analyzer equipment.
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.
Cisco MWR 2941 Router Command Reference, Release 15.0(1)MR
If the packets are compressed over an outgoing interface, the
improved packet rate achieved by packet compression is not
reflected in the offered rate. Also, if the packets are classified
before they enter a combination of tunnels (for example, a generic
routing encapsulation (GRE) tunnel and an IP Security (IPSec)
tunnel), the offered rate does not include all the extra overhead
associated with tunnel encapsulation in general. Depending on the
configuration, the offered rate may include no overhead, may
include the overhead for only one tunnel encapsulation, or may
include the overhead for all tunnel encapsulations. In most of the
GRE and IPSec tunnel configurations, the offered rate includes
the overhead for GRE tunnel encapsulation only.
1
OL-23890-01
Advertisement
Table of Contents
