Pool Member Logs

Hello, I think that this may be the answer you are looking for:

We can't know how many pool-member there was in the pool with those LOGs attached. It follows that he didn´t have any active pool-member because the pool was down.

When pool-member 10.16.1.22:80 was activated, the pool service was up.

The 4 messages of tmm (0-3) of the pool (services ), are of 4 TMM threads per processing core but in reference to the same pool.

================================================================

https://support.f5.com/csp/article/K14358

“TMM uses a multi-threaded architecture. Under the threaded model, the basic context of execution becomes a thread. The Clustered Multiprocessing (CMP) feature allows platforms that contain multiple CPUs to run to single TMM process for every CPU, and multiple TMM threads per processing core.

For example, starting in BIG-IP 11.3.0, the BIG-IP 8950 platform runs two TMM processes, one for each CPU. Each process creates four separate TMM threads.”