Bug ID 453349: Interval value stting for iCall periodic handlers on vCMP

Last Modified: Mar 12, 2019

Bug Tracker

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

Known Affected Versions:
11.4.0, 11.4.1, 11.5.0, 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

Fixed In:
12.0.0

Opened: Mar 20, 2014
Severity: 3-Major
Related AskF5 Article:
K30516454

Symptoms

The default value for unspecified field 'interval' for the iCall periodic handler configuration item might cause system instability, and consume 100% CPU.

Impact

The system might become unstable and cause daemon restarting.

Conditions

Not defining the 'interval' value on creation, or modifying the value to '0' using vCMP.

Workaround

Specify an interval value of '1' or greater for all iCall periodic handlers

Fix Information

In cases in which no value is specified for interval' for the iCall periodic handler configuration, or if the value specified is '0' (zero), a negative value, or greater than the maximum '4294967295 value', the system displays a valid error, so no system instability can occur. Note that upgrades in which the interval value is '0', the system modifies that value to '1'.

Behavior Change