Forum Discussion
NimbostratusCOOKIE persistance with geographically seperate LTM pairs
I have a GTM with geographically seperate LTM pairs. I am looking at how to read the origianly COOKIE persistance was set in the first pair when the user is passed to the second pair of LTMs. We are using the same POOL names and nodes at both locations with Round Robin on the GTM. Please help
4 Replies
- Kevin_Stewart
Employee
Having identical VIP/pool/node names on both boxes means the BIGipServer cookie is going to look the same. I can maybe think of two options:
-
Change the name of the persistence cookie on each device (inside the cookie persistence profile).
-
Set a separate cookie via iRule that indicates the original site.
With both options, check the cookie on each HTTP request.
-
- Kevin_Stewart
Gotcha. So did you say the VIP name was the same too?
Geoff_Fallin_28Yes... One GTM with round robin to the LTMs 2 geographically seperate LTM pairs VIP, POOL are named the same
Looking for the persistance that was set via COOKIE on the first LTM to be used when the user is redirected to the other LTM so that the same backend node is used based on the cookie if a cookie exists on the end users session
- Kevin_Stewart
Well, given that the pool and nodes have the same names, the cookie names should also be the same. I've tested this locally and one BIG-IP will accept and use another's BIGipServer persistence cookie. Cookie persistence has to be enabled for both. I'm also assuming that both VIPs answer to the same resolved name. The persistence cookie is host-based, so that would be important. Can you verify whether you're seeing the initial Set-Cookie from the first VIP and if the client is sending it to the second VIP?
