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

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