Understanding cos-based packet statistics, Configuring cos-based packet statistics, Table 14-6 – Cisco 15327 User Manual
Page 237

14-29
Ethernet Card Software Feature and Configuration Guide, R7.2
Chapter 14 Configuring Quality of Service
Understanding CoS-Based Packet Statistics
policy-map policy_egress_bandwidth
class customer_core_traffic
bandwidth 1000
class customer_voice
priority 1000
class customer_data
bandwidth 3000
class class-default
bandwidth 5000
!
!
interface POS0
no ip address
crc 32
service-policy output policy_egress_bandwidth
!
Understanding CoS-Based Packet Statistics
Enhanced performance monitoring displays per-CoS packet statistics on the ML-Series card interfaces
when CoS accounting is enabled. Per-CoS packet statistics are only supported for bridged services, not
for IP routing or Multiprotocol Label Switching (MPLS). CoS-based traffic utilization is displayed at
the Fast Ethernet or Gigabit Ethernet interface or subinterface (VLAN) level, or at the POS interface
level. It is not displayed at the POS subinterface level. Cisco proprietary RPR statistics are not available
at the SPR interface level, but statistics are available for the individual POS ports that make up the SPR
interface. EtherChannel (port-channel) and BVI statistics are available only at the member port level.
shows the types of statistics available at specific interfaces.
CoS-based packet statistics are available through the Cisco IOS CLI and Simple Network Management
Protocol (SNMP), using an extension of the CISCO-PORT-QOS MIB. They are not available through
CTC.
Configuring CoS-Based Packet Statistics
Note
CoS-based packet statistics require the enhanced microcode image to be loaded onto the ML-Series card.
Table 14-6
Packet Statistics on ML-Series Card Interfaces
Statistics Collected
Gigabit/Fast Ethernet
Interface
Gigabit/Fast Ethernet
Subinterface (VLAN)
POS
Interface
POS
Subinterface
Input—Packets and Bytes
Yes
Yes
No
No
Output—Packets and Bytes Yes
Yes
No
No
Drop Count—Packets and
Bytes
1
1.
Drop counts only include discards caused by output congestion and are counted at the output interface.
Yes
No
Yes
No