Last Modified: Sep 13, 2023
Known Affected Versions:
184.108.40.206, 220.127.116.11, 12.1.6, 18.104.22.168, 22.214.171.124, 126.96.36.199, 13.1.4, 188.8.131.52, 13.1.5, 184.108.40.206, 220.127.116.11, 18.104.22.168, 22.214.171.124, 126.96.36.199, 188.8.131.52, 15.1.1, 15.1.2, 184.108.40.206, 15.1.3, 220.127.116.11, 15.1.4, 18.104.22.168, 15.1.5, 22.214.171.124, 15.1.6, 126.96.36.199, 15.1.7, 15.1.8, 188.8.131.52, 184.108.40.206, 16.0.0, 220.127.116.11, 16.0.1, 18.104.22.168, 22.214.171.124, 16.1.0, 16.1.1, 16.1.2, 126.96.36.199, 188.8.131.52, 16.1.3, 184.108.40.206, 220.127.116.11, 18.104.22.168, 22.214.171.124, 126.96.36.199
17.1.0, 16.1.4, 15.1.9
Opened: Nov 23, 2020 Severity: 3-Major
If an FQDN template node is configured with "autopopulate enabled" and the FQDN name resolves to multiple IP addresses, multiple FQDN ephemeral nodes will be created. If the FQDN template node is then deleted, the associated FQDN ephemeral nodes (sharing the same FQDN name) will not be deleted as expected.
Unused FQDN ephemeral nodes may remain in the active configuration. -- Since is it not possible to delete an FQDN template node if there are any FQDN template pool members referring to that node, it is not possible for any FQDN ephemeral pool members to remain when the steps that lead to this issue occur. -- Since traffic can only be passed to FQDN ephemeral pool members, the existence of the unused FQDN ephemeral nodes does not lead to traffic being passed to such nodes.
This may occur under the following conditions: -- An FQDN template node is configured with "autopopulate enabled" -- The configured DNS server resolves the FQDN name to multiple IP addresses -- You are running an Affected Version of BIG-IP, or an Engineering Hotfix based on a non-Affected Version of BIG-IP which contains a fix for ID 722230 This issue does not occur if only one FQDN ephemeral node is created for the associated FQDN template node.
It is possible to work around this issue by one of the following methods: -- Manually deleting the remaining FQDN ephemeral nodes using the "tmsh" command-line interface (CLI) (Note that this is normally not possible. It is possible to manually delete an FQDN ephemeral node only if the corresponding FQDN template node no longer exists.) -- Restarting BIG-IP (for example, using the command "bigstart restart")