Bug ID 536757: BIG-IP VE may restart tmm if descheduled by hypervisor for extended periods

Last Modified: Apr 10, 2019

Bug Tracker

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

Known Affected Versions:
12.0.0, 12.0.0 HF1, 12.0.0 HF2, 12.0.0 HF3, 12.0.0 HF4, 12.1.0, 12.1.0 HF1, 12.1.0 HF2, 12.1.1, 12.1.1 HF1, 12.1.1 HF2, 12.1.2, 12.1.2 HF1, 12.1.2 HF2, 12.1.3, 12.1.3.1, 12.1.3.2, 12.1.3.3, 12.1.3.4, 12.1.3.5, 12.1.3.6, 12.1.3.7, 12.1.4, 12.1.4.1, 13.0.0, 13.0.0 HF1, 13.0.0 HF2, 13.0.0 HF3, 13.0.1, 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.1, 13.1.1.2, 13.1.1.3, 13.1.1.4, 14.0.0, 14.0.0.1, 14.0.0.2, 14.0.0.3, 14.0.0.4, 14.1.0, 14.1.0.1, 14.1.0.2, 14.1.0.3

Opened: Jul 30, 2015
Severity: 2-Critical

Symptoms

BIG-IP Virtual Edition (VE) configuration may restart the tmm process if it is descheduled for 10 seconds or more. This generally happens only on oversubscribed systems.

Impact

The tmm potentially restarts due to an ABORT signal. This does not always happen, depending upon what happens to run first (tmm or sod) when the BIG-IP system gets a chance to run. Traffic disrupted while tmm restarts.

Conditions

-- Overprovision resources on a hypervisor without any CPU reservations for a BIG-IP system. -- Cause enough work to happen where the BIG-IP system cannot be scheduled to run for 10 seconds.

Workaround

You can use either of the following workarounds: -- Reserve ample CPU resources to guarantee that tmm gets an opportunity to touch its watchdog within 10 seconds. -- Do not provision enough jobs on a hypervisor host such that the BIG-IP system is not allotted sufficient CPU cycles.

Fix Information

None

Behavior Change