Bug ID 476705: TMM can crash if receiving radius start or stop messages with multiple IP but no subscriber ID.

Last Modified: Apr 10, 2019

Bug Tracker

Affected Product:  See more info
BIG-IP PEM(all modules)

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.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

Fixed In:
12.0.0, 11.6.0 HF4

Opened: Aug 25, 2014
Severity: 3-Major
Related AskF5 Article:
K16790

Symptoms

TMM crashes if the radius start/stop messages received have multiple IP addresses but have no subscriber ID.

Impact

Traffic disrupted while tmm restarts.

Conditions

Conditions leading to this issue include: Receiving radius start or stop messages; the radius message has multiple IP addresses listed; and the radius message dose not have subscriber ID.

Workaround

This issue has no workaround at this time.

Fix Information

After the fix, TMM does not crash if receiving the radius message specified in the above condition

Behavior Change