Last Modified: Apr 28, 2025
Affected Product(s):
BIG-IP (all modules)
Known Affected Versions:
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.6.0, 11.6.0 HF1, 11.6.0 HF2, 11.6.0 HF3, 11.6.0 HF4, 11.6.0 HF5
Fixed In:
12.0.0, 11.6.0 HF6, 11.5.3 HF2
Opened: Sep 15, 2014 Severity: 2-Critical
An error case may happen on BIG-IP if the following conditions are met: 1. There are two BIG-IPs configured as inter-cluster HA. 2. These two BIG-IPs are multi-blade chasis system. 3. Master record with independent subkeys is added to SessionDB. The observed symptom this that you can explicitly deleted such a master record, but auto expiration mechanisms (timeout & lifetime) will not work on it, and this record will live forever until it is explicitly deleted.
an inconsistent state between systems can cause persistence entries to never timeout. This will impact CGNAT records stored in SessionDB such as persistence records and PBA blocks.
Inter-chassis mirroring Chassis w/ multiple blades
None
None