Cisco ASR 9000 Series Configuration Manual page 71

Configuring Authentication, Authorization, and Accounting Functions
of the service and any associated counters. This feature is the Service Accounting feature. Service accounting
records are consolidated accounting records that represent the collection of features that make up a service as
part of a subscriber session.
Service accounting starts when a subscriber session comes up with a service enabled on it. This can happen
through a dynamic template applied through a control policy, through access-accept (AA) messages when
the session is authorized, or through a change of authorization (CoA), when a new service is applied on a
subscriber session. Service accounting stops either when the session is terminated, or a service is removed
from the session through CoA, or some other event that deactivates the service. Start records have no counters;
interim and stop records with QoS counters are generated when service accounting is enabled for QoS. Interim
accounting records can be generated, in between start and stop accounting, as an option with a pre-defined
periodic interval. When the interim period is zero, interim accounting records are not created. Different interim
intervals are based on every service for each session. Service accounting is enabled on each template, based
on the configuration.
The policy-map associated to a dynamic template can be edited to change the service parameters. However,
Note
this does not update the accounting records. Therefore, to generate all the accounting records accurately,
it is recommended that a new service with all the required service parameters be created and associated
to the new service, through a CoA.
For service accounting, statistics for ingress and egress QoS policies, which are applied under each service
for a given subscriber, may need to be reported as part of the accounting interim and stop records. For each
service, these QoS counters can be reported as part of the accounting records:
• BytesIn — Aggregate of bytes matching all classes of the ingress QoS policy for the service minus the
policer drops.
• PacketsIn — Aggregate of packets matching all classes of the ingress QoS policy for the service minus
the policer drops.
• BytesOut — Aggregate of bytes matching all classes of the egress QoS policy for the service minus the
queuing drops.
• PacketsOut — Aggregate of packets matching all classes of the egress QoS policy for the service minus
the queuing drops
Dynamic template features that support accounting statistic collection and require that their statistics be
reported in the AAA service accounting records can enable accounting statistics on their features using the
newly-introduced optional acct-stats configuration option. This option is not available for the features that
do not support statistic collection. By default, QoS accounting statistics are disabled to optimize performance.
Note The QoS counters for each direction is reported only if a QoS policy is applied for that service in the given
direction. For example, if a service does not have an ingress policy applied, BytesIn and PacketsIn counters
are reported as being 0.
Pre-requisites
• Subscriber accounting, the parent accounting record for service accounting, must be configured to enable
the service accounting feature to work.
OL-28375-03
Cisco ASR 9000 Series Aggregation Services Router Broadband Network Gateway Configuration Guide, Release
Service Accounting
4.3.x
59