Bug ID 620788: FQDN pool created with existing FQDN node has RED status

Last Modified: Apr 10, 2019

Bug Tracker

Affected Product:  See more info
BIG-IP LTM(all modules)

Known Affected Versions:
11.6.0, 11.6.0 HF1, 11.6.0 HF2, 11.6.0 HF3, 11.6.0 HF4, 11.6.0 HF5, 11.6.0 HF6, 11.6.0 HF7, 11.6.0 HF8, 11.6.1, 11.6.1 HF1, 11.6.1 HF2, 11.6.2, 11.6.2 HF1, 11.6.3, 11.6.3.1, 11.6.3.2, 11.6.3.3, 11.6.3.4, 11.6.4, 12.0.0, 12.0.0 HF1, 12.0.0 HF2, 12.0.0 HF3, 12.0.0 HF4, 12.1.0, 12.1.0 HF1, 12.1.0 HF2, 12.1.1, 12.1.1 HF1, 12.1.1 HF2, 12.1.2, 12.1.2 HF1, 12.1.2 HF2

Fixed In:
13.0.0, 12.1.3

Opened: Oct 05, 2016
Severity: 3-Major
Related AskF5 Article:
K05232247

Symptoms

After creating an FQDN pool using an existing FQDN node, the pool has RED status.

Impact

Traffic will not pass in this pool.

Conditions

-- Existing FQDN node. -- Pool created with an existing FQDN node as a member.

Workaround

As a workaround, follow these steps: 1. Delete the existing FQDN node. 2. Create a new one. 3. Create a pool that includes the new FQDN node.

Fix Information

When creating an FQDN pool with an existing FQDN node, the pool status now reflects the actual monitor status.

Behavior Change