Bug ID 497078: Modifying an existing ipsec policy configuration object might cause tmm to crash

Last Modified: Sep 13, 2023

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

Known Affected Versions:
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.5.3 HF2, 11.5.4 HF1, 11.5.4 HF2, 11.5.4 HF3, 11.5.4 HF4, 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

Opened: Dec 17, 2014

Severity: 2-Critical

Symptoms

Modifying an existing ipsec policy configuration object might cause tmm to crash

Impact

Traffic disrupted while tmm restarts.

Conditions

Modifying an existing ipsec policy configuration object that's not associated with any traffic selector that's assigned to an ikev2 ike peer configuration object.

Workaround

Delete and re-create the ipsec policy mcp object

Fix Information

tmm will not crash when user modify an existing ipsec policy configuration object

Behavior Change

Guides & references

K10134038: F5 Bug Tracker Filter Names and Tips