Bug ID 623509: Gx CCA with non-existent or non-pem policy does not trigger CCR-u reply

Last Modified: Oct 06, 2020

Bug Tracker

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

Known Affected Versions:
13.0.0, 13.0.0 HF1, 13.0.0 HF2, 13.0.0 HF3, 13.0.1

Fixed In:
13.1.0

Opened: Oct 19, 2016
Severity: 4-Minor

Symptoms

If Gx interface, from the PCRF, receives a CCA with non-existent or non-pem policy, a CCR-u with 'Unknown rule name' is not being sent back to PCRF.

Impact

CCR-u with 'unknown rule name' is not being send back to PCRF.

Conditions

By default, for any CCR with a CCA having non-existent or non-pem policy.

Workaround

Configure PCRF to send an existing policy on the BIG-IP system.

Fix Information

Set the sys db variable tmm.pem.session.policy.InstallUnknown to FALSE to receive CCR-u with result code UNKNOWN_RULE_NAME, otherwise there will be no CCR-u sent back.

Behavior Change

Before: If CCA with an unknown policy is received from Gx, the BIG-IP system replied with CCR-u with Result code set to UNKNOWN_RULE_NAME. Now: You can set a sys db variable tmm.pem.session.policy.InstallUnknown to FALSE to receive CCR-u with result code UNKNOWN_RULE_NAME. Otherwise, there will be no CCR-u sent back.