Bug ID 422554: Lack of detail for why TMM does not become Ready For World

Last Modified: Sep 13, 2023

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

Known Affected Versions:
11.4.1, 11.5.1, 11.5.2, 11.5.3, 11.5.4, 11.5.5, 11.5.6, 11.5.7, 11.5.8, 11.5.9, 11.5.10, 11.6.0, 11.6.1, 11.6.2, 11.6.3,,,,, 11.6.4, 11.6.5,,,, 12.1.0 HF1, 12.1.0 HF2, 12.1.1 HF1, 12.1.1 HF2, 12.1.2 HF1, 12.1.2 HF2

Fixed In:
12.0.0, 11.4.1 HF9

Opened: Jun 04, 2013

Severity: 3-Major


TMM may fail to achieve ready-for-world status (as shown in the HA Status table) due to a number of possible reasons. Currently, there is no direct logging of the specific reason that TMM fails to achieve ready-for-world status.


Diagnosing situations where TMM does not become Ready-For-World requires understanding the requirements/dependencies for TMM to become Ready-For-World, and examining indirect logged data to confirm which dependency failed in each observed case.


TMM ready-for-world condition (as shown in the HA Status table) fails, and the HA group member fails to become active and to begin passing traffic.



Fix Information

The tmm/ready_for_world_stat tmstat table now list the components upon which TMM depends to become Ready For World, and indicates whether each is currently in a 'ready' versus 'not_ready' state. For example: # tmctl -d blade tmm/ready_for_world_stat name ready not_ready ---- -------------------------------------------------- --------- tmm0 platform_msg,shared_random,cmp_mpi,dag_transition,

Behavior Change

Guides & references

K10134038: F5 Bug Tracker Filter Names and Tips