Bug ID 716119: No error or ephemerals upon adding FQDN pool member with zero port to pool with wildcard monitor

Last Modified: Jan 05, 2021

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, 11.6.5, 11.6.5.1, 11.6.5.2, 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, 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, 13.1.0, 13.1.0.1, 13.1.0.2, 13.1.0.3, 13.1.0.4, 13.1.0.5, 13.1.0.6, 13.1.0.7, 13.1.0.8, 13.1.1, 13.1.1.2, 13.1.1.3, 13.1.1.4, 13.1.1.5, 13.1.3, 13.1.3.1, 13.1.3.2, 13.1.3.3, 13.1.3.4, 13.1.3.5, 14.0.0, 14.0.0.1, 14.0.0.2, 14.0.0.3, 14.0.0.4, 14.0.0.5, 14.0.1, 14.0.1.1, 14.1.0, 14.1.0.1, 14.1.0.2, 14.1.0.3, 14.1.0.5, 14.1.0.6, 14.1.2, 14.1.2.1, 14.1.2.2, 14.1.2.3, 14.1.2.4, 14.1.2.5, 14.1.2.6, 14.1.2.7, 14.1.2.8, 14.1.3, 14.1.3.1, 15.0.0, 15.0.1, 15.0.1.1, 15.0.1.2, 15.0.1.3, 15.0.1.4, 15.1.0, 15.1.0.1, 15.1.0.2, 15.1.0.3, 15.1.0.4, 15.1.0.5, 15.1.1, 15.1.2, 16.0.0, 16.0.0.1, 16.0.1

Opened: Apr 20, 2018
Severity: 4-Minor

Symptoms

Attempting to add a pool member with a statically-configured address and a zero port to a pool with a monitor configured for a wildcard destination fails with an error similar to: 01070622:3: The monitor /Common/http has a wildcard destination service and cannot be associated with a node that has a zero service. In contrast, adding an FQDN pool member with a zero port to a pool with a monitor configured for a wildcard destination appears to succeed with no error. However, ephemeral pool members are not created for the pool, and a message similar to the following will be logged to the ltm log file: err mcpd[6611]: 01070622:3: The monitor /Common/http has a wildcard destination service and cannot be associated with a node that has a zero service.

Impact

No FQDN ephemeral members will be added to the pool. If the FQDN template pool member is the only member of the pool, the pool will have no members and cannot pass traffic.

Conditions

This occurs if: -- The monitor assigned to the pool is configured with a wildcard destination, such as: ltm monitor http http { destination *:* } -- The pool member is added to the pool with a port of "0" or "any".

Workaround

Use one of the following methods to work around this issue: -- Configure the monitor to use a non-zero port, such as: ltm monitor http http_80 { destination *:http } -- Add the pool member to the pool with a non-zero port.

Fix Information

None

Behavior Change