Behavior for Multiple Failure Cause Code Configuration
If multiple status codes return one after another matches the failure handling profile, the following known behavior is observed:
-
Example—When retry count is configured and retransmit value is not configured.
config profile nf-client-failure nf-type smsf profile failure-handling FH5 service name type nsmsf-sms responsetimeout 1000 message type SmsfActivationReq status-code httpv2 500 retry 3 retransmit-interval 2000 action retry-and-ignore exit status-code httpv2 504 retry 2 retransmit-interval 2000 action retry-and-ignore end
For the example mentioned,
-
If AMF receives 500 response for the first try, then it performs a second retry.
-
In the second retry, if AMF gets 504 response, AMF tries twice.
-
When this retry count (for 504 response) is exhausted, AMF doesn't resume the retry count for first one (500 response).
-
The maximum retries depend on the maximum number of endpoints configured (primary, secondary, tertiary) or NRF discovered ones.
-
-
Example—When retry count and retransmit value are configured.
config profile nf-client-failure nf-type smsf profile failure-handling FH5 service name type nsmsf-sms responsetimeout 1000 message type SmsfActivationReq status-code httpv2 504 retransmit 3 retry 2 action retry-and-terminate end
For the example mentioned,
-
If both retransmit value and retry count are configured, retransmit happens first and then retry.
Retransmmission is done thrice and if it fails, retry to done for secondary endpoint.
If retry returns 504 response, retransmmission is done three times and if it fails, retry is done for tertiary endpoint.
NoteRetries are always done to another endpoint, while retransmmission is done always to same endpoint.
-