Bug ID 690294: New DIAMETER::persist keyword to set the timeout without changing key

Last Modified: Oct 16, 2019

Bug Tracker

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

Known Affected Versions:
13.1.0, 13.1.0.1, 13.1.0.2, 13.1.0.3, 13.1.0.4, 13.1.0.5, 13.1.0.6, 13.1.0.7, 13.1.0.8, 13.1.1, 13.1.1.1, 13.1.1.2, 13.1.1.3, 13.1.1.4, 13.1.1.5, 13.1.3, 13.1.3.1, 14.0.0, 14.0.0.1, 14.0.0.2, 14.0.0.3, 14.0.0.4, 14.0.0.5, 14.0.1, 14.1.0, 14.1.0.1, 14.1.0.2, 14.1.0.3, 14.1.0.4, 14.1.0.5, 14.1.0.6, 14.1.2, 14.1.2.1

Fixed In:
15.0.0

Opened: Oct 24, 2017
Severity: 3-Major

Symptoms

Setting the DIAMETER persistence key's timeout using DIAMETER::persist <new_key> <new_timeout> disables bidirectional persistence.

Impact

Disables bidirectional persistence. Persistence entry records only destination (not source) of the session.

Conditions

Setting the DIAMETER persistence key's timeout using DIAMETER::persist <new_key> <new_timeout>.

Workaround

None.

Fix Information

New keyword, DIAMETER::persist timeout <new_timeout> allows changing the timeout without changing the key.

Behavior Change

There is a new keyword, DIAMETER::persist timeout <new_timeout>, which supports changing the timeout without changing the key. Previously, if you changed the timeout, it disabled bidirectional persistence.