Cisco Cisco ASR 5000
Accounting Policy Configuration Mode Commands
trigger-type ▀
Command Line Interface Reference, StarOS Release 18 ▄
251
gy-sdf-volume-limit { cache | immediate }
Enables the SDF volume-limit trigger for Rf-Gy interaction.
cache
: If this keyword option is configured then upon receipt of volume-limit event trigger from Gy, the
container record will be cached for reporting in a future transaction.
immediate
: If this keyword option is configured then upon receipt of volume-limit event trigger from Gy, Rf
will send out an interim record immediately.
+
Indicates that more than one of the keywords can be entered in a single command.
Usage
In Release 15.0 when time/volume quota on the Gy interface gets exhausted, Gy will trigger
SERVICE_DATA_VOLUME/TIME_LIMIT. Release 16.0 and beyond, this behavior is CLI controlled.
This CLI configuration will either enable PCEF to send an ACR-Interim immediately or cache the container
records for reporting in a future transaction. If there is no such configuration for that event-trigger, then the
ACR-Interims will be dropped.
When the subscriber disconnects while in Assume Positive mode, then the CLI configuration enables the
PCEF to send an ACR-Stop with PS-level change condition “Normal Release” and container level “Service
Specific Unit Limit”. The presence of the “Service Specific Unit Limit” change condition at the container
level indicates to the OFCS that data has gone unreported on Gy. The change-condition at container level is
only present if the keyword option
SERVICE_DATA_VOLUME/TIME_LIMIT. Release 16.0 and beyond, this behavior is CLI controlled.
This CLI configuration will either enable PCEF to send an ACR-Interim immediately or cache the container
records for reporting in a future transaction. If there is no such configuration for that event-trigger, then the
ACR-Interims will be dropped.
When the subscriber disconnects while in Assume Positive mode, then the CLI configuration enables the
PCEF to send an ACR-Stop with PS-level change condition “Normal Release” and container level “Service
Specific Unit Limit”. The presence of the “Service Specific Unit Limit” change condition at the container
level indicates to the OFCS that data has gone unreported on Gy. The change-condition at container level is
only present if the keyword option
gy-sdf-unit-limit
is configured.
The gateway provides a configuration option to enable/disable the functionality at the ACR level to control
which of the triggers are enabled – Service Specific Unit Limit, Service Data Volume Limit and Service Data
Time Limit. The gateway provides configuration options to control the various Rf messages triggered for
sync on this feature.
Gy Quota Update - Volume Limit - CLI options are:
which of the triggers are enabled – Service Specific Unit Limit, Service Data Volume Limit and Service Data
Time Limit. The gateway provides configuration options to control the various Rf messages triggered for
sync on this feature.
Gy Quota Update - Volume Limit - CLI options are:
Disabled
Enabled, container with SDF Volume limit queued and sent at next ACR trigger.
Enabled, container with SDF Volume limit created and ACR sent immediately with PS info level of
Volume Limit
Gy Quota Update – Validity Timer Expires - CLI options are:
Disabled
Enabled, container with SDF Time Limit queued and sent at next ACR trigger.
Enabled, container with SDF Time limit created and ACR sent immediately with PS info level of Time
Limit
Example
The following command specifies to send ACR-Interim message immediately when the time quota on the Gy
interface expires:
interface expires:
trigger-type gy-sdf-time-limit immediate