Load Balancing Web Proxy Servers

Hi agvelegol,

 

 

Since you are load balancing Web Proxy Servers I wonder if you are going for too aggressive of a profile setup. The Layer 4 Performance Profiles are associated with a FastL4 Protocol Profile (Client). These have aggressive timeout values (TCP Close Timeout 5 seconds) for high speed "fast in / fast out / close" instead of the default TCP Profile which is geared for a more persistent client interaction (TCP Timeout 5 minutes).

 

 

Your clients connections could be getting closed too fast, causing the need for a new connection to be opened which would translate to sluggish performance.

 

 

I would suggest changing to a "Standard" Type with a normal / default Protocol Profile (Client) of "tcp" and see if the performance improves. If you need to increase the timeout values you can create a custom TCP Profile and up the Idle Timeout values as needed.

 

 

For your concerns "Performance L4 rule (I need to do this as I need the VIP to not respond to the port if all pool members are down)" you can control several behaviors.

 

 

On the Pool, set the Action On Service Down to "Reselect". If a server fails, all clients will be re-load balanced to a different server in the pool. The default is "None" which would result in a hard failure and the user would have to manually restart the session and be re-load balanced.

 

 

For the "all pool members are down", you can create an iRule using the active_members command to sense the availability of the pool members and take whatever action you like if none are available (redirect, alternate pool of proxy servers, etc.).

 

 

Hope this helps.