Cisco Cisco Packet Data Gateway (PDG) トラブルシューティングガイド
AAA Server Group Configuration Mode Commands
radius accounting rp ▀
Cisco ASR 5000 Series Command Line Interface Reference ▄
OL-22947-02
: 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)
: 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.
: Disables an R-P event (and therefore a RADIUS accounting event) when an Active-
Stop is received from the PCF.
Default:
: Disabled
Important:
This keyword has been obsoleted by the
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.
Default:
: Disabled
:
= Disabled
= Disabled
= Disabled
: Enabled
Configures the overall accounting policy for R-P sessions as one of the following:
: 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
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.
: Specifies the use of custom RADIUS accounting policy for R-P. The custom policy can
consist of the following:
: 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)
: 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
enabled is identical to the
trigger-policy.
: Enables an R-P event (and therefore a RADIUS accounting event) when an Active-
Stop is received from the PCF.