Bug ID 2368565: TMM connects to read-only DB causing NAT operation failures

Last Modified: Oct 16, 2026

Affected Product(s):
BIG_IP_NEXT(BNK) BNK(all modules)

Fixed In:
2.4.0, 2.3.3, 2.2.4

Opened: Jul 01, 2026

Severity: 3-Major

Symptoms

After restart, TMM re-established its connection to the DSSM database pod but connected to the replica instead of the primary. This misconnection caused session APIs to fail, which in turn caused configured NAT operations to fail.

Impact

Because the TMM is connected to READONLY DB, the data sent to Redis DB will not be saved.

Conditions

TMM should be connected to sentinel based redis connection with NAT traffic enabled.

Workaround

None

Fix Information

Fixed code to perform a Redis DB role check after establishing the connection.

Behavior Change

Guides & references

K10134038: F5 Bug Tracker Filter Names and Tips