Bug ID 1644337: Redis connection must be included in the tmm liveness probe

Last Modified: Nov 29, 2025

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

Fixed In:
1.4.0

Opened: Sep 09, 2024

Severity: 2-Critical

Symptoms

Once the connection between Redis and TMM is lost, it is necessary to check the logs for session sync errors in the TMM logs.

Impact

TMM continues to accept and process requests even though there is no session sync between Redis and TMM. This could lead to inconsistent or incorrect processing of session data.

Conditions

To reproduce the issue, Redis can be shut down (set replica to 0), causing TMM to continuously try to reconnect to Redis.

Workaround

None

Fix Information

The Redis connection status has been included as part of the TMM liveness probe. If the connection fails and cannot be reestablished, the TMM is marked as unhealthy, and the TMM pod is deleted.

Behavior Change

Guides & references

K10134038: F5 Bug Tracker Filter Names and Tips