Bug ID 474226: LB_FAILED may not be triggered if persistence member is down

Last Modified: Feb 13, 2019

Bug Tracker

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

Known Affected Versions:
11.0.0, 11.1.0, 11.2.0, 11.2.1, 11.3.0, 11.4.0, 11.4.1, 11.5.0, 11.5.1, 11.5.1 HF1, 11.5.1 HF10, 11.5.1 HF11, 11.5.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.6.0, 11.6.0 HF1, 11.6.0 HF2, 11.6.0 HF3, 11.6.0 HF4

Fixed In:
12.0.0, 11.6.0 HF5, 11.5.2, 11.4.1 HF9

Opened: Aug 02, 2014
Severity: 3-Major
Related AskF5 Article:
K15736

Symptoms

LB_FAILED may not be triggered if persistence member is down.

Impact

Cannot utilize LB::reselect command.

Conditions

This occurs when the following conditions exist: - Incoming connection has cookie matching persistence entry. - Persisted pool member has been marked down. - No other pool members are available.

Workaround

None.

Fix Information

LB_FAILED event is correctly triggered when persistence pool member is not available or offline.

Behavior Change