Forum Discussion
tom_kleinpeter_
Nimbostratus
NimbostratusCookie hash persistence
I'm trying to keep the same user accounts going to the same members of a pool, even if they are accessing our site from different browsers and at different times of day (possibly hours apart). From r...
Your question is more a general BIG-IP persistence question, rather than an iRules question, but I'll try to give you some quick answers:
You are correct, all state for cookie persistence is maintained at the browser only.
A down node will cause the connection to be load balanced to an available node instead, as if no persistence token existed. The new node overwrite the persistence value in the existing persistence token with its own self-referencing value.
Changes to the pool membership will indeed cause changes in the resultant hash distribution.
Flow of events is correct, up to step 4, where I'm assuming you meant node A? Of course dependent on hash of Node A's cookie value resolving back to pool member NodeA, and on cookie expiry.
The LTM manual section on "passive cookie persistence" has the correct format for the initial cookie values you'd need to set for each user to hit a preferred node.
HTH
/d
