Forum Discussion
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 Pool member it is more than 5 mins.
What wrong I am doing ? How can I validate this ?
https://my.f5.com/manage/s/article/K7166
Creating a new protocol profile that uses a different timeout value
- Log in to the Configuration utility.
- Navigate to Local Traffic > Profiles.
- Click the Protocol tab.
- Click the relevant protocol profile. For example, FastL4.
- Click Create.
- Type a name for the new profile.
- For Parent Profile click the parent profile you want to use.
- For Idle Timeout, select the Custom check box.
- Type the new Idle Timeout value, in seconds.
- Click Finished.
- Navigate to Local Traffic > Virtual Servers.
- Click the virtual server to modify.
- For Configuration, click Advanced.
Note: For BIG-IP 11.5.0 and later versions, clicking Advanced is no longer necessary.
- In the Protocol Profile (Client) box, click the new profile you created.
- Click Update.
The virtual server now uses the new idle timeout setting.
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.
- SubrunCirrostratus
My Keep Alive Interval - is higher than Idle Timeout , since idle time out should trigger before
Recent Discussions
Related Content
* Getting Started on DevCentral
* Community Guidelines
* Community Terms of Use / EULA
* Community Ranking Explained
* Community Resources
* Contact the DevCentral Team
* Update MFA on account.f5.com