Bug ID 434397: connection could be reset if a pool member changes to unavailable and then available again.

Last Modified: Oct 16, 2023

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

Known Affected Versions:
10.2.3, 10.2.4, 11.0.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.5.1 HF1, 11.6.1 HF1, 11.5.1 HF2, 11.6.1 HF2, 11.5.1 HF3, 11.5.1 HF4, 11.5.1 HF5, 11.5.1 HF6, 11.5.1 HF7, 11.5.1 HF8, 11.5.1 HF9, 11.5.1 HF10, 11.5.1 HF11, 11.5.2 HF1, 11.6.2 HF1, 11.5.3 HF1, 11.5.3 HF2, 11.5.4 HF1, 11.5.4 HF2, 11.5.4 HF3, 11.5.4 HF4, 11.1.0, 11.2.0, 11.2.1, 11.3.0, 11.4.0, 11.4.1

Fixed In:
11.5.0

Opened: Oct 17, 2013

Severity: 3-Major

Related Article: K14861

Symptoms

A connection could be reset with 'no pool member available' as reason while there is still capacity in low-priority pool.

Impact

a connection may get reset

Conditions

a pool with 1) priority group set 2) connection limit set A pool member with 1) connection limit reached 2) becomes unavailable and available again immediately All other poolmember with same or high priority has no more capacity but there are capacity in lower priority group. pool has min_activemember set to 1

Workaround

raise min_active member to 2

Fix Information

Resets do not continue to occur if there is still capacity in low priority pool member.

Behavior Change

Guides & references

K10134038: F5 Bug Tracker Filter Names and Tips