smp_86112
Jan 15, 2010Cirrostratus
Persistent Connection Forwarded to Wrong Pool Member
v9.3.1HF8
(I haven't really studied this behavior closely before, so please go light on me.)
It seems we have identified an issue where HTTP clients with a BigIP Cookie are being forwarded to the wrong pool member. Upon review of the logs, we see the same BigIP cookie header value on both pool members. The clients are behind a proxy server, so we suspect that multiple client sessions are being pipelined into a single TCP session between the LTM and the proxy. The VIP is pretty vanilla, and so is the persistence profile which I have included below for reference.
How do you troubleshoot something like this? The GUI doesn't show the persistence records, so I can't confirm from that perspective. Is there a different type of persistence I could use that would prevent this problem from happening at all? What other mitigation strategies are out there?
virtual app {
destination :80
ip protocol tcp
profile default_http tcp
persist cookie
pool app
}
profile persist cookie {
mode cookie
cookie mode insert
cookie expiration 0d
cookie hash offset 0
cookie hash length 0
cookie name none
rule none
mirror disable
timeout 0
}
pool app {
lb method member predictive
min active members 1
monitor all dtac.deere.com
member :
member :}