Last Modified: Nov 15, 2019
See more info
Known Affected Versions:
13.1.0, 220.127.116.11, 18.104.22.168, 22.214.171.124, 126.96.36.199, 188.8.131.52, 184.108.40.206, 220.127.116.11, 18.104.22.168, 13.1.1, 22.214.171.124, 126.96.36.199, 188.8.131.52, 184.108.40.206, 220.127.116.11, 13.1.3, 18.104.22.168, 22.214.171.124
Opened: Jul 17, 2017
When FQDN names in FQDN nodes are resolved to actual IP addresses, and the BIG-IP creates ephemeral nodes for those, ephemeral nodes are created in the /Common partition even if the FQDN nodes themselves are created in their respective custom partitions. For example, an FQDN node is created in a partition say Partition1, the ephemeral nodes get created in /Common, while the template node remains in Partition1. Despite the Ephemeral Nodes being created in the /Common partition, the Ephemeral Pool Members which reference these Nodes appear as members of their respective Pools in their respective partitions.
FQDN ephemeral nodes are created in the /Common partition so that they can be referenced by FQDN template nodes and FQDN ephemeral pool members from any partition. This behavior is intentional to support multi-tenancy, where multiple FQDN template nodes in different partitions may resolve to the same physical IP address (thereby allowing the several FQDN template nodes to resolve to the same physical ephemeral node).
FQDN nodes are configured in a custom (non-/Common) partition.
The location of FQDN ephemerals has changed. In previous versions: FQDN ephemerals are in the partition where the FQDN template node was defined. In this version: FQDN ephemerals are in '/Common' partition, regardless of where the FQDN template node was defined.