Last Modified: Nov 07, 2022
Affected Product:
See more info
BIG-IP PEM
Known Affected Versions:
11.5.1, 11.5.1 HF1, 11.5.1 HF10, 11.5.1 HF11, 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.10, 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.6.0, 11.6.0 HF1, 11.6.0 HF2, 11.6.0 HF3, 11.6.0 HF4
Fixed In:
12.0.0, 11.6.0 HF5
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.
