Classifier-Specific Statistics Accounting for Classifier Groups Overview

Classifier groups support the classifier-specific statistics accounting feature, which defines a new policy rule for input and output policies to take into account only the statistics of the classifier groups that have the classifier action set as aaa count enable. You can use the aaa count enable command to enable the classifier-specific statistics accounting feature for each classifier group.

When the classifier-specific statistics accounting feature is enabled in any of the classifier groups assigned to IPv4 and IPv6 interfaces, the router adds the forwarded bytes of only the classifier groups that have the classifier action set as aaa count enable and sends the total bytes to authentication, authorization, and accounting (AAA) for service accounting.

Note: The classifier-specific statistics accounting feature is not supported for secondary input policy and hierarchical rate-limit policy.

The classifier-specific statistics accounting feature also enables the router to include only the IPv4 or IPv6 and user payload headers in policy octet counters of upstream and downstream packet statistics. The router excludes control overheads from policy octet counters.

Note: To exclude Dynamic Host Configuration Protocol version 6 (DHCPv6) or multicast packets from service accounting, you must explicitly configure a corresponding classifier group that matches the DHCPv6 or multicast packets and for which the classifier-specific statistics accounting feature is disabled.

The following sections describe sample computations of upstream and downstream packet statistics with the classifier-specific statistics accounting feature disabled and enabled:

Calculation of Upstream Packet Statistics for Service Accounting

This example describes how the upstream packet statistics to be used for service accounting is calculated for an input policy when the classifier-specific statistics accounting feature is disabled and enabled. You can consider an upstream packet that contains the following headers of the mentioned sizes:

When the classifier-specific statistics accounting feature is disabled, the upstream packet statistics is calculated by adding the sizes of all headers. So the upstream packet statistics for the sample packet is 56 bytes.

When the classifier-specific statistics accounting feature is enabled, the upstream packet statistics is calculated by adding only the sizes of the IP header and user payload. So the upstream packet statistics for the sample packet is 46 bytes.

Calculation of Downstream Packet Statistics for Service Accounting

This example describes how the downstream packet statistics to be used for service accounting is calculated for an output policy when the classifier-specific statistics accounting feature is disabled and enabled. You can consider a downstream packet that contains the following headers of the mentioned sizes:

When the classifier-specific statistics accounting feature is disabled, the downstream packet statistics is calculated by adding the sizes of all headers. So the downstream packet statistics for the sample packet is 84 bytes.

When the classifier-specific statistics accounting feature is enabled, the downstream packet statistics is calculated by adding only the sizes of the IP header and user payload. So the downstream packet statistics for the sample packet is 46 bytes.

Related Documentation