Bug ID 706484: Upgrading AVR DOS visibility database to 13.x/14.0.x versions from earlier major releases take significant resources

Last Modified: Aug 08, 2019

Bug Tracker

Affected Product:  See more info
BIG-IP Install/Upgrade, TMOS(all modules)

Known Affected Versions:
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, 13.1.1.5, 13.1.3, 14.0.0, 14.0.0.1, 14.0.0.2, 14.0.0.3, 14.0.0.4, 14.0.0.5

Fixed In:
14.1.0

Opened: Feb 13, 2018
Severity: 3-Major

Symptoms

When upgrading a system to 13.x version from earlier major releases that had DoS visibility information stored, the first boot after upgrade takes additional CPU and disk I/O resources.

Impact

During the database update, a python script takes significant memory and disk I/O resources, and one or more of the following can happen: -- Other processes can crash (such as monpd or mcpd). -- Unexpected/unwanted failover. -- The kernel OOM killer can stop a python process with 1 GBytes or more of memory in use.

Conditions

-- A system that was running 12.x or earlier releases, and upgraded to 13.x/14.0.x versions. -- AVR database contains a large volume of DoS visibility information.

Workaround

None.

Fix Information

None

Behavior Change