Last Modified: Jan 13, 2020
See more info
Known Affected Versions:
12.1.0, 12.1.0 HF1, 12.1.0 HF2, 12.1.1, 12.1.1 HF1, 12.1.1 HF2, 12.1.2, 12.1.2 HF1, 12.1.2 HF2, 12.1.3, 22.214.171.124, 126.96.36.199, 188.8.131.52, 184.108.40.206, 220.127.116.11, 18.104.22.168, 13.0.0, 13.0.0 HF1, 13.0.0 HF2, 13.0.0 HF3, 13.0.1
Opened: Apr 20, 2017
Related AskF5 Article: K80024155
Mirroring persistence records may cause a Traffic Management Microkernel (TMM) memory leak. As a result of this issue, you may encounter one or more of the following symptoms: -- The tmsh show /sys memory command indicates that TMM memory usage increases over time. -- The TMM process generates a core file to the /shared/core directory. -- The BIG-IP system generates a SIGSEGV fault message in the /var/log/tmm log file.
Traffic is disrupted while the TMM process produces a core file and restarts. Systems configured as part of a HA device group may fail over to a peer device.
-- Mirroring enabled on virtual server and/or persistence profile. -- Persistence used. -- Another error condition exists, such as high availability (HA) channel down or no mirroring address configured.
To work around this issue, you can disable the Mirror Persistence option for the persistence profiles or make sure the mirroring channel is properly configured and operational. For information about troubleshooting the mirroring channel, refer to K54622241: Troubleshooting connection mirroring :: https://support.f5.com/csp/article/K54622241.
When HA mirroring is re-established, persist records will now be freed