Forcing the use of a new pool and new member based on the current pool and member

I believe so.

 

You might want to take a look at the following. Keep in mind that this is more untested psudeo code. It's simply to get you thinking about how it can be used to pin down. Of course there are other briliant minds out there that probably have a better answer and I hope they do.

 

 

 
 when HTTP_REQUEST {  
 switch -glob [HTTP::uri] { 
 "*/cf/*" {  
 switch $pin { 
 "10.77.177.88" { node 10.77.177.78 80 } 
 "10.77.177.89" { node 10.77.177.79 80 } 
 "10.77.177.90" { node 10.77.177.80 80 } 
 default { pool Pool-A } 
 } 
 } 
 "*/hf/*"  
 {  
 switch $pin { 
 "10.77.177.78" { node 10.77.177.88 80 } 
 "10.77.177.79" { node 10.77.177.89 80 } 
 "10.77.177.80" { node 10.77.177.90 80 } 
 default { pool Pool-B } 
 } 
 } 
 } 
 when LB_SELECTED { 
 set pin[LB::server addr] 
 } 
 

 

 

hope this helps

 

CB