Bug ID 689343: Diameter persistence entries with bi-directional flag created with 10 sec timeout

Last Modified: Apr 19, 2021

Bug Tracker

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

Known Affected Versions:
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, 12.1.3.2, 12.1.3.3, 12.1.3.4, 12.1.3.5, 12.1.3.6, 12.1.3.7, 12.1.4, 12.1.4.1, 12.1.5, 12.1.5.1, 12.1.5.2, 12.1.5.3, 12.1.6, 13.0.0, 13.0.0 HF1, 13.0.0 HF2, 13.0.0 HF3, 13.0.1, 13.1.0, 13.1.0.1, 13.1.0.2, 13.1.0.3

Fixed In:
14.0.0, 13.1.0.4

Opened: Oct 18, 2017
Severity: 2-Critical

Symptoms

Diameter persistence entries have timeout value less than 10 seconds, although the configured persistence timeout is 120 seconds

Impact

The persist timeout is less than 10 seconds, thus subsequent requests will be dispatched to other pool member.

Conditions

When Diameter custom persistence "DIAMETER::persist key 1" bi-directional iRule is used.

Workaround

Don't use bi-directional persistence iRule. Use AVP persistence type with session-id as the persist key.

Fix Information

When the Diameter custom persistence iRule "DIAMETER::persist key 1" is used, the persist timeout value will be set correctly as configured.

Behavior Change