Bug ID 1632209: Monitors with service port checking should not be used with wildcard pool members

Last Modified: Feb 11, 2025

Affected Product(s):
BIG_IP_NEXT(VE/HW) TMOS(all modules)

Known Affected Versions:
20.3.0

Opened: Aug 21, 2024

Severity: 2-Critical

Symptoms

Certain monitor types like HTTP, TCP, HTTPS, etc are NOT allowed to be used with a wildcard pool member, as they require a specific port to check and a wildcard pool member does not have a specific port.

Impact

Monitor will show pool member as down, won't be able to pass traffic to it.

Conditions

Using a monitor that requires a service port with a pool that has a wildcard pool member, or a pool member with a port of 0.

Workaround

Consider using an ICMP monitor instead.

Fix Information

None

Behavior Change

Guides & references

K10134038: F5 Bug Tracker Filter Names and Tips