Hi,
I thought, by disabling the node (not marking down), the LTM will do just exactly what we are trying to do. The document says so.
Below is the extract from the BIG IP documentation:-
==========
Enabling and disabling a node
A node must be enabled in order to accept traffic. When a node is disabled,
the LTM system allows existing connections to time out or end normally. In
this case, the node can accept new connections only if the connections
belong to an existing persistence session. (In this way a disabled node
differs from a node that is set to down. The down node allows existing
connections to time out, but accepts no new connections.)
==========
Only thing is, if we want to DISABLE the node remotely ( via some script), how do we do it?
To mark the node DOWN is simple, we can have a custom http-ecv health monitor, which will act a a remote control to mark the node DOWN. But as the document suggests, by marking the node down , we will also loose the persistent sessions. To save these persistent sessions & have a graceful removal of the node from the pool, we have to DISABLE the node.
Any one knows any method to disable the node in F5 via some script ( or any F5 monitor or so) ??
regds,
Lee..since1976.