Best Way to do Cookie Persistence here?

Posted By Michael Yates on 04/27/2010 08:14 AM

 

I believe that you are trying to replace the default behavior of the F5 Persistence Cookie and compensate for Pool Member failures with an iRule. You shouldn't have to do either since those features are available through Virtual Server and Pool setup options.

 

 

Use Default Cookie Behavior (Tracks the Pool and Pool Member selected by whatever Load Balancing Method is configured - Round Robin, Least Connections (Node), Least Connections (Member), etc):

 

HTTP Cookie Insert: Specifies that the system inserts server information, in the form of a cookie, into the header of the server response. This is the default setting.

 

 

If Pool Member Fails:

 

Set Pool setting "Action On Service Down" to "Reselect".

 

 

This should give you the behavior that you are looking for and decrease the setup complexity.

 

 

Michael - in this case, the separate pools have shared resources - ie, pool 1 has 3 servers but all 3 depend on a certain java resource. I need pool persistency, but not node persistency. So, I'm not compensating for pool member failure...something else does that for us...I'm compensating for complete pool failure. For instance, if you get sent to pool 1, you need to stay in pool 1. If pool 1 doesn't have any active nodes, now it's time to find a different pool.