F5 is upgrading its customer support chat feature on My.F5.com. Chat support will be unavailable from 6am-10am PST on 1/20/26. Refer to K000159584 for details.

Forum Discussion

Krypto50_190970's avatar
Krypto50_190970
Icon for Nimbostratus rankNimbostratus
Mar 30, 2015

The answer I received from F5 support is that this is expected behavior. With CMP, TMM is now a single process with multiple threads. All memory is allocated to the TMM process which manages the memory for the different threads. I'm still unclear on why the memory shows up under TMM0.0. I don't have access to the system right now but here is what I can get from the qkview file.

 

list /sys db all-properties

 

sys db provision.tmmcount { default-value "0" scf-config "false" value "0" value-range "integer min:0 max:1024" } sys db provision.tmmcountactual { default-value "0" scf-config "false" value "4" value-range "integer min:0 max:1024" }

 

Hannes_Rapp's avatar
Hannes_Rapp
Icon for Nimbostratus rankNimbostratus
Mar 31, 2015
In case of vCMP, it makes sense, but do you have any vCMP Guests configured? For example, I have an F5 appliance (5250v) that has 8 vCMP Guests. When issuing the 'tmsh show sys tmm-info' command on any of the Guests systems, or the vCMP Host itself, I only see one TMM instance, even on the guests that are configured to use up 2 cores instead of 1. In case you have vCMP configuration in place, seeing the provisions only on TMM0.x is as expected - nothing to worry about. If you don't have any vCMP configuration in place, you do have something to be concerned about. Perhaps this arcticle will help you: https://support.f5.com/kb/en-us/products/big-ip_ltm/manuals/product/vcmp-administration-appliances-11-5-0/1.html. Cheers!