Last Modified: Apr 28, 2025
Affected Product(s):
BIG-IP GTM, LTM
Known Affected Versions:
11.2.1, 11.3.0, 11.4.0, 11.4.1, 11.5.0, 11.5.1, 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, 11.5.2 HF1, 11.5.3, 11.5.3 HF1, 11.5.3 HF2
Fixed In:
11.6.0, 11.5.4, 11.4.1 HF2, 11.3.0 HF9, 11.2.1 HF11
Opened: Nov 07, 2013 Severity: 2-Critical Related Article:
K15698
If big3d loses its connection to MCPD and cannot reconnect immediately, big3d retries too often and re-uses timer IDs incorrectly. This might result in a core dump with either SIGABRT or SIGSEV. One way this can happen is that while processing very large configs, the mcpd process does not respond to queries from the big3d process.
big3d core errors.
A large configuration file (for example, larger than 10 MB) or a very busy MCPD/control plane.
This issue has no workaround at this time.
Very large configuration files (for example, larger than 10 MB) or a very busy MCPD/control plane no longer causes big3d core errors.