Bug ID 525633: Configurable behavior if PCRF returns unknown session ID in middle of session.

Last Modified: May 14, 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

Fixed In:
12.1.0, 12.0.0 HF1, 12.0.0, 11.6.0 HF6

Opened: May 28, 2015
Severity: 3-Major
Related AskF5 Article:
K02093894

Symptoms

If PEM sends CCR-U, and PCRF responds with CCA-U (PCRF lost session), PEM ignores the response and sends CCR-U.

Impact

Session remains for a long period of time with PCRF not acknowledging.

Conditions

PCRF lost session (reboot/failover) and responds to session update requests with unknown session ID.

Workaround

To enable PCRF can get the context back, it is recommended that you delete the session on the PEM end (configurable), and also recreate the same session (configurable). When PCRF indicates that the session ID unknown, set the following Sys db variable to TRUE to have PEM delete the session: tmm.pem.diameter.application.trigger.delete.onPeer.failure. To have PEM recreate the session, set the following Sys db variable to TRUE: tmm.pem.session.ppe.recreate.afterPeerFailure.

Fix Information

PCRF no longer returns unknown session ID in middle of session.

Behavior Change