Alcatel-Lucent 7950 SR, System Management Manual

Page: 319 / 462

Event and Accounting Logs
7950 SR OS System Management Guide Page 319
Configurable Accounting Records
• XML Accounting Files for Service Accounting on page 319
XML
Accounting Files for Service
Accounting
The custom-record command in the config>log>accounting-policy context provide the flexibility
to reduce the volume of data generated, network operators can define the record that needs to be
collected. This can eliminate queues or selected counters within these queues that are not relevant
for billing.
Record headers including information such as service-ID, SAP-ID, etc., will always be generated.
Significant Change Only Reporting
Another way to decrease accounting messaging related to overhead is to include only “active”
objects in a periodical reporting. An “active object” in this context is an object which has seen a
“significant” change in corresponding counters. A significant change is defined in terms of a
cumulative value (the sum of all reference counters).
This concept is applicable to all methods used for gathering accounting information, such as an
XML file and RADIUS, as well as to all applications using accounting, such as service-acct.
Accounting records are reported at the periodical intervals. This periodic reporting is extended
with an internal filter which omits periodical updates for objects whose counter change
experienced lower changes than a defined (configurable) threshold.
Specific to RADIUS accounting the significant-change command does not affect ACCT-STOP
messages. ACCT-STOP messages will be always sent, regardless the amount of change of the
corresponding host.
For Application Assurance records, a significant change of 1 in any field of a customized record
(send a record if any field changed) is supported. When configured, if any statistic field records
activity, an accounting record containing all fields will be collected.