Bug ID 548114: RAR for already deleted session returns RAA with 5012 error code

Last Modified: Mar 21, 2019

Bug Tracker

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

Known Affected Versions:
11.6.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.6.1, 11.6.1 HF1, 11.6.1 HF2, 11.6.2, 11.6.2 HF1, 11.6.3, 11.6.3.1, 11.6.3.2, 11.6.3.3, 11.6.3.4, 11.6.4, 12.0.0

Fixed In:
12.1.0, 12.0.0 HF1

Opened: Sep 24, 2015
Severity: 3-Major

Symptoms

Session already deleted forcefully by PEM, but when PCRF sends RAR with the same session ID then PEM responds with RAA with error code 5012 (unable to comply) instead of 5002(unknown session ID)

Impact

PCRF still think session exists giving wrong signal to PCRF

Conditions

Session Deleted when Gx connection down and tmm.pem.session.endpointDeleteResponse and tmm.pem.session.FinalUsageRecord set to low value to trigger forced delete.

Workaround

Make sure tmm.pem.session.endpointDeleteResponse is set to high value to make sure session not deleted if Gx connection is down for a short period of time

Fix Information

Issue is fixed now. PEM will send RAA with 5002 error code for forcefully deleted session

Behavior Change