Last Modified: Sep 13, 2023
Affected Product(s):
BIG-IP PEM
Known Affected Versions:
11.6.0, 11.6.1, 11.6.2, 11.6.3, 11.6.3.1, 11.6.3.2, 11.6.3.3, 11.6.3.4, 11.6.4, 11.6.5, 11.6.5.1, 11.6.5.2, 11.6.5.3, 12.0.0, 12.1.0 HF1, 12.1.0 HF2, 12.1.1 HF1, 12.1.1 HF2, 12.1.2 HF1, 12.1.2 HF2
Fixed In:
12.1.0, 12.0.0 HF1
Opened: Sep 24, 2015 Severity: 3-Major
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)
PCRF still think session exists giving wrong signal to PCRF
Session Deleted when Gx connection down and tmm.pem.session.endpointDeleteResponse and tmm.pem.session.FinalUsageRecord set to low value to trigger forced delete.
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
Issue is fixed now. PEM will send RAA with 5002 error code for forcefully deleted session