Bug ID 672988: MCP memory leak when performing incremental ConfigSync

Last Modified: Sep 13, 2023

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

Known Affected Versions:
11.4.0, 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.6.0, 11.6.1, 11.6.2, 11.6.3, 11.6.3.1, 11.6.3.2, 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, 13.0.0, 13.0.0 HF1, 13.0.0 HF2, 13.0.0 HF3, 13.0.1

Fixed In:
13.1.0, 12.1.3.1, 11.6.3.3, 11.5.7

Opened: Jul 07, 2017

Severity: 3-Major

Related Article: K03433341

Symptoms

MCP will leak memory when performing incremental ConfigSync operations to peers in its device group. The memory leak can be seen tmctl utility to watch the umem_alloc_80 cache over time. This leak occurs on the device that is sending the configuration.

Impact

MCP leaks a small amount of memory during each sync operation, and after an extended period of time, might eventually crash.

Conditions

A device group that has incremental sync enabled. In versions prior to BIG-IP v13.0.0, this is controlled by the 'Full Sync' checkbox. When unchecked, the system attempts to perform incremental sync operations.

Workaround

None.

Fix Information

MCPD no longer leaks when performing incremental ConfigSync operations.

Behavior Change

Guides & references

K10134038: F5 Bug Tracker Filter Names and Tips