Forum Discussion

suhe_arie_17691's avatar
suhe_arie_17691
Icon for Nimbostratus rankNimbostratus
Nov 13, 2014

LTM default behavior on long lived tcp connection when server went down

Hi all,   We are planning to use F5 LTM to enhance the availability of the overall solution. In our application, the client uses long-lived TCP connection to connect to the server and once the con...
application delivery
availability
design
LTM
new to f5
tcp
Thomas_Schocka1's avatar
Thomas_Schocka1
Icon for Altocumulus rankAltocumulus
Nov 13, 2014

Hi Suhe Arie,

 

You can choose the action the F5 will undertake when "the backend server goes down". I believe you can set this through the 'Action On Service Down' setting on the pools.

 

In a standard loadbalancing virtual server scenario, there are a few usecases you need to take into account, then influence them to the best of the F5's possibilities:

 

  • the backend server resets the connection => the F5 will reset the client's frontend connection as well
  • the backend server cleanly terminates the connection => the F5 will cleanly terminate the client's frontend connection
  • the backend server no longer response => the connection will timeout, and upon timeout, the F5 will reset the client's frontend connection
  • the client cleanly closes the frontend connection => the F5 will cleanly close the backend connection
  • the client resets the frontend connection => the F5 will reset the backend connection

Kind regards,

 

Thomas Schockaert