Configures failure
handling behavior in the event of a failure with the HSS peer service.
It also defines the action on various error codes on the Diameter
interface during authentication or session activities.
Privilege:
Security Administrator,
Administrator
Syntax
failure-handling { authentication-information-request | check-identity-request| notify-request | purge-ue-request | update-location-request } { diameter-result-code start_error_code [ to end_error_code ] | request-timeout } action { continue | retry-and-terminate | terminate }
no failure-handling { authentication-information-request | check-identity-request | notify-request | purge-ue-request | update-location-request } diameter-result-code start_error_code [ to end_error_code ]
default failure-handling { authentication-information-request | check-identity-request | notify-request | purge-ue-request | update-location-request } request-timeout
no
Removes the preconfigured
failure handling procedures for calls in an HSS peer service.
default
Sets the default action
for failure handling procedure for calls in an HSS peer service.
For default actions
on Diameter result/error codes see the Usage section below.
authentication-information-request
Configures the MME-HSS
service to handle the failures in an Auth-Information-Request message.
check-identity-request
Configures the MME-HSS
service to handle the failures in a Check-Identity-Information-Request
message.
notify-request
Configures the MME-HSS
service to handle the failures in a Notify-Request message.
purge-ue-request
Configures the MME-HSS
service to handle the failures in a Purge-UE-Request message.
update-location-request
Configures the HSS
peer service to handle the failures in an Update-Location-Request message.
diameter-result-code start_error_code [to end_error_code]
Configures the HSS
peer service to handle the failures for various request message
having specific single or range of Diameter result codes in a request
message.
start_error_code specifies
an individual error code for Diameter protocol as an integer from
3000 through 5999. This will be the starting of code if a range
of error codes is specified with the optional keyword to end_error_code.
to end_error_code is
used to specify a range of error codes to handle by this command. end_error_code specifies
the end error code for Diameter protocol as an integer from 3000
through 5999.
request-timeout
Configures the HSS
peer service to handle the failures for various request messages
if response to that message is not received before timeout duration
exhausted.
action { continue | retry-and-terminate |
terminate }
Specifies the action
to be taken on failure of any message as a policy for failure handling.
- continue: On
receipt of any error, the system allows the HSS peer service to
continue with the session procedure without any interruption.The continue option
for IMEI procedure on SGSN:For IMEI procedure
on SGSN, the continue
option performs the same function as the retry-and-terminate option, this
behaviour is changed for SGSN only. Configure the continue option
as follows:configure context <name> hss-peer-service <name> failure-handling check-identity-request request-timeout
action continue failure-handling check-identity-request diameter-result-code
<range1> to <range2> action continue failure-handling check-identity-request diameter-result-code
<range1> action continue exit exit exitBy configuring the continue option
as shown above, the timeout and error response requests will be
re-tried on a second peer (if the second peer is configured) and
the call procedure is continued.
- retry-and-terminate:
On receipt of any error, the system instructs the HSS peer service
to retry the procedure. The system will retry up to the configured
number of attempts and terminate the session/procedure
if it received a subsequent number of errors after retry attempts.
- terminate:
The system allows the HSS peer service to terminate the session
procedure without any retry attempt on the event of any failure.
Usage:
Use this command to
configure the failure handling behavior in the event of a communication
failure with the HSS peer service.
The following are the
default action for Diameter result codes:
- For all protocol error
codes 3000 to 3999, the default action is terminate. For all transient
error codes 4000, 4001, 4004 to 4180, and 4182 to 4999, the default
action is continue.
- For transient error
codes 4002, 4003, and 4181, the default action is retry.
- For error code 4001,
the default action is terminate.
- For permanent error
codes 5000 to 5999, the default action is terminate
Example:
The following command
will allow HSS peer service to continue if any failure in Auth-Information-Request
message occurred with Diameter error code
3050:
failure-handling authentication-information-request
diameter-result-code 3050 action continue