Forum Discussion
hooleylist
Nov 18, 2010Cirrostratus
Hi Chris,
It sounds like you could use an iRule which selects either the iPlanet pool or IIS pool based on the requested URI. You could set two different persistence cookies to ensure clients are persisted back to the same pool member.
when HTTP_REQUEST {
Check the requested URI
switch -glob [HTTP::uri] {
"/path1/* -
"/path2/* {
Request was for an IIS URI so select the pool and set a pool-specific cookie
pool iis_pool
persist cookie insert iis_persist 0
}
default {
Request was for an iPlanet URI so select the pool and set a pool-specific cookie
pool iplanet_pool
persist cookie insert iplanet_persist 0
}
}
}
Or you could use the default cookie insert profile with no custom name specified and then remove the persist commands from the iRule. LTM will handle the persistence automatically for you.
Make sure to use a OneConnect profile with cookie persistence or URI-based pool switching to ensure each HTTP request is parsed and load balanced/persisted to the correct pool and pool member. If you're using SNAT you can use the default OneConnect profile. If you're not using SNAT, then you can use a custom OneConnect profile with the source mask set to 255.255.255.255. This ensures that serverside connections are only re-used for one client IP and that the server logs accurately reflect the client IP address.
Aaron