Meaning of Session Persistence

Hi Frank,

 

 

Thanks for the additional info. If the traffic is encrypted through the LTM virtual server, there isn't much LTM can do to break up the application "requests" and send them to different pool members. ie, OneConnect or other attempts at breaking up the connections wouldn't really help as LTM cannot inspect the application traffic.

 

 

If you can use SSL session ID persistence you would have persistence throughout the SSL session and avoid pinning one client to one pool member forever. A new load balancing decision would be made each time LTM sees an SSL session ID which is not already mapped to a pool member. This wouldn't make a big difference though if the clients aren't opening new connections.

 

 

To move connections off of a pool member you want to do maintenance on, you could set the pool's action on service down to reset or reselect. You'd then want to make the monitor fail to trigger the action on service down action.

 

 

Aaron