Last Modified: Aug 19, 2026
Affected Product(s):
BIG-IP PEM
Known Affected Versions:
11.5.1, 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, 11.5.2 hf1, 11.5.3, 11.5.3 hf1, 11.5.3 hf2, 11.5.4, 11.5.4 hf1, 11.5.4 hf2, 11.5.4 hf3, 11.5.4 hf4, 11.5.5, 11.5.6, 11.5.7, 11.5.8, 11.5.9, 11.5.10, 11.6.0, 11.6.0 hf1, 11.6.0 hf2, 11.6.0 hf3, 11.6.0 hf4, 11.6.0 hf5, 11.6.0 hf6, 11.6.0 hf7, 11.6.0 hf8, 11.6.1, 11.6.1 hf1, 11.6.1 hf2, 11.6.2, 11.6.2 hf1, 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
Fixed In:
12.0.0
Opened: Feb 25, 2015 Severity: 3-Major Related Article:
K74503799
TMM might core sometimes if provisioning hold time is set. When a multiple IP session is created with IPv4 and IPv6 addresses.
Traffic disrupted while tmm restarts.
Provisioning hold time is set to non-zero.And remove one of the IP address by running the command: radius stop.
Disable provisioning hold time. Set the tmm.pem.session.radius.provisioning.hold.time DB variable to 0: list sys db tmm.pem.session.radius.provisioning.hold.time sys db tmm.pem.session.radius.provisioning.hold.time { value "0" } root@(dpi-bvt2)(cfg-sync Standalone)(Active)(/Common)(tmos)#.
In this release, TMM no longer cores if provisioning hold time is set to non-zero.