Resetting Connections

Do you really want to do this? It will disrupt al the users on your application whenever a pool member comes up. How about using a load balancing option of least connections. This way, whenever a pool member comes up, it will get the vast majority of connections until everything is balanced out. If you really want to do this, I think it is more of an iControl thing. The iControl could poll the BIGIP to see if the number of active pool members increases. If it ever does, the iControl can force down all pool members and then bring them all back. This will reset all connections to the server side.

I do have the LB method set for least connections and that works fine for any "new" connections that occur after the pool member comes up but the existing member will hold on to the existing connections for long periods of time and that is where the problem lies. The traffic is stateless and not a big deal at the app level if I kill the connections. Is there an iRule method for killing connections for a particular member(s)? If I need to look down the iControl path that's fine... I was just hoping there was a way to handle this with an iRule. Thanks again.

iRules are meant to affect the particular event that triggers them. It would be extremely difficult to create an iRule that would keep track of all connections to a particular pool member globally and I cannot think of a way to make an iRule reset a different connection than the one that triggered the iRule. iControl is your best bet.