Bug ID 507797: Persistence records are ignored during service-down-action reselect

Last Modified: Sep 29, 2022

Bug Tracker

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

Known Affected Versions:
16.1.0, 16.1.1, 16.1.2,,, 16.1.3,,

Opened: Feb 18, 2015
Severity: 4-Minor


When a pool member is marked down and a connection reselects a pool member, it will ignore any persistence entries while making the selection and not update the persistence records after the selection is made.


Connections that, due to persistence configuration, should utilize a single pool member may utilize more that one pool member.


A virtual server with a persistence profile utilizes a pool which has service-down-action set to reselect.


With some configurations, service-down-action drop might be a valid work-around.

Fix Information


Behavior Change