An LTM Specialist is investigating reports from users that SSH connections are being terminated unexpectedly. SSH connections are load balanced through a virtual server. The users experiencing this problem are running SQL queries that take upwards of 15 minutes to return with no screen output. The virtual server is standard with a pool associated and no other customizations.
What is causing the SSH connections to terminate?
The issue is likely caused by the TCP idle timeout. The BIG-IP system maintains connection information and has an idle timeout setting that specifies the length of time a connection can be idle before it is eligible for deletion. If the users' SSH sessions have no screen output while running long SQL queries, the connection may appear idle to the BIG-IP system, leading to its termination. Increasing the idle timeout setting can help prevent these unexpected disconnections.
B - Correct Idle Timeout The BIG-IP system maintains connection information including the idle time for ongoing sessions. The Idle Timeout setting in the TCP profile specifies the length of time that a connection is idle before the connection is eligible for deletion. If no traffic flow is detected within the idle session timeout, the BIG-IP system can delete the session. The default is 300 seconds. https://my.f5.com/manage/s/article/K13004262