Pool Persistence while buiilding the page

There are a couple of ways around this. Persistence of some form (cookie, IP, etc.) should do the trick as once the pool is chosen the client should stick there throughout their connection. That should be the simplest way to go about things. I'm surprised you tried cookie persistence with no luck. What did your config look like? What was the behavior? Were there any errors showing in the logs?

 

 

The other thing that is likely worth changing is the logic of the rule. If prod-pool-5001 is the default pool for all traffic that isn't going to the /Test page, then why include it in the iRule? Why not make it the default pool for the virtual, and leave it out of the iRule statement completely. This might make your persistence a little more ... persistent.

 

 

Colin