Last Modified: May 14, 2025
Affected Product(s):
BIG-IP LTM
Known Affected Versions:
15.1.4.1, 15.1.5, 15.1.5.1, 15.1.6, 15.1.6.1, 15.1.7, 15.1.8, 15.1.8.1, 15.1.8.2, 15.1.9, 15.1.9.1, 15.1.10, 15.1.10.2, 15.1.10.3, 15.1.10.4, 15.1.10.5, 15.1.10.6, 16.0.0, 16.0.0.1, 16.0.1, 16.0.1.1, 16.0.1.2, 16.1.2, 16.1.2.1, 16.1.2.2, 16.1.3, 16.1.3.1, 16.1.3.2, 16.1.3.3, 16.1.3.4, 16.1.3.5, 16.1.4, 16.1.4.1, 16.1.4.2, 16.1.4.3, 16.1.5, 16.1.5.1, 16.1.5.2
Opened: Feb 20, 2020 Severity: 2-Critical
Incoming packets are dropped, connections are dropped. "Aggressive mode sweeper" messages recorded in "ltm" log, such as: warning tmm[457]: 011e0003:3: Aggressive mode sweeper: /Common/default-eviction-policy (1cf1) (global memory) 99 Connections killed The output of the following command shows a value of 2.3G for "Alloc (bytes)": # tmsh show sys memory | grep -E "SubSystem|EB.Tree"
Dropping packets and connections impedes handling of network traffic. In extreme cases, the shortage of available TMM memory may trigger a greater disruption.
-- At least one virtual server has a clientssl profile configured to enable the TLS 1.3 protocol, along with the advanced option setting "0-RTT/Early Data with Anti-Replay". (In the Configuration Utility, the field in Profile Properties is "Data 0-RTT" and the value would be "Enabled with Anti-Replay".)
In the "clientssl" profile, set the TLS 1.3 option "Data 0-RTT" to "Disabled".
None