Cisco Cisco Packet Data Gateway (PDG)
AAA Server Group Configuration Mode Commands
radius accounting ▀
Command Line Interface Reference, StarOS Release 17 ▄
167
Default: 10 minutes
Important:
This parameter should be set to allow enough time to remedy the issue that originally caused the
server’s state to be changed to “Down”. After the deadtime timer expires, the system returns the server’s state to
“Active” regardless of whether or not the issue has been fixed.
“Active” regardless of whether or not the issue has been fixed.
Important:
For a complete explanation of RADIUS server states, if you are using StarOS 12.3 or an earlier
release, refer to the RADIUS Server State Behavior appendix in the AAA and GTPP Interface Administration and
Reference. If you are using StarOS 14.0 or a later release, refer to the AAA Interface Administration and Reference.
Reference. If you are using StarOS 14.0 or a later release, refer to the AAA Interface Administration and Reference.
detect-dead-server { consecutive-failures consecutive_failures_count | keepalive
| response-timeout response_timeout_duration }
| response-timeout response_timeout_duration }
consecutive-failures consecutive_failures_count
: Specifies the number of consecutive failures,
for any AAA Manager, before a server’s state is changed from “Active” to “Down”.
consecutive_failures_count
must be an integer from 1 through 1000. Default: 4
keepalive
: Enables the AAA server alive-dead detect mechanism based on sending keepalive
authentication messages to all authentication servers. Default: disabled
response-timeout response_timeout_duration
: Specifies the number of seconds, for any AAA
Manager, to wait for a response to any message before a server’s state is changed from “Active” to “Down”.
response_timeout_duration
must be an integer from 1 through 65535.
Important:
If both
consecutive-failures
and
response-timeout
are configured, then both parameters
must be met before a server’s state is changed to “Down”.
Important:
The “Active” or “Down” state of a RADIUS server as defined by the system, is based on
accessibility and connectivity. For example, if the server is functional but the system has placed it into a “Down” state,
it could be the result of a connectivity problem. When a RADIUS server’s state is changed to “Down”, a trap is sent to
the management station and the deadtime timer is started.
it could be the result of a connectivity problem. When a RADIUS server’s state is changed to “Down”, a trap is sent to
the management station and the deadtime timer is started.
Important:
For a complete explanation of RADIUS server states, if you are using StarOS 12.3 or an earlier
release, refer to the RADIUS Server State Behavior appendix in the AAA and GTPP Interface Administration and
Reference. If you are using StarOS 14.0 or a later release, refer to the AAA Interface Administration and Reference.
Reference. If you are using StarOS 14.0 or a later release, refer to the AAA Interface Administration and Reference.
fire-and-forget
Enables RADIUS Fire-and-Forget accounting for the AAA group.
Default: Disabled
The request sent to the RADIUS accounting server configured under the AAA group with this keyword
configured will not expect a response from the server. If the request must be sent to more than one such type
of server, the acct-algorithm first-n configuration in the AAA group can be used.
Default: Disabled
The request sent to the RADIUS accounting server configured under the AAA group with this keyword
configured will not expect a response from the server. If the request must be sent to more than one such type
of server, the acct-algorithm first-n configuration in the AAA group can be used.
Important:
The Fire-and-Forget feature is supported on GGSN, HA, PDSN and P-GW.
Keepalive feature for server state detection is supported in conjunction since there is no waiting for
responses. Archiving in such a AAA group is not supported. If the server is down, the request is sent to the
next server in the group. If all the servers in the group are down, the request is deleted.
responses. Archiving in such a AAA group is not supported. If the server is down, the request is sent to the
next server in the group. If all the servers in the group are down, the request is deleted.