Bug ID 497627: Tmm cores while using APM network access and no leasepool is created on the BIG-IP system.

Last Modified: May 29, 2024

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

Known Affected Versions:
10.2.4, 11.5.1 HF1, 11.5.1 HF2, 11.5.1 HF3, 11.5.1 HF4, 11.5.1 HF5, 11.5.1 HF6, 11.5.1 HF7, 11.5.1 HF8, 11.5.1 HF9, 11.5.1 HF10, 11.5.1 HF11, 11.5.2 HF1, 11.5.3 HF1, 11.4.0, 11.6.0, 11.6.1, 11.6.2, 11.6.3, 11.6.3.1, 11.6.3.2, 11.6.3.3, 11.6.3.4, 11.6.4, 11.6.5, 11.6.5.1, 11.6.5.2, 11.6.5.3, 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.6.0 HF6, 11.5.3 HF2

Opened: Dec 19, 2014

Severity: 4-Minor

Related Article: K58125050

Symptoms

TMM cores in Network Access scenario when no leasepool is created on the BIG-IP system and IP address assignment is done through the Variable Assign agent (mcget {session.ldap.last.attr.vpnClientIp}).

Impact

Traffic disrupted while tmm restarts.

Conditions

APM network access and no leasepool is created on the BIG-IP system.

Workaround

To work around the problem, create a leasepool on the BIG-IP system; it does not need to be attached to an access policy.

Fix Information

TMM does not core now when using APM network access and no leasepool is created on the BIG-IP system.

Behavior Change

Guides & references

K10134038: F5 Bug Tracker Filter Names and Tips