This table is used to query the statistics of user group queues.
The indexes of the table are hwhqosUserGroupQueueStatisticsGroupName, hwhqosUserGroupQueueStatisticsDirection, hwhqosUserGroupQueueStatisticsSlotNumber, hwhqosUserGroupQueueStatisticsQueueIndex.
|
OID |
Object |
Syntax |
Max Access |
Description |
Implemented Specifications |
|---|---|---|---|---|---|
|
1.3.6.1.4.1.2011.5.25.132.1.33.1.1 |
hwhqosUserGroupQueueStatisticsGroupName |
OCTET STRING{(1,31)} |
read-only |
The value of this object identifies the name of a user group queue. |
This object is implemented as defined in the corresponding MIB files. |
|
1.3.6.1.4.1.2011.5.25.132.1.33.1.2 |
hwhqosUserGroupQueueStatisticsDirection |
INTEGER{inbound(1),outbound(2)} |
read-only |
This object indicates the traffic direction to which the user group queue profile is applied. |
This object is implemented as defined in the corresponding MIB files. |
|
1.3.6.1.4.1.2011.5.25.132.1.33.1.3 |
hwhqosUserGroupQueueStatisticsSlotNumber |
Integer32{(0,128)} |
read-only |
The value of this object identifies the number of the slot where a user group queue template is applied. |
This object is implemented as defined in the corresponding MIB files. |
|
1.3.6.1.4.1.2011.5.25.132.1.33.1.4 |
hwhqosUserGroupQueueStatisticsQueueIndex |
INTEGER{be(1),af1(2),af2(3),af3(4),af4(5),ef(6),cs6(7),cs7(8),total(9)} |
read-only |
This object indicates the index of a user group queue. |
This object is implemented as defined in the corresponding MIB files. |
|
1.3.6.1.4.1.2011.5.25.132.1.33.1.5 |
hwhqosUserGroupQueueStatisticsReset |
INTEGER{reset(1)} |
read-create |
This object indicates the resetting of statistics. |
The actually supported access is read-write. |
|
1.3.6.1.4.1.2011.5.25.132.1.33.1.6 |
hwhqosUserGroupQueueStatisticsPassPackets |
Counter64 |
read-only |
This object indicates the number of forwarded packets. |
This object is implemented as defined in the corresponding MIB files. |
|
1.3.6.1.4.1.2011.5.25.132.1.33.1.7 |
hwhqosUserGroupQueueStatisticsPassBytes |
Counter64 |
read-only |
This object indicates the number of forwarded bytes. |
This object is implemented as defined in the corresponding MIB files. |
|
1.3.6.1.4.1.2011.5.25.132.1.33.1.8 |
hwhqosUserGroupQueueStatisticsDropPackets |
Counter64 |
read-only |
This object indicates the number of discarded packets. |
This object is implemented as defined in the corresponding MIB files. |
|
1.3.6.1.4.1.2011.5.25.132.1.33.1.9 |
hwhqosUserGroupQueueStatisticsDropBytes |
Counter64 |
read-only |
This object indicates the number of dropped bytes. |
This object is implemented as defined in the corresponding MIB files. |
|
1.3.6.1.4.1.2011.5.25.132.1.33.1.10 |
hwhqosUserGroupQueueStatisticsPassPacketsRate |
Counter64 |
read-only |
This object indicates the rate at which packets are forwarded. |
This object is implemented as defined in the corresponding MIB files. |
|
1.3.6.1.4.1.2011.5.25.132.1.33.1.11 |
hwhqosUserGroupQueueStatisticsPassBytesRate |
Counter64 |
read-only |
This object indicates the rate at which bytes are forwarded. |
This object is implemented as defined in the corresponding MIB files. |
|
1.3.6.1.4.1.2011.5.25.132.1.33.1.12 |
hwhqosUserGroupQueueStatisticsDropPacketsRate |
Counter64 |
read-only |
This object indicates the rate at which packets are dropped. |
This object is implemented as defined in the corresponding MIB files. |
|
1.3.6.1.4.1.2011.5.25.132.1.33.1.13 |
hwhqosUserGroupQueueStatisticsDropBytesRate |
Counter64 |
read-only |
This object indicates the rate at which bytes are discarded. |
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).
3.When you perform the get operation on the sub-object of this MIB table, if the device or network is not in the high load state, it takes less than 500 ms to get the data of a single object [In normal configuration, the time taken is less than 300 ms. In extreme configuration (the involved interface configuration occupies a large number of SQs and the underlying data needs to be traversed), it takes about 500 ms to get data.] If you attempt to get data of multiple objects, the time accumulates. For example, collecting the data of other objects, smooth reconciliation of devices, or high load of the device or network increases the time.
4.The default timeout period of the NMS is set to 5s for one operation. If you need to set it manually or using a non-Huawei NMS, you are advised to adjust the timeout period based on the actual collection scenario to prevent collection timeout.