top button
Flag Notify
    Connect to us
      Site Registration

Site Registration

Diameter : When a node sends transient failure as error code ?

+1 vote
1,013 views

A Diameter node sends an error message in Answer message. It uses different error code based on the category it falls.
I am not able to understand about transient failure category.

posted Mar 28, 2016 by Vikram Singh

Share this question
Facebook Share Button Twitter Share Button LinkedIn Share Button

3 Answers

+2 votes

One example: DIAMETER-OUT-OF-SPACE when a server (or any node) is out of memory or is unable to write to a socket due to flow control.

we have also seen some implementations sending DIAMETER-UNABLE-TO-COMPLY (5012) sometimes when an internal temporary error is encountered. Probably implementers were too lazy :)

answer Mar 28, 2016 by Rathnakumar Kayyar
+2 votes

Hi Vikram,

From RFC - 6733 section 7.1.4 describes ,Errors that fall within the transient failures category are used to inform a peer that the request could not be satisfied at the time it was received but MAY be able to satisfy the request in the future.

Below Errors are examples of Transient Failures
DIAMETER_AUTHENTICATION_REJECTED 4001
DIAMETER_OUT_OF_SPACE 4002
ELECTION_LOST 4003

Thanks

answer Mar 28, 2016 by Chinmoy Padhi
+1 vote

When a request received at a Diameter node can't be processed successfully for the time being, node responds to its peer with error code that comes under the category of transient failure. Chinmoy captured error codes that comes under the transient failure category.

Reference: https://tools.ietf.org/html/rfc3588

answer Mar 28, 2016 by Vimal Kumar Mishra
Similar Questions
+5 votes

I think any developer or tester can help me for this.

DIAMETER_UNABLE_TO_COMPLY 5012
This error is returned when a request is rejected for unspecified reasons. For sayings an unspecified reasons is very easy but as a tester if i want to verify this error code. How can i make it possible. How can i create this scenario?

For developer also it is difficult. Mostly all the scenario has been covered by RFC's. So for development as well as for testers this could be a challenge to generate/ test this error code. Can anybody share some words on this ?

0 votes

I know Diameter client can re-transmit the request message until it receives the answer message.
But what about when a Diameter node has sent answer message to the last received request from its peer and that's is not received but its peer. In this case, from Diameter client node transaction is not completed since it did not receive answer message but from other node point of view it has responded with answer and transaction is completed.

+4 votes

I am not able to understand the significance of "limited success" in a answer message and also want to know what a diameter node does when it receives this limited success within a answer message ?

...