Last Modified: Jan 09, 2025
Affected Product(s):
BIG-IP LTM
Known Affected Versions:
15.1.0, 15.1.0.1, 15.1.0.2, 15.1.0.3, 15.1.0.4, 15.1.0.5, 15.1.1, 15.1.2, 15.1.2.1, 15.1.3, 15.1.3.1, 15.1.4, 15.1.4.1, 15.1.5, 15.1.5.1, 15.1.6, 15.1.6.1, 15.1.7, 15.1.8, 15.1.8.1, 15.1.8.2, 15.1.9, 15.1.9.1, 15.1.10, 15.1.10.2, 15.1.10.3, 15.1.10.4, 15.1.10.5, 15.1.10.6, 16.1.0, 16.1.1, 16.1.2, 16.1.2.1, 16.1.2.2, 16.1.3, 16.1.3.1, 16.1.3.2, 16.1.3.3, 16.1.3.4, 16.1.3.5, 16.1.4, 16.1.4.1, 16.1.4.2, 16.1.4.3, 16.1.5, 16.1.5.1, 16.1.5.2, 17.0.0, 17.0.0.1, 17.0.0.2, 17.1.0, 17.1.0.1, 17.1.0.2, 17.1.0.3, 17.1.1, 17.1.1.1, 17.1.1.2, 17.1.1.3, 17.1.1.4, 17.1.2
Opened: Oct 23, 2024 Severity: 3-Major
If the BIG-IP configuration becomes corrupted in such a way that an ephemeral pool member exists with no corresponding FQDN template pool member, ephemeral node or FQDN template node, the dynconfd daemon may crash repeatedly.
The dynconfd daemon performs the action of resolving node FQDN names to IP addresses and creating ephemeral nodes and pool members with those addresses. When this issue occurs, dynconfd will be unable to resolve FQDN names in any existing FQDN template nodes (and FQDN template pool members) to their corresponding IP addresses. This can result in a lack of available pool members to process traffic.
This issue has only been encountered when corruption of the MCP database resulted in an ephemeral pool member existing with no corresponding FQDN template pool member, ephemeral node or FQDN template node. This is an invalid configuration which cannot be created through user action, and can only occur due to corruption of the MCP database. Such corruption is extremely rare, and the cause is not known.
To recover from the MCP database corruption, perform the actions described in the following F5 knowledge article: K13030: Forcing the mcpd process to reload the BIG-IP configuration
None