Forum Discussion
CAS exchange tcp 60001 expires before source persistence timeout
Hi,
we are loadbalancing CAS Exchange services (135, 60000, 60001, 443, 25) using source address persistence timeout 7200 seconds (LTM 11.2.1)
Nevertheless, our Exchange workmates say most connections ends before that time.
We are wondering if maybe we should also modify tcp idle timeout profile (300 seconds by default)
Best Regards
3 Replies
- nathe
Cirrocumulus
Victor,
The Exchange iApp does indeed set a TCP idle timeout of 7200secs so I would recommend you do change it from the default.
Rgds
N
- Victor_129910
Nimbostratus
Hi,
sorry, we are not using Exchange iApp, we are using our own config, but for your answer I guess we should modify TCP idle timeout also to 7200.
Many thanks.
- nathe
Cirrocumulus
I was using the iApp as the recommended config. Hopefully changing this will sort your issue.
Help guide the future of your DevCentral Community!
What tools do you use to collaborate? (1min - anonymous)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