Last Modified: Sep 13, 2023
Affected Product(s):
BIG-IP AAM, AFM, APM, ASM, AVR, EM, PEM, SWG, vCMP
Known Affected Versions:
11.5.1 HF1, 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.1 HF10, 11.5.1 HF11, 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.2 HF1
Opened: Sep 26, 2013 Severity: 2-Critical Related Article:
K17310
When traffic is very sparse, the report may be incorrect and omit information due to skipped aggregation process of collected data. The original fix caused heavy spikes to the CPU every 5 minutes.
AVR reports may be incorrect.
Very sparse traffic with significant gaps.
This issue has no workaround at this time.
Aggregation of data when traffic is very sparse with significant gaps is now done correctly, and also occurs when data is queried, instead of every 5 minutes in order to avoid a 5 minute CPU spiking issue.