Forum Discussion

Subrun's avatar
Subrun
Icon for Cirrostratus rankCirrostratus
Jun 22, 2023

Idle Timeout not reflecting when Changed from Default 300 secs.

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 P...
application delivery
whisperer's avatar
whisperer
Icon for MVP rankMVP

You may want to review the following article:

https://my.f5.com/manage/s/article/K13004262

Also, note that many times firewalls will also have a default 300s timeout. So also make sure any other network device in the path has been amended in terms of its timeout config.

 

Subrun's avatar
Subrun
Icon for Cirrostratus rankCirrostratus
Jun 22, 2023

whisperer 

My Keep Alive Interval - is higher than Idle Timeout , since idle time out should trigger before

  • JRahm's avatar
    JRahm
    Icon for Admin rankAdmin
    Jun 22, 2023

    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.

  • whisperer's avatar
    whisperer
    Icon for MVP rankMVP
    Jun 24, 2023

    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.