1 VIP < Multiple pools

We are doing this very same thing using the default cookie persistance profile. If you do not specify a cookie name, the BigIP creates it own name for each pool.

 

 

For example I use this iRule to direct traffic based on the root directory:

 

 

when HTTP_REQUEST {

 

switch [getfield [string tolower [HTTP::uri]] "/" 2] {

 

app1 { pool pool_app1 }

 

app2 { pool pool_app2 }

 

app3 { pool pool_app3}

 

}

 

}

 

 

After visiting all 3 pools in the same broswer session I get the following cookies:

 

BIGipServerpool_app1

 

BIGipServerpool_app2

 

BIGipServerpool_app3

 

 

The BigIP uses the value stored in the respective cookie to direct the traffic to the correct pool.

 

 

I also verified that this works when we create our own persistance profile of type cookie, parent = cookie, method = HTTP Cookie Insert, Cookie Name = and Expiration Session Cookie checked.

 

 

/Eric Grepps