I changed Idle Timeout form 300 secs to a bigger value mainly followed below steps , but when traffic is following through F5 , user is seeing timeout in around 5 mins when they check directly from Pool member it is more than 5 mins.
What wrong I am doing ? How can I validate this ?
Creating a new protocol profile that uses a different timeout value
Note: For BIG-IP 11.5.0 and later versions, clicking Advanced is no longer necessary.
The virtual server now uses the new idle timeout setting.
Hi @Subrun if you take a verbose tcpdump capture w/ the F5 flags enabled, you'll be able to see the reset reason on the packets in the capture, if it is the big-ip that is resetting it and not an upstream devices that has shorter timers.
My understanding is that keep alive should be shorter. So if the client in indeed still connected, a response to keep alive extends the amount of time remaining until idle timeout.
If an application is enterprise grade and developed by a 3rd party, they usually have guidance for integration with app delivery controllers like F5. They should be able to provide guidance on what values to set on the Virtual Server config for the app.