Bug ID 2223665: When sdag.shuffle.table is non-zero on a clustered tenant, tmm may not go ready-for-world

Last Modified: Oct 16, 2026

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

Known Affected Versions:
17.1.0, 17.1.0.1, 17.1.0.2, 17.1.0.3, 17.1.1, 17.1.1.1, 17.1.1.2, 17.1.1.3, 17.1.1.4, 17.1.2, 17.1.2.1, 17.1.2.2, 17.1.3, 17.1.3.1, 17.1.3.2, 17.1.3.4, 17.1.3.5, 17.1.3.6, 17.5.0, 17.5.1, 17.5.1.2, 17.5.1.3, 17.5.1.4, 17.5.1.5, 17.5.1.6, 17.5.1.8, 17.5.1.9, 17.5.1.10, 21.0.0, 21.0.0.1, 21.0.0.2, 21.0.0.3

Fixed In:
21.1.0

Opened: Feb 13, 2026

Severity: 4-Minor

Symptoms

A tenant may not pass traffic after a reboot or a re-deploy if the sdag.shuffle.table db var is set to a non-default value. The following command tmctl -d blade tmm/ready_for_world_stat the value is "not_ready = dag_transition"

Impact

Tmm may not go ready-for-world.

Conditions

Cluster platform. sdag.shuffle.table is changed from the default (0).

Workaround

Set sdag.shuffle.table back to zero and restart tmm.

Fix Information

Changing sdag.shuffle.table no longer causes tmm to be not ready for world after a restart.

Behavior Change

Guides & references

K10134038: F5 Bug Tracker Filter Names and Tips