Cisco Cisco ASR 5000
AAA Server Group Configuration Mode Commands
radius accounting rp ▀
Command Line Interface Reference, StarOS Release 18 ▄
183
trigger-event { active-handoff | active-start-param-change | active-stop }
active-start-param-change
: Enabled
active-stop
: Disabled
Configures the events for which a RADIUS event is generated for accounting as one of the following:
active-handoff
: Disables a single R-P event (and therefore a RADIUS accounting event) when an
Active PCF-to-PFC Handoff occurs. Instead, two R-P events occur (one for the Connection Setup,
and the second for the Active-Start)
and the second for the Active-Start)
active-start-param-change
: Disables an R-P event (and therefore a RADIUS accounting event)
when an Active-Start is received from the PCF and there has been a parameter change.
active-stop
: Disables an R-P event (and therefore a RADIUS accounting event) when an Active-
Stop is received from the PCF.
Default:
active-handoff
: Disabled
Important:
This keyword has been obsoleted by the
trigger-policy
keyword. Note that if this command is
used, if the context configuration is displayed, radius accounting rp configuration is represented in terms of the trigger-
policy.
policy.
trigger-policy { airlink-usage [ counter-rollover ] | custom [ active-handoff |
active-start-param-change | active-stop ] | standard }
active-start-param-change | active-stop ] | standard }
Default:
airlink-usage
: Disabled
custom
:
active-handoff
= Disabled
active-start-param-change
= Disabled
active-stop
= Disabled
standard
: Enabled
Configures the overall accounting policy for R-P sessions as one of the following:
airlink-usage [ counter-rollover ]
: Specifies the use of Airlink-Usage RADIUS accounting
policy for R-P, which generates a start on Active-Starts, and a stop on Active-Stops.
If the
counter-rollover
option is enabled, the system generates a STOP/START pair before
input/output data octet counts (or input/output data packet counts) become larger than (2^32 - 1) in
value. This setting is used to guarantee that a 32-bit octet count in any STOP message has not
wrapped to larger than 2^32 thus ensuring the accuracy of the count. The system, may, at its
discretion, send the STOP/START pair at any time, so long as it does so before the 32-bit counter
has wrapped. Note that a STOP/START pair is never generated unless the subscriber RP session is
in the Active state, since octet/packet counts are not accumulated when in the Dormant state.
value. This setting is used to guarantee that a 32-bit octet count in any STOP message has not
wrapped to larger than 2^32 thus ensuring the accuracy of the count. The system, may, at its
discretion, send the STOP/START pair at any time, so long as it does so before the 32-bit counter
has wrapped. Note that a STOP/START pair is never generated unless the subscriber RP session is
in the Active state, since octet/packet counts are not accumulated when in the Dormant state.
custom
: Specifies the use of custom RADIUS accounting policy for R-P. The custom policy can
consist of the following:
active-handoff
: Enables a single R-P event (and therefore a RADIUS accounting event) when an
Active PCF-to-PFC Handoff occurs. Normally two R-P events will occur (one for the Connection
Setup, and the second for the Active-Start)
Setup, and the second for the Active-Start)
active-start-param-change
: Enables an R-P event (and therefore a RADIUS accounting event)
when an Active-Start is received from the PCF and there has been a parameter change.
Important:
Note that a custom trigger policy with only
active-start-param-
change
enabled is identical to the
standard
trigger-policy.