Bug ID 711230: FQDN template nodes resolving to same IP address cannot be used in multiple non-Common partitions

Last Modified: Sep 13, 2023

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

Known Affected Versions:
11.6.0, 11.6.1, 11.6.2, 11.6.3, 11.6.3.1, 11.6.3.2, 11.6.3.3, 11.6.3.4, 11.6.4, 11.6.5, 11.6.5.1, 11.6.5.2, 11.6.5.3, 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, 12.1.3.1, 12.1.3.2, 12.1.3.3, 12.1.3.4, 12.1.3.5, 12.1.3.6, 12.1.3.7, 12.1.4, 12.1.4.1, 12.1.5, 12.1.5.1, 12.1.5.2, 12.1.5.3, 12.1.6, 13.0.0, 13.0.0 HF1, 13.0.0 HF2, 13.0.0 HF3, 13.0.1

Opened: Mar 21, 2018

Severity: 4-Minor

Symptoms

If an FQDN template node is created in a partition (not Common), then another FQDN template node is created in different partition but resolves to same IP address as the first FQDN template node, adding the second FQDN template node to a pool in the second partition will fail. An error message will be logged similar to the following: err mcpd[...]: 01020036:3: The requested Pool Member (/part1/pool_1 /part2/node2-192.168.172.246 80) was not found.

Impact

Cannot add FQDN node to pool.

Conditions

-- Creating FQDN template node in a partition other than Common. -- Creating another FQDN template node in different partition. -- Each node resolves to same IP address.

Workaround

Create the first FQDN template node in the Common partition. Then, when FQDN template nodes are created on a different partition, they use the ephemeral node in Common.

Fix Information

None

Behavior Change

Guides & references

K10134038: F5 Bug Tracker Filter Names and Tips