Last Modified: Sep 13, 2023
Affected Product(s):
BIG-IP PEM
Known Affected Versions:
11.6.1, 11.6.2, 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.1.0 HF1, 12.0.0 HF2, 12.1.0 HF2, 12.0.0 HF3, 12.0.0 HF4, 12.1.1 HF1, 12.1.1 HF2, 12.1.2 HF1, 12.1.2 HF2, 12.1.0, 12.1.1, 12.1.2, 12.1.3, 12.1.3.1, 13.0.0, 13.0.0 HF1, 13.0.0 HF2, 13.0.0 HF3, 13.1.0, 13.1.0.1, 13.1.0.2, 13.1.0.3
Fixed In:
14.0.0, 13.1.0.4, 13.0.1, 12.1.3.2
Opened: Nov 28, 2017 Severity: 2-Critical
If a PEM Diameter flow is not fully created, for example suspended by an iRule, the sweeper may encounter a tmm crash.
The tmm restarts and all flows reset. Traffic disrupted while tmm restarts.
-- PEM Diameter flow not fully created. -- The flow is suspended by an iRule. -- There is a CMP state change (likely) or a manual cluster-mirror change (less likely) while the flow is suspended.
None.
The PEM diameter flow is now created in such a way to prevent any crash by the sweeper.