Bug ID 974501: Excessive memory usage by mirroring subsystem when remirroring

Last Modified: Sep 14, 2023

Affected Product(s):
BIG-IP TMOS(all modules)

Known Affected Versions:
13.1.0,,,,,,,,, 13.1.1,,,,, 13.1.3,,,,,,, 13.1.4,, 13.1.5,, 14.1.0,,,,,, 14.1.2,,,,,,,,, 14.1.3,, 14.1.4,,,,,,, 14.1.5,,,,,, 15.1.0,,,,,, 15.1.1, 15.1.2, 16.0.0,, 16.0.1,,

Fixed In:

Opened: Dec 16, 2020

Severity: 3-Major


Aggressive sweeper messages are seen in /var/log/ltm similar to the following: Dec 31 02:35:44 bigip1 warning tmm[25306]: 011e0002:4: sweeper_segment_cb_any: Aggressive mode /Common/default-eviction-policy activated (0) (global memory). (26227799/30854144 pages) In severe cases, tmm might restart and generate a core file due to an out of memory condition.


A portion of the connections handled by the BIG-IP might be dropped causing traffic interruption for those connections. In severe cases, tmm might restart causing traffic interruption.


The active BIG-IP has a large number of mirrored fastL4 connections. The active BIG-IP reconnects the statemirror connection to the standby BIG-IP. This is indicated by messages similar to the following in /var/log/ltm: Dec 31 02:35:37 bigip1 err tmm[25306]: 01340001:3: high availability (HA) Connection with peer for traffic-group /Common/traffic-group-1 established.



Fix Information

The memory utilization when remirroring fastL4 flows has been improved to allow remirroring to handle a larger number of connections.

Behavior Change

Guides & references

K10134038: F5 Bug Tracker Filter Names and Tips