cookie insert persist not working
Howdy,
I've got a pool of 4 JVMs (same IP, different port if that might be relevant) and am trying to use cookie insertion for the session persistence. This is principally because the connections are coming from any 1 of 5 standalone 8900's, which in turn have been load balanced by a standard 8900 HA pair. As such, stateful persistence mechanism would be instantly useless, as there is no guarentee which of the 2nd level of 8900's will receive the request. There is also an even high level of GTM potentially moving connections between two entire DC's each containing this architecture with a common end destination server farm.
My understanding is that the cookie insertion mechanism is totally stateless as the cookie value includes the ip and port to use, so there's no need for any session data to be held on any system, so any correctly configured LTM can always handle the request.
However... this is apparently not happening. In a sample of the logs on the server I can see the cookie is coming back in just fine:
2012-09-11 11:33:17 GET /service/userActivityHistory.app - '6012748' /service/userActivityHistory.app?command=userActivityHistoryResponse&alertId=3193244&hexUserID=303030303030303835333837383139&fromUserDetails=false&ruleID=10727&contextSiteId=UNKNOWN 200 'FB3416D24D5AEACD7BDD48240A74863' 10.3.8.2 'siteIdSelection=UNKNOWN; JSESSIONID=FB3416D24D5ADCD7BDD48240A74863; WT_FPC=id=72.15.129.210-4099525184.30213996:lv=1333023181739:ss=1333023181739; SESSION_ID=SMS_P1_0531::d2c92e24df4dc7347136ca83c8c74418; INTERNAL_USER=true; Identifier-Internal-SSO=PID,USERDOMAIN01\602748:2ynYDMzVImtMLaTng8knt/; t2_service_persist=222109962.37663.0000'
and the virtual servers are set up right:
profile persist t2_service_persist_cookie_pr {
defaults from cookie
mode cookie
cookie mode insert
cookie name "t2_service_persist"
cookie expiration immediate
}
virtual t2_service_apache_to_apps_85_vs {
pool t2_service_pool
destination 10.20.30.20:85
ip protocol 6
persist t2_service_persist_cookie_pr
profiles {
http {}
tcp-lan-optimized {}
}
vlans vlan123 enable
}
yet periodically the user will be sent to a different server and, not being known, get 302'd to a login page. Throughout this though the cookie value NEVER changes. it's always exactly the same, as it should be, yet is what... just being completely ignored?
Any clues?
Thanks
Chris