hwhqosUseridStatTable
This Table is supported only on the NetEngine 8000 F1A.
This table is used to query the statistics of a specified user ID.
The indexes of the table are hwhqosUseridStatUserid, hwhqosUseridStatQueue, hwhqosUseridStatDirection.
|
OID |
Object |
Syntax |
Max Access |
Description |
Implemented Specifications |
|---|---|---|---|---|---|
|
1.3.6.1.4.1.2011.5.25.132.1.52.1.1 |
hwhqosUseridStatUserid |
Unsigned32 |
read-only |
The value of this object identifies an HQoS user ID. |
This object is implemented as defined in the corresponding MIB files. |
|
1.3.6.1.4.1.2011.5.25.132.1.52.1.2 |
hwhqosUseridStatQueue |
INTEGER{be(1),af1(2),af2(3),af3(4),af4(5),ef(6),cs6(7),cs7(8),total(9)} |
read-only |
This object indicates a queue. |
This object is implemented as defined in the corresponding MIB files. |
|
1.3.6.1.4.1.2011.5.25.132.1.52.1.3 |
hwhqosUseridStatDirection |
INTEGER{inbound(1),outbound(2)} |
read-only |
The value of this object identifies the direction of the traffic to which HQoS applies. |
This object is implemented as defined in the corresponding MIB files. |
|
1.3.6.1.4.1.2011.5.25.132.1.52.1.4 |
hwhqosUseridStatPassBytes |
Counter64 |
read-only |
This object indicates the number of forwarded user traffic bytes. |
This object is implemented as defined in the corresponding MIB files. |
|
1.3.6.1.4.1.2011.5.25.132.1.52.1.5 |
hwhqosUseridStatDropBytes |
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.52.1.6 |
hwhqosUseridStatPassPackets |
Counter64 |
read-only |
This object indicates the number of forwarded user traffic packets. |
This object is implemented as defined in the corresponding MIB files. |
|
1.3.6.1.4.1.2011.5.25.132.1.52.1.7 |
hwhqosUseridStatDropPackets |
Counter64 |
read-only |
This object indicates the number of dropped packets. |
This object is implemented as defined in the corresponding MIB files. |
|
1.3.6.1.4.1.2011.5.25.132.1.52.1.8 |
hwhqosUseridStatPassPacketsRate |
Counter64 |
read-only |
This object indicates the rate at which user traffic 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.52.1.9 |
hwhqosUseridStatDropPacketsRate |
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.52.1.10 |
hwhqosUseridStatReset |
INTEGER{reset(1)} |
read-create |
This object indicates the flag of clearing the statistics. |
This object is implemented as defined in the corresponding MIB files. |
|
1.3.6.1.4.1.2011.5.25.132.1.52.1.11 |
hwhqosUseridStatPassBytesRate |
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.52.1.12 |
hwhqosUseridStatDropBytesRate |
Counter64 |
read-only |
This object indicates the rate at which bytes are dropped. |
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
This object indicates that the user goes online successfully, and SQ/CAR resources are used to limit the rate.
When a get operation is performed on a sub-object of this MIB table on a single NMS and the device or network is not heavily loaded, getting one data takes less than 30 ms (the average time for a non-low-performance board is 15 ms). If multiple data is gotten, the time is accumulated. If data of other nodes is collected, smooth data synchronization is performed on the device, or the device or network is heavily loaded, the collection takes a longer time. The default timeout period is 5s for each collection. If you need to manually set the timeout period or use a third-party NMS, you are advised to adjust the timeout period based on the actual collection scenario to prevent collection timeout.
When a walk operation is performed on this MIB table on a single NMS and the device or network is not heavily loaded, collecting 1000 instances takes less than 20s. In a scenario with a large number of users (32K or more online users), the walk operation takes a long time and a large amount of data is generated, which is inconvenient for query. The get or get-bulk operation is recommended for specific query. If data of other nodes is collected, smooth data synchronization is performed on the device, or the device or network is heavily loaded, the collection time increases.
When a get-bulk operation is performed on this MIB table on a single NMS and the device or network is not heavily loaded, collecting 50 records takes less than 1s. If data of other nodes is collected, smooth data synchronization is performed on the device, or the device or network is heavily loaded, the collection time increases. You are advised to adjust the collection period as required.
When a walk operation is performed on this MIB table on a single NMS and the device or network is not heavily loaded, the CPU usage increases by 10% to 20% if no CPU rate is limited. If the CPU rate is limited, the total time is prolonged and a timeout may occur. You are advised to adjust the rate limit and timeout period based on the actual scenario.