How LTM attaches information about node to JSessionsID ?
Hi all,
I'd like to ask whether you could explain me how LTM attaches information about node to JSessionsID used in cookie.
Introduction:
-
we have pool SRV_POOL: -SRV1 10.10.10.1 -SRV2 10.10.10.2 -SRV3 10.10.10.3 (new)
-
system creates cookies with JSessionID
ISSUE:
Recently we've added additional node to our pool. Issue occurs when request goes to last node and we get: C73AA9C0CC0F1045667015AF8F281AD4.node1 instead of node3
Logs:
Rule /Common/Node3Log : 10.7.255.251:16966: Used persistence record from cookie. Existing key? /Common/SRV_POOL 10.10.10.3 8080 Rule /Common/Node3Log : 10.7.255.251:16965: Request to .../soria/images/tooltipConnectorRight.gif with cookie: C73AA9C0CC0F1045667015AF8F281AD4.node1
Question:
Would you please explain me how LTM assignes nodes' information to JSession?
Thank you in advance, Mateusz