Disable (Only persistent or active connections allowed) a Pool member through a monitor in v9.x

That's right -- we have proven in tests that if a node is marked down by the monitor it won't gracefully drain out existing session, hence the hoop jumping exercise ;)

 

 

So Aaron, I have been playing with this all day and it appears that the questions has risen many times in the forums - there seems to be two main schools of thought in regard:

 

 

1. ECV Monitor + perl/iControl (many ready iControl apps available)

 

 

2. Driving the pool member status through an irule and query string as per Deb's example (http://devcentral.f5.com/Community/GroupDetails/tabid/1082223/asg/51/aft/26906/showtab/groupforums/Default.aspx)

 

 

Both methods seem to work in a rough and ready lab test although with the ECV Monitor script seems the more labour intensive of the two solutions to get working properly - thinking error handling and compatibility with future releases.

 

 

So I am tempted to go for the irule solution as it seems to offer the possibility of driving the pool member from an existing VIP directly from the target web servers - ultimately the target node would have to be manually disabled for maintenance so it makes little difference if the operator has to executes a binary that fires up an HTTP request to the VIP instead of changing the content of a file.

 

 

Thoughts?

 

 

Claud