Bug ID 710221: Ephemeral node stays Unavailable on 'standby' BIG-IP system after a forced-offline FQDN node is re-enabled

Last Modified: May 29, 2024

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

Known Affected Versions:,,,,, 12.1.4,, 12.1.5,,,, 12.1.6, 13.1.0,,,,,,,,, 13.1.1, 14.0.0,,

Fixed In:

Opened: Mar 14, 2018

Severity: 2-Critical

Related Article: K67352313


In an high availability (HA) configuration where an FQDN template-node on the 'active' unit is 'Force Offline', and the configuration is synchronized to the 'standby' unit, upon 'Enable' on that FQDN template-node in the 'active' unit (and the configuration is synchronized to the 'standby' unit), the ephemeral nodes associated with that FQDN template node remain Unavailable on the 'standby' unit.


The ephemerals on the 'standby' unit remain unavailable, even though the associated FQDN template node is 'available'. However, as no traffic is routed to the 'standby' unit, traffic is unaffected. Upon transition from 'standby' to' active', the ephemeral nodes will be refreshed and traffic should continue.


HA configuration is configured with 'active' sync. -- FQDN template-node is configured. -- After ephemeral nodes are refreshed on the 'active' unit, it transitions to the 'standby' unit. -- The FQDN template node on the (new-'active') unit is 'Force Offline' by the user. -- The user explicitly 'Enable' that FQDN template node on the 'active' unit.


You can use either of these configuration options to prevent this issue from occurring: -- Select 'Disabled' (rather than 'Force Offline') for the FQDN template node on the 'active' unit. -- Configure the node without using FQDN.

Fix Information

Upon 'Force Offline' and then 'Enable' for an FQDN template node on an 'active' unit in an high availability (HA) configuration, the ephemerals on the 'standby' unit will reflect the re-enabled status based on the associated FQDN template-node on the 'active' unit.

Behavior Change

Guides & references

K10134038: F5 Bug Tracker Filter Names and Tips