Priority Group Activation

If I can expand on Cmbhatt's comments, forcing the user to break their persistence to one server in favor of another will BREAK their application session. There are very few commercial web applications out there that don't rely in some way on a session to track a user's movement through the application. If the application stores everything in a cookie (including authentication information), then you might be okay. But if that cookie (or header) is a session ID (PHPSESSIONID, ASPSESSIONID, CFID, JSESSIONID, etc.) that points to an in-memory session object on the server, then you will break the application and interrupt the user's experience. You're probably better off leaving existing users on the server. Many environments, including the BigIP, do allow some session mirroring capability, but it is hardly ever an easy option.

 

 

 

Kevin