ChrisJackel_103
Nov 30, 2007Nimbostratus
Persistence problem with multiple pools under one VIP
We have one VIP with two separate applications under it, with traffic segregated with an iRule like the following:
when HTTP_REQUEST {
if {[matchclass [string tolower [HTTP::uri]] starts_with $::myURL] } {
pool app1_http
} else {
pool app2_http
}
}
App1 is a set of Apache servers with no state information. App2 is dotNET and maintains state with the ASP state service, so persistence is less of an issue.
The persistence profile on the VIP is cookie insert.
Previously, there was very little crossover between the two applications. However, they do occasionally call objects from each other and when they do the BigIP cookie is overwritten. This is expected, the session information is a connection between the client and a node, and I can't see an easy way to maintain a session to two different nodes under the same VIP.
My understanding is that the 'match across virtual servers' and 'match across pools' wouldn't really apply in this case, since it is the same VIP throughout.
However, this is causing problems for app1, where it loses state as soon as it calls an image (or anything) that resides on a path under app2. They next time a request is made for app1 it establishes a new session and bad things happen.
It would take months of dev work to get the two applications into separate namespace and different VIPs. Any suggestions how I can maintain persistence within the same VIP to two applications at once?
We are running 9.3.1. Thanks in advance.