This table records classifier statistics.
The indexes of the table are hwCBQoSIfApplyPolicyIfIndex , hwCBQoSIfVlanApplyPolicyVlanid1, hwCBQoSIfApplyPolicyDirection, hwCBQoSPolicyStatClassifierName.
|
OID |
Object |
Syntax |
Max Access |
Description |
Implemented Specifications |
|---|---|---|---|---|---|
|
1.3.6.1.4.1.2011.5.25.32.1.1.5.6.4.1.1 |
hwCBQoSPolicyStatClassifierName |
OCTET STRING{(1,127)} |
read-only |
This object indicates the classifier name. |
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.4.1.2 |
hwCBQoSPolicyStatClassifierMatchedPackets |
Counter64 |
read-only |
Number of matched 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.4.1.3 |
hwCBQoSPolicyStatClassifierMatchedBytes |
Counter64 |
read-only |
This object indicates the number of matching 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.4.1.6 |
hwCBQoSPolicyStatClassifierMatchedPassPackets |
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.4.1.7 |
hwCBQoSPolicyStatClassifierMatchedPassBytes |
Counter64 |
read-only |
This object indicates the number of matching and forwarded 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.4.1.8 |
hwCBQoSPolicyStatClassifierMatchedDropPackets |
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.4.1.9 |
hwCBQoSPolicyStatClassifierMatchedDropBytes |
Counter64 |
read-only |
This object indicates the number of matching and discarded 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.4.1.10 |
hwCBQoSPolicyStatClassifierMatchedPacketsRate |
Counter64 |
read-only |
Rate of matched 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.4.1.11 |
hwCBQoSPolicyStatClassifierMatchedBytesRate |
Counter64 |
read-only |
This object indicates the average number of matching 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.4.1.12 |
hwCBQoSPolicyStatClassifierMatchedPassPacketsRate |
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.4.1.13 |
hwCBQoSPolicyStatClassifierMatchedPassBytesRate |
Counter64 |
read-only |
This object indicates the average number of matching and forwarded 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.4.1.14 |
hwCBQoSPolicyStatClassifierMatchedDropPacketsRate |
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.4.1.15 |
hwCBQoSPolicyStatClassifierMatchedDropBytesRate |
Counter64 |
read-only |
This object indicates the average number of matching and discarded bytes. |
This object is implemented as defined in the corresponding MIB files. |
None.
QoS MIB statistics are monitored in real time. The monitoring period cannot be set to less than 1 minute. If less than 1 minute is set, the monitor waveform may be unstable. The main causes are as follows:
1. When the NMS is used to calculate the collection rate, the collection statistics information is obtained from the device side, and collection time difference means the time difference of packets received by the NMS. When the device or network load is high, there will be a deviation between the time difference of collecting data packets on the device side and that of calculating collection rate on the NMS side. The shorter the collection period, the larger the deviation. So the monitoring period cannot be set to less than 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).