hwCBQoSHierarchicalCarStatisticsTable

Query CAR statistics of a hierarchical policy.

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

OID	Object	Syntax	Max Access	Description	Implemented Specifications
1.3.6.1.4.1.2011.5.25.32.1.1.5.6.21.1.1	hwCBQoSHierarchicalCarAclPolicyIndex	Integer32	read-only	ID of a hierarchical policy.	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.21.1.2	hwCBQoSHierarchicalCarClassifierIndex	Integer32	read-only	ID of the classifier in a hierarchical policy.	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.21.1.3	hwCBQoSHierarchicalCarConformedPackets	Counter64	read-only	Number of packets marked green by CAR.	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.21.1.4	hwCBQoSHierarchicalCarConformedBytes	Counter64	read-only	Number of bytes marked green by CAR.	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.21.1.5	hwCBQoSHierarchicalCarConformedPacketRate	Counter64	read-only	Rate of packets marked green by CAR.	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.21.1.6	hwCBQoSHierarchicalCarConformedByteRate	Counter64	read-only	Rate of bytes marked green by CAR.	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.21.1.7	hwCBQoSHierarchicalCarExceededPackets	Counter64	read-only	Number of packets marked yellow by CAR.	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.21.1.8	hwCBQoSHierarchicalCarExceededBytes	Counter64	read-only	Number of bytes marked yellow by CAR.	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.21.1.9	hwCBQoSHierarchicalCarExceededPacketRate	Counter64	read-only	Rate of packets marked yellow by CAR.	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.21.1.10	hwCBQoSHierarchicalCarExceededByteRate	Counter64	read-only	Rate of bytes marked yellow by CAR.	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.21.1.11	hwCBQoSHierarchicalCarOverflowPackets	Counter64	read-only	Number of packets marked red by CAR.	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.21.1.12	hwCBQoSHierarchicalCarOverflowBytes	Counter64	read-only	Number of bytes marked red by CAR.	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.21.1.13	hwCBQoSHierarchicalCarOverflowPacketRate	Counter64	read-only	Rate of packets marked red by CAR.	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.21.1.14	hwCBQoSHierarchicalCarOverflowByteRate	Counter64	read-only	Rate of bytes marked red by CAR.	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.21.1.15	hwCBQoSHierarchicalCarPassedPackets	Counter64	read-only	Number of packets allowed by CAR.	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.21.1.16	hwCBQoSHierarchicalCarPassedBytes	Counter64	read-only	Number of bytes allowed by CAR.	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.21.1.17	hwCBQoSHierarchicalCarDroppedPackets	Counter64	read-only	Number of packets dropped by CAR.	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.21.1.18	hwCBQoSHierarchicalCarDroppedBytes	Counter64	read-only	Number of bytes dropped by CAR.	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

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 calculates the collection rate, statistics are obtained from the device. The collection time difference is that for the NMS to receive packets. When the device or network is heavily loaded, there is a large deviation between the time difference for the device to collect data packets and the time difference for the NMS to calculate the collection rate. The shorter the collection period, the larger the deviation. It is recommended that the collection period be not less than 1 minute.

2. To reduce the impact of performance data procession on the device CPU, the device returns the data saved in the software during the performance data procession on the NMS (the device periodically reads data from hardware and writes it into software). 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 80 ms. In normal configurations, the time is less than 30 ms. In extreme configurations (a large number of interfaces' data is collected or a large number of traffic classifier-behavior pairs are configured, requiring the one-by-one determination of valid indexes), the time increases to about 80 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 50s. In extreme configurations (a large number of traffic classifier-behavior pairs or consecutive VLAN segments are configured on an interface whose data is to be collected), the time increases to 5 minutes. 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 10 records takes less than 1s. In extreme configurations (a large number of traffic classifier-behavior pairs are configured on an interface whose data is to be collected, requiring the traversal and accumulation of underlying data), the collection time increases. 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.