Last Modified: Sep 13, 2023
Known Affected Versions:
11.5.1 HF1, 11.5.1 HF2, 11.5.1 HF3, 11.5.1 HF4, 11.5.1 HF5, 11.5.1 HF6, 11.5.1 HF7, 11.5.1 HF8, 11.5.1 HF9, 11.5.1 HF10, 11.5.1 HF11, 11.5.2 HF1, 11.5.3 HF1, 11.5.3 HF2, 11.5.4 HF1, 11.5.4 HF2, 11.5.4 HF3, 11.5.4 HF4, 11.4.0, 11.4.1, 11.5.0, 11.5.1, 11.6.0, 11.6.1, 11.6.2, 11.6.3, 18.104.22.168, 22.214.171.124, 126.96.36.199, 188.8.131.52, 11.6.4, 11.6.5, 184.108.40.206, 220.127.116.11, 18.104.22.168, 12.1.0 HF1, 12.1.0 HF2, 12.1.1 HF1, 12.1.1 HF2, 12.1.2 HF1, 12.1.2 HF2
12.0.0, 11.6.0 HF4, 11.5.2, 11.4.1 HF6
Opened: Jun 23, 2014 Severity: 3-Major Related Article:
Related Article: K16000
Receiving several configuration synchronization (ConfigSync) requests, in a short period of time, may cause the mcpd process to exhaust memory resources, restart, and produce a core file. Note: The Automatic Sync feature can exacerbate this issue. The Automatic Sync feature is disabled by default. As a result of this issue, you may encounter one or more of the following symptoms: Performing a ConfigSync operation causes the BIG-IP system to experience a brief service interruption while the mcpd process restarts. If configured as part of a high availability (HA) group, the BIG-IP system fails over. The BIG-IP system generates an mcpd core file.
The BIG-IP system may experience a brief service interruption while the mcpd process restarts.
Receiving several configuration synchronization (ConfigSync) requests with a short interval.
Sync of a folder delete or create now will send an incremental sync if possible. Sync of a folder modify that changes the device group still will trigger a full load; this is necessary and does not indicate an issue.