Bug ID 840097: Improvement to MRF Bidirectional Persistence to instruct logic of default direction

Last Modified: Apr 17, 2024

Affected Product(s):
BIG-IP LTM(all modules)

Known Affected Versions:
15.1.0, 15.1.0.1, 15.1.0.2, 15.1.0.3, 15.1.0.4, 15.1.0.5, 15.1.1, 15.1.2, 15.1.2.1, 15.1.3, 15.1.3.1, 15.1.4, 15.1.4.1, 15.1.5, 15.1.5.1, 15.1.6, 15.1.6.1, 15.1.7, 15.1.8, 15.1.8.1, 15.1.8.2, 15.1.9, 15.1.9.1, 15.1.10, 15.1.10.2, 15.1.10.3, 15.1.10.4

Fixed In:
16.0.0

Opened: Oct 17, 2019

Severity: 4-Minor

Symptoms

MRF Bidirectional Persistence makes assumptions when determining the direction to forward a message that matches a persistence entry. For some systems, the algorithm used forwards the message to the wrong endpoint.

Impact

Messages from the server or an alternate server are not identified as needing to be forwarded to the client. Instead they are incorrectly forwarded to back to the server.

Conditions

-- Using MRF Bidirectional Persistence. -- The system is attempting to forward a message that matches a persistence entry.

Workaround

None. This is an improvement.

Fix Information

A new iRule command has been added to enable you to specify the direction of travel for the message if a persistence record is found.

Behavior Change

Guides & references

K10134038: F5 Bug Tracker Filter Names and Tips