For more information regarding the security incident at F5, the actions we are taking to address it, and our ongoing efforts to protect our customers, click here.

Forum Discussion

DevBabu_124276's avatar
DevBabu_124276
Icon for Nimbostratus rankNimbostratus
Jul 16, 2015

LTM tcp client profile does not set idle timeout to the configured value

Some, of the users waiting for report, reported that they are receiving timeout and do not get the report. I checked the connection table and found that some of the connections show idle timeout as d...
VernonWells's avatar
VernonWells
Icon for Employee rankEmployee
Jul 19, 2015

If you change the tcp profile, it will affect only new connections made after the change. Any existing connections will continue to use whatever tcp profile (and thus, idle timeout) was associated with the Virtual Server when the connection was initiated.

 

If you are certain that the connections in question were established after the change of tcp profile, and that you are using the same profile on both the client- and server-sides, then I recommend opening a case with F5 Support.