Cisco Cisco Packet Data Gateway (PDG)
Diameter Overload Control
▀ Configuring Diameter Overload Control
▄ AAA Interface Administration and Reference, StarOS Release 19
52
Configuring Diameter Overload Control
The following sections provide the configuration commands to enable the Overload Control on Diameter Interfaces.
Defining Failure Handling Template
The failure handling template defines the action to be taken when the Diameter application encounters a failure
supposing a result-code failure, Tx-expiry or response-timeout. The application will take the action given by the
template.
supposing a result-code failure, Tx-expiry or response-timeout. The application will take the action given by the
template.
The commands illustrated below define the failure handling template.
configure
failure-handling-template template_name
end
Configuring Local Policy Parameters
The commands illustrated below configure the failure handling parameters. In support of the Diameter Overload Control
feature, the
feature, the
without-retry
keyword has been added to the failure handling template configuration to fallback to
local-policy without retrying the secondary PCRF server.
configure
failure-handling-template template_name
msg-type { any | authentication info request | authorization-request | check-
identity-request | credit-control-initial | credit-control-terminate | credit-control-
update | eap-request | eap-termination-request | notify-request | profile-update-request
| purge-ue-request | update-location-request | user-data-request } failure-type { any |
diabase-error | diameter result-code { any-error | result-code [ to end-result-code ] } |
diameter exp-result-code { any-error | result-code [ to end-result-code ] } | resp-
timeout | tx-expiry } action { continue [ local-fallback [ without-retry ] | retry-
server-on-event | send-ccrt-on-call-termination | without-retry ] | retry-and-terminate [
max-transmissions | without-term-req ] | terminate [ without-term-req ] }
identity-request | credit-control-initial | credit-control-terminate | credit-control-
update | eap-request | eap-termination-request | notify-request | profile-update-request
| purge-ue-request | update-location-request | user-data-request } failure-type { any |
diabase-error | diameter result-code { any-error | result-code [ to end-result-code ] } |
diameter exp-result-code { any-error | result-code [ to end-result-code ] } | resp-
timeout | tx-expiry } action { continue [ local-fallback [ without-retry ] | retry-
server-on-event | send-ccrt-on-call-termination | without-retry ] | retry-and-terminate [
max-transmissions | without-term-req ] | terminate [ without-term-req ] }
end
Notes:
without-retry
: This keyword specifies to continue the session without retrying the secondary PCRF server,
when in Assume Positive mode. By default, the Diameter message is retried to secondary PCRF before falling
back to local-policy.
back to local-policy.
This keyword is introduced to support Overload Control on Diameter interfaces such as Gx, S6b and SWm and
also to prevent network overload and outages. For more information on the commands used in this
configuration, refer to the Command Line Interface Reference guide.
configuration, refer to the Command Line Interface Reference guide.