Bug ID 567238: Value of sysdb var tmm.pem.spm.maxsessionlimit

Last Modified: Sep 13, 2023

Affected Product(s):
BIG-IP Install/Upgrade, PEM(all modules)

Known Affected Versions:
11.2.1, 11.3.0, 11.4.1, 11.5.0, 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.0.0, 12.0.0 HF1, 12.1.0 HF1, 12.0.0 HF2, 12.1.0 HF2, 12.0.0 HF3, 12.0.0 HF4, 12.1.1 HF1, 12.1.1 HF2, 12.1.2 HF1, 12.1.2 HF2

Fixed In:

Opened: Jan 12, 2016

Severity: 1-Blocking


PEM was incorrectly doubling the value of the sysdb var tmm.pem.spm.maxsessionlimit.


You will notice that the maximum number of sessions supported by PEM is now half of what it used to be.


This will impact only those users that have modified the sysdb var tmm.pem.spm.maxsessionlimit prior to version 12.1.0 and then upgraded to 12.1.0 or beyond.



Fix Information

We now honor the value specified in the sysdb var tmm.pem.spm.maxsessionlimit. If you have modified the value for this sysdb var prior to 12.1.0, you will need to fix this value in your config. The sysdb should now be set to the desired value(instead of half of the desired value). If you use BIG-IP with htsplit disabled, it is recommended that you reduce this value, since there are more tmms with htsplit disabled.

Behavior Change

Guides & references

K10134038: F5 Bug Tracker Filter Names and Tips