Forum Discussion
Scooter_42218
Oct 31, 2011Nimbostratus
Action on service down + Persistence
My company has run into stability issues with a specific application during a server outage. The environment is overbuilt by 10x (planned rollout later this year) and they shouldn't have problems whe...
Matt_85761
Mar 01, 2012Nimbostratus
Thanks to the US choosing a totally absurd date format, I'm not sure if this is a really old post, was it 01 November or 11 January?
Anyway this may help... There's a good techtip on the behavior of this setting at https://devcentral.f5.com/Tutorials/TechTips/tabid/63/articleType/ArticleView/articleId/179/LTM-Action-on-Service-Down.aspx
None (default)
LTM will continue to send data on established connections as long as client is sending and server is responding. Connection management / recovery / cleanup is via standard TCP mechanics for both clientside and serverside flows.
Use "None" if you don't want LTM to intervene in managing either side of the connection. Useful if your servers may not be accepting new connections, but should be allowed to continue servicing existing connections when marked DOWN. Also supports custom monitoring designed to support connection bleeding and other non-standard state management schemes.
Matt
Recent Discussions
Related Content
DevCentral Quicklinks
* 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
Discover DevCentral Connects