Configuring Route Failure

To configure the route failure, use the following sample configuration:

config 
   profile diameter-endpoint interface_name 
      name profile_name 
      internal-vip ip_address 
         route-failure deadtime deadtime_valueresult-code result_code_value threshold  number 
         route-failure result-code result_codes_value 
         route-failure threshold  threshold_number 
         route-failure recovery-threshold percent  recovery_threshold_percentage 
exit 

NOTES:

  • route-failure deadtime deadtime_valueresult-code result_code_value threshold number : Specify the duration in seconds for which the system keeps the route in the FAILED status. After the configured duration expires, the system changes the status to AVAILABLE . deadtime_value must be an integer in the range of 1–86400. The default value is 60.

  • route-failure result-code result_codes_value : Specify the answer messages that are to be considered as failures, in addition to the requests that time out.

    Note

    You can specify up to 16 result codes.

  • route-failure threshold threshold_number : Specify the number of errors that cause the FAILED status. The default value is 16.

    Note

    The error counter begins at zero. In a case of a good response, the error counter decrements or increments. This counter does not decrement below zero or increment above the configured threshold number.

  • route-failure recovery-threshold percent recovery_threshold_percentage : Specify the percentage value at which the failure counter is reset when provisionally changing the status from FAILED to AVAILABLE . For example, a failure counter of 16 caused the AVAILABLE status to change to FAILED status. After the configured deadtime expires, the status changes to AVAILABLE . If recovery_threshold_percentage is configured with 75 percent, the failure counter resets to 12, which is 75 percent of 16. The default value is 90.