hwCBQoSClassifierStatisticsTable

This table is used to record class-based multi-field traffic classification statistics.

The indexes of the table are hwCBQoSIfApplyPolicyIfIndex, hwCBQoSIfApplyPolicyDirection, hwCBQoSIfVlanApplyPolicyVlanid1, hwCBQoSIfVlanApplyPolicyVlanid2, hwCBQoSPolicyClassifierIndex.

OID	Object	Syntax	Max Access	Description	Implemented Specifications
1.3.6.1.4.1.2011.5.25.32.1.1.5.6.3.1.4	hwCBQoSPolicyClassifierIndex	Integer32	read-only	Indicates the index of a traffic class.	This object is implemented as defined in the corresponding MIB files.
1.3.6.1.4.1.2011.5.25.32.1.1.5.6.3.1.5	hwCBQoSClassifierMatchedPackets	Counter64	read-only	This object indicates the number of matching packets.	This object is implemented as defined in the corresponding MIB files.
1.3.6.1.4.1.2011.5.25.32.1.1.5.6.3.1.6	hwCBQoSClassifierMatchedBytes	Counter64	read-only	Indicates the number of matched bytes.	This object is implemented as defined in the corresponding MIB files.
1.3.6.1.4.1.2011.5.25.32.1.1.5.6.3.1.7	hwCBQoSClassifierMatchedPassPackets	Counter64	read-only	This object indicates the number of matching and forwarded packets.	This object is implemented as defined in the corresponding MIB files.
1.3.6.1.4.1.2011.5.25.32.1.1.5.6.3.1.8	hwCBQoSClassifierMatchedPassBytes	Counter64	read-only	Indicates the matched and passed traffic in bytes.	This object is implemented as defined in the corresponding MIB files.
1.3.6.1.4.1.2011.5.25.32.1.1.5.6.3.1.9	hwCBQoSClassifierMatchedDropPackets	Counter64	read-only	This object indicates the number of matching and discarded packets.	This object is implemented as defined in the corresponding MIB files.
1.3.6.1.4.1.2011.5.25.32.1.1.5.6.3.1.10	hwCBQoSClassifierMatchedDropBytes	Counter64	read-only	Indicates the matched and discarded traffic in bytes.	This object is implemented as defined in the corresponding MIB files.
1.3.6.1.4.1.2011.5.25.32.1.1.5.6.3.1.11	hwCBQoSClassifierMatchedPacketRate	Counter64	read-only	Rate of packets that match the traffic classifier.	This object is implemented as defined in the corresponding MIB files.
1.3.6.1.4.1.2011.5.25.32.1.1.5.6.3.1.12	hwCBQoSClassifierMatchedByteRate	Counter64	read-only	Rate of bytes that match the traffic classifier.	This object is implemented as defined in the corresponding MIB files.
1.3.6.1.4.1.2011.5.25.32.1.1.5.6.3.1.13	hwCBQoSClassifierMatchedPassPacketRate	Counter64	read-only	Rate of packets that match the traffic classifier and pass through.	This object is implemented as defined in the corresponding MIB files.
1.3.6.1.4.1.2011.5.25.32.1.1.5.6.3.1.14	hwCBQoSClassifierMatchedPassByteRate	Counter64	read-only	Rate of bytes that match the traffic classifier and pass through.	This object is implemented as defined in the corresponding MIB files.
1.3.6.1.4.1.2011.5.25.32.1.1.5.6.3.1.15	hwCBQoSClassifierMatchedDropPacketRate	Counter64	read-only	Rate of packets that match the traffic classification policy and are discarded.	This object is implemented as defined in the corresponding MIB files.
1.3.6.1.4.1.2011.5.25.32.1.1.5.6.3.1.16	hwCBQoSClassifierMatchedDropByteRate	Counter64	read-only	Rate of bytes that match the traffic classification policy and are discarded.	This object is implemented as defined in the corresponding MIB files.

Creation Restriction

No entry can be created in this table.

Modification Restriction

The entries in this table cannot be modified.

Deletion Restriction

The entries in this table cannot be deleted.

Access Restriction

QoS MIB statistics are monitored in real time. It is recommended that the monitoring period be greater than or equal to 1 minute. If the monitoring period is less than 1 minute, the monitoring waveform may be unstable. The possible causes are as follows:

1. When the NMS calculates the collection rate, the collection count is obtained from the device. The collection time difference is calculated based on the time when the NMS receives packets. When the device or network is heavily loaded, the difference between the time difference collected on the device side and the time difference calculated on the NMS is large. The shorter the collection period, the larger the difference. Therefore, it is recommended that the collection period be greater than or equal to 1 minute.

2. To reduce the impact of performance data procession on device CPU, the device returns data saved using software when the NMS-side performance data procession is implemented (hardware data is periodically recorded into software on the device side).