Forum Discussion
johnfilo_45702
Jul 21, 2010Nimbostratus
OK, just been reading up on "LTM - Action when service down" here - http://devcentral.f5.com/Tutorials/TechTips/tabid/63/articleType/ArticleView/articleId/179/LTM-Action-on-Service-Down.aspx
Does this feature give you the flexibility to take various actions depending on the string returned from the monitored page?
For example, lets say I defined 3 different status strings returned by the monitored page in the backend:
RUNNING - Normal operating server
MAINTENANCE - Server in maintenance mode so reselect another server from the pool, don't RST the client connection and send no new sessions or connections to this server. (assume active TCP connections can complete?)
DRAINING - Server will be placed in maintenance mode once all active sessions have cleared, so keep sending existing sessions to this server but don't allow any new sessions to be created.
RUNNING and MAINTENANCE are easy and I think "LTM - Action when service down" is perfect to help me do this.
The problem is once I have upgraded the server that was in MAINTENANCE and add it back to the pool, I would then need to place the other server into DRAINING so that existing sessions complete and die a natural death, whilst all new sessions get directed to the newly upgraded server.
Is this possible?