Cisco Cisco Packet Data Gateway (PDG)
Accounting Policy Configuration Mode Commands
rf ▀
Command Line Interface Reference, StarOS Release 18 ▄
245
rf
This command controls the reporting of subscriber traffic data for Rating Groups (RGs) based on the generation of
Interim Record (IR).
Interim Record (IR).
Product
GGSN
HSGW
P-GW
S-GW
SAEGW
Privilege
Administrator
Mode
Exec > Global Configuration > Context Configuration > Accounting Policy Configuration
configure > context context_name > policy accounting policy_name
Entering the above command sequence results in the following prompt:
[context_name]host_name(config-accounting-policy)#
Syntax
rf report-all-active-rgs
{ default | no } rf report-all-active-rgs
default | no
The default behavior is to disable traffic data reporting in Service Data Container (SDC) for all active Rating
Groups (RGs) whenever an interim is sent.
Groups (RGs) whenever an interim is sent.
report-all-active-rgs
This keyword enables to report the traffic data in the SDC for all the active RGs whenever an IR is sent. By
default, this feature is enabled.
default, this feature is enabled.
Usage
There are several change conditions where a partial Service Data Container (SDC) is not cut for a particular
RG but ACR-Interim is generated due to maximum change conditions. There are many triggers like time
limit, volume limit, etc., that will lead to maximum change condition. Because of this some RGs SDC may
not be generated for a longer period of time.
In releases prior to 18.0, when a Maximum Change Condition event was triggered, only those RGs that have
hit one of the Change Conditions that require a caching of data as opposed to cutting an IR, used to have their
data in the generated IR. In 18.0 and later releases, when the Maximum Change Condition happens, the
current Rf implementation is changed to make sure all RGs that have not been cached have a snapshot of
their usage taken.
RG but ACR-Interim is generated due to maximum change conditions. There are many triggers like time
limit, volume limit, etc., that will lead to maximum change condition. Because of this some RGs SDC may
not be generated for a longer period of time.
In releases prior to 18.0, when a Maximum Change Condition event was triggered, only those RGs that have
hit one of the Change Conditions that require a caching of data as opposed to cutting an IR, used to have their
data in the generated IR. In 18.0 and later releases, when the Maximum Change Condition happens, the
current Rf implementation is changed to make sure all RGs that have not been cached have a snapshot of
their usage taken.