Last Modified: Sep 13, 2023
Affected Product(s):
BIG-IP All
Known Affected Versions:
11.5.1 HF1, 11.5.1 HF2, 11.5.1 HF3, 11.5.1 HF4, 11.6.2 HF1, 11.6.0, 11.6.1, 11.6.2, 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, 12.1.0 HF1, 12.1.0 HF2, 12.1.1 HF1, 12.1.1 HF2, 12.1.2 HF1, 12.1.2 HF2
Fixed In:
12.0.0, 11.6.0 HF5, 11.5.1 HF5
Opened: Aug 05, 2014 Severity: 3-Major
The average system CPU usage and the busiest CPU in the dashboard can appear to be exceptionally high when a module with dedicated analysis processes like AVR is being used. These processes have dedicated resources so they do not impact the resources used by the critical data plane, so the high CPU usage is misleading.
The system CPU usage and busiest CPU appear to be higher than expected.
A module such as AVR that has dedicated analysis processes must be provisioned.
The workaround is to examine the detailed per CPU graphs and note that the high CPU is limited to the analysis processor which is the CPU with the highest number on a BIG-IP appliance.
Average system CPU and busiest CPU calculation is now based on the critical data plane processing.
Average system CPU and busiest CPU calculation is now based on the critical data plane processing.