Last Modified: Apr 28, 2025
Affected Product(s):
BIG-IP LTM
Known Affected Versions:
11.4.1, 11.5.0, 11.5.1, 11.5.1 HF1, 11.5.1 HF2, 11.5.1 HF3, 11.5.1 HF4, 11.5.1 HF5, 11.5.1 HF6, 11.5.1 HF7, 11.5.1 HF8, 11.5.1 HF9, 11.5.1 HF10, 11.5.1 HF11, 11.5.2, 11.5.2 HF1, 11.5.3, 11.5.3 HF1, 11.5.3 HF2, 11.5.4, 11.5.4 HF1, 11.5.4 HF2, 11.5.4 HF3, 11.5.4 HF4, 11.5.5, 11.5.6, 11.5.7, 11.5.8, 11.5.9, 11.5.10, 11.6.0, 11.6.0 HF1, 11.6.0 HF2, 11.6.0 HF3, 11.6.0 HF4, 11.6.0 HF5, 11.6.0 HF6, 11.6.0 HF7, 11.6.0 HF8, 11.6.1, 11.6.1 HF1, 11.6.1 HF2, 11.6.2, 11.6.2 HF1, 11.6.3, 11.6.3.1, 11.6.3.2, 11.6.3.3, 11.6.3.4, 11.6.4, 11.6.5, 11.6.5.1, 11.6.5.2, 11.6.5.3, 12.0.0, 12.0.0 HF1, 12.0.0 HF2, 12.0.0 HF3, 12.0.0 HF4
Fixed In:
12.1.0
Opened: Jan 21, 2015 Severity: 3-Major
When a virtual server is configured with fallback persistence, which looks up information from a session table (e.g., source address persistence) and the cookie is associated with an iRule that performs cookie insert, periodically TMM uses the default cookie name instead of the cookie name set in the iRule.
The cookie inserted by TMM will switch between the configured cookie name and the default cookie name (e.g., BIGip<cookie_name><pool_name>Server). Persistence may fail to work correctly when the persist iRule command overrides from cookie to hash-cookie persistence.
- Fallback persistence configured. - Using 'persist cookie insert' with custom cookie name in iRule.
There is no workaround at this time.
Persistence now works correctly when overridden via the persist iRule command.
When inserting a persistence cookie via an iRule, the TMM now remembers the persistence cookie details. The system uses those details for persistence in later HTTP requests/responses, rather than defaulting to the information within the cookie persistence profile.