Forum Discussion
Brad_Parker
Sep 30, 2015Cirrus
The BigIP will only make a decision based on the name of the cookie configured in the persistence profile. By default that is BIGipServer, so it will only persist to the pool for which the connection is destined for. I would recommend changing the name of the cookie to something more specific to your organization and not leave it as the default "BIGip..." cookie. Gives a little to much info to the world, ;-).
- Ed_SummersSep 30, 2015NimbostratusThanks, Brad. Follow-up for clarification: For the default 'cookie' persistence profile, I believe the cookie name is BIGipServer, which is confirmed by viewing cookies in a browser session. Assuming both virtual servers use the default session 'cookie' profile. When the BIG-IP receives an HTTP request with two BigIP cookies, does it read the cookie that has the pool name for the virtual on which the request was received? I believe the answer is 'yes', but wanted to confirm. I'll try to lab it out also. As for your last statement, all I can do for now is tell you "I agree". :)