Bug ID 476521: Unit may hang for an extended period during boot trying to initialize FIPS device.

Last Modified: Mar 21, 2023

Affected Product(s):
BIG-IP TMOS(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.10, 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, 11.6.0 HF4, 11.6.0 HF5, 11.6.0 HF6, 11.6.0 HF7, 11.6.0 HF8, 11.6.1, 11.6.1 HF1, 11.6.1 HF2, 11.6.2, 11.6.2 HF1, 11.6.3, 11.6.3.1, 11.6.3.2, 11.6.3.3, 11.6.3.4, 11.6.4, 11.6.5, 11.6.5.1, 11.6.5.2, 11.6.5.3

Fixed In:
12.0.0

Opened: Aug 22, 2014

Severity: 2-Critical

Symptoms

During boot-up initialization, the unit may hang up to four hours trying to initialize the FIPS device and cause the unit to be nonfunctional and unresponsive for the duration. After initialization is allowed to complete, the FIPS device cannot be used.

Impact

The unit is unusable until initialization completes, after which there is no FIPS functionality.

Conditions

Random and rare. This happens only on FIPS devices.

Workaround

Power cycle the unit.

Fix Information

Use true timeout instead of retries limit in when to give up initializing FIPS device, and subsequently power cycle the unit to recover FIPS device.

Behavior Change

Guides & references

K10134038: F5 Bug Tracker Filter Names and Tips