For more information regarding the security incident at F5, the actions we are taking to address it, and our ongoing efforts to protect our customers, click here.

Forum Discussion

JG's avatar
JG
Icon for Cumulonimbus rankCumulonimbus
May 03, 2014

Persistence cookies set by different, chained BIG-IP devices: How are they handled?

Example situation: A user access goes through two chained LTM devices (the first on v11.3.0, the second on v10.2.4), both virtual servers (in Partiton A and Partiton B respectively) each setting its ...
application delivery
availability
design
performance
security
TMOS
Scott_Hopkins_8's avatar
Scott_Hopkins_8
Icon for Nimbostratus rankNimbostratus
May 05, 2014

The main issue we ran into with standard cookie persistence is using the same pool name on both sets of chained devices. We had problems with them overwriting each other.

Format is: 

BIGipServerPoolName=9999999999.99999.0000

To solve this, we just put a prefix on one of the pools. (We call the pairs, ecom and internal, so the ecom unit gets 'e-' on all of it's Virtual Server and Pool objects).

Edited to correct cookie name