Bug ID 910097: Changing per-request policy while tmm is under traffic load may drop heartbeats

Last Modified: Aug 05, 2020

Bug Tracker

Affected Product:  See more info
BIG-IP APM, SSLO, SWG(all modules)

Known Affected Versions:
13.1.0, 13.1.0.1, 13.1.0.2, 13.1.0.3, 13.1.0.4, 13.1.0.5, 13.1.0.6, 13.1.0.7, 13.1.0.8, 13.1.1, 13.1.1.2, 13.1.1.3, 13.1.1.4, 13.1.1.5, 13.1.3, 13.1.3.1, 13.1.3.2, 13.1.3.3, 13.1.3.4, 14.0.0, 14.0.0.1, 14.0.0.2, 14.0.0.3, 14.0.0.4, 14.0.0.5, 14.0.1, 14.0.1.1, 14.1.0, 14.1.0.1, 14.1.0.2, 14.1.0.3, 14.1.0.5, 14.1.0.6, 14.1.2, 14.1.2.1, 14.1.2.2, 14.1.2.3, 14.1.2.4, 14.1.2.5, 14.1.2.6, 15.0.0, 15.0.1, 15.0.1.1, 15.0.1.2, 15.0.1.3, 15.0.1.4, 15.1.0, 15.1.0.1, 15.1.0.2, 15.1.0.3, 15.1.0.4, 16.0.0

Opened: May 18, 2020
Severity: 2-Critical

Symptoms

Cluster failover, tmm restart, and tmm killed due to missed heartbeats. tmm crash

Impact

Traffic disrupted while tmm restarts.

Conditions

TMM is under load due to heavy traffic while MCP attempts to configure per-request policy. This can be caused by a modification to the policy or one of its agents, or by a restart of the TMM.

Workaround

When making changes to per-request policies, use a scheduled maintenance window so that impact to traffic is minimized.

Fix Information

None

Behavior Change