Last Modified: Oct 16, 2026
Affected Product(s):
BIG_IP_NEXT(BNK) BNK
Fixed In:
2.4.0, 2.3.4, 2.2.5
Opened: Jul 16, 2026 Severity: 2-Critical
When you create a pool with a pool member and a monitor, every TMM in a TMM pod sends status updates to the DSSM each time the pool member's state changes. This behavior can degrade performance, especially when many TMM pods contain multiple TMMs, causing the problem to scale rapidly.
Multiple TMM pods and TMMs writing to DSSM at the same time can create performance bottlenecks in the DSSM pod.
N/A
Increase the CPU allocation for the DSSM pod to prevent write operations from overloading it. Alternatively, reduce the number of TMM threads, TMM pods, or both.
Fixed the DSSM limits. DSSM now writes to a single TMM in a given TMM pod instead of writing to all TMMs.