Bug ID 642068: PEM: Gx sessions will stay in marked_for_delete state if CCR-T timeout happens

Last Modified: Nov 07, 2022

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, 12.0.0, 12.0.0 HF1, 12.0.0 HF2, 12.0.0 HF3, 12.0.0 HF4, 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, 13.0.0, 13.0.0 HF1, 13.0.0 HF2, 13.0.0 HF3, 13.1.0, 13.1.0.1, 13.1.0.2, 13.1.0.3

Fixed In:
14.0.0, 13.1.0.4, 13.0.1, 12.1.3.2, 11.6.3

Opened: Jan 28, 2017
Severity: 3-Major

Symptoms

PEM sessions stay in the marked-for-delete state if CCR-T times out.

Impact

PEM sessions remain in the marked-for-delete state.

Conditions

This occurs if PCRF does not respond to CCR-T packets from the BIG-IP system during session termination.

Workaround

Configure the required timeout value in the sys db variable tmm.pem.session.timeout.endpointdeleteresponse. Note: The value must be greater than 0 (zero).

Fix Information

PEM sessions no longer stay in the marked-for-delete state if CCR-T times out.

Behavior Change