Last Modified: Oct 17, 2023
Affected Product(s):
BIG-IP LTM
Known Affected Versions:
11.4.1, 11.5.0, 11.5.1, 11.5.2, 11.5.3, 11.5.4, 11.5.5, 11.5.6, 11.5.7, 11.5.8, 11.5.9, 11.5.10, 11.6.0, 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, 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, 12.1.3.2, 12.1.3.3, 12.1.3.4, 12.1.3.5, 13.0.0, 13.0.0 HF1, 13.0.0 HF2, 13.0.0 HF3, 13.0.1, 13.1.0, 13.1.0.1, 13.1.0.2, 13.1.0.3, 13.1.0.4, 13.1.0.5, 13.1.0.6, 13.1.0.7, 13.1.0.8, 13.1.1
Fixed In:
14.0.0, 13.1.1.2, 12.1.3.6, 11.6.4
Opened: Jan 02, 2018 Severity: 3-Major Related Article:
K10870739
BIG-IP LTM policies may cause an mcpd process memory leak. As a result of this issue, you may encounter one or more of the following symptoms: -- Latency when configuring the BIG-IP system. -- Error messages logged in /var/log/ltm similar to the following example: 01140029:4: HA daemon_heartbeat mcpd fails action is restart. -- The mcpd process may generate a core file in the /var/core directory.
The mcpd process might run slower as memory is consumed, and can fail when all system memory is exhausted. Devices in a high availability (HA) configuration may experience a failover event.
This issue occurs when all of the following conditions are met: -- Your configuration includes one or more virtual servers with an associated BIG-IP LTM policy. -- The BIG-IP LTM policy has at least one rule. Note: Rules with actions or conditions can leak increased amounts of memory. -- You delete and add BIG-IP LTM policies that are associated with the virtual server. Note: This modification causes the memory leak to increase over time.
None.
The system now prevents MCP from leaking memory when attaching an LTM policy to a virtual server.