Last Modified: Jan 16, 2024
Affected Product(s):
BIG-IP LTM
Known Affected Versions:
10.2.0, 10.2.1, 10.2.2, 10.2.3, 10.2.4, 11.0.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.5.1 HF1, 11.6.1 HF1, 11.5.1 HF2, 11.6.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 HF1, 11.6.2 HF1, 11.5.3 HF1, 11.5.3 HF2, 11.5.4 HF1, 11.5.4 HF2, 11.5.4 HF3, 11.5.4 HF4, 11.1.0, 11.2.0, 11.2.1, 11.3.0, 11.4.0, 11.4.1, 11.5.0, 11.5.1
Fixed In:
11.6.0, 11.5.2, 11.4.1 HF9, 10.2.4 HF12
Opened: Apr 01, 2014 Severity: 3-Major Related Article:
K15410
Virtual server with iRule and no default pool marked offline if one of the iRule pools is forced offline. Although the virtual server is marked offline it can actually reach available pool members from another pool by a multi-pool picker iRule.
During maintainability, a pool (that could not be targeted at the moment) marked offline (pool members) could bring the whole virtual server offline.
- Virtual server with no default iRule. - iRule with if-else that picks a different pool for each condition. - Force offline the pool members for one of the pools.
Mark the pool members as disabled, instead of offline: modify ltm pool pool_http members modify { 10.2.202.5:http { session user-disabled } }
N/A