I have a doubt in Failover and Fallback mechanisms present under DIAMETER.

Question

Failover and Fallback procedures we know very well.

Suppose initial message was supposed to send to primary peer, but peer went down and message has been forwarded to Secondary peer i.e. Failover. Now suppose if Primary Peer has come up and according to DIAMETER theory the message should go to primary peer. So the next message will be Update message. Which will have the same session id which was used with the initial message.

Now my doubt is how the primary peer will recognize the session-id of update message. Because it has no info for that session. The session was created with the secondary peer.

Comments

Hi Hiteshwar,
                      Can you explain me how to did this and what you changed in code . Please explain me i will implement same ...

Answer 1

If your server is stateful the next message will have to include a Destination-Host AVP which will prevent the issue you described.

It is probably a better idea to share the session states between all your servers anyway.

Comments

I got your point but i am partially disagree with the solution because the same thing can be happen in case of failover and if destination host AVP's are present in the messages then these feature has no point to be there.