Bug ID 696382: Max in-progress sessions per client IP does not work correctly with Redirect ending

Last Modified: Oct 24, 2019

Bug Tracker

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

Known Affected Versions:
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, 13.0.0, 13.0.0 HF1, 13.0.0 HF2, 13.0.0 HF3, 13.0.1, 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.1, 13.1.1.2, 13.1.1.3, 13.1.1.4, 13.1.1.5, 13.1.3, 13.1.3.1, 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.4, 14.1.0.5, 14.1.0.6, 14.1.2, 14.1.2.1

Fixed In:
15.0.0

Opened: Nov 28, 2017
Severity: 3-Major

Symptoms

Once the 'Max In Progress Sessions Per Client IP' limit is reached, new sessions cannot be established even after manually deleting few sessions.

Impact

New sessions from client cannot be created after 'Max In Progress Sessions Per Client IP' limit is reached. End users may not be redirected to another internal or external URL.

Conditions

-- APM is licensed and provisioned. -- Per-session policy is created with Redirect ending agent. -- 'Close session after redirect' setting is not checked in Redirect Ending agent.

Workaround

If it's not required to keep the access session after redirecting to internal or external URL, check the 'Close session after redirect' setting in Redirect Ending agent of per-session policy.

Fix Information

New sessions are created from same client after manually deleting the existing access sessions once 'Max In Progress Sessions Per Client IP' limit is reached.

Behavior Change