Last Modified: Nov 07, 2022
Affected Product:
See more info
BIG-IP ASM, Install/Upgrade
Known Affected Versions:
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, 12.0.0, 12.0.0 HF1, 12.0.0 HF2, 12.0.0 HF3, 12.0.0 HF4, 12.1.0, 12.1.0 HF1, 12.1.0 HF2, 12.1.1, 12.1.1 HF1, 12.1.1 HF2, 12.1.2, 12.1.2 HF1, 12.1.2 HF2, 12.1.3, 12.1.3.1, 12.1.3.2, 12.1.3.3, 12.1.3.4, 12.1.3.5, 12.1.3.6, 12.1.3.7, 12.1.4, 12.1.4.1, 12.1.5, 12.1.5.1, 12.1.5.2, 12.1.5.3, 12.1.6
Fixed In:
13.0.0
Opened: Jun 21, 2016
Severity: 3-Major
A scheduled report (of predefined type) that is created using the GUI might result in a validation error on upgrade, which might cause the upgrade process to fail. You may see this error in /var/log/ltm: Syntax Error:(/config/bigip.conf at line: 86) "predefined-report-name" may not be specified with "multi-leveled-report.time-diff".
Upgrade process can fail.
Creating predefined-scheduled-report from the GUI.
If the config load fails, you can get the configuration to load by manually removing the scheduled reports. Impact of mitigation: This removes scheduled reports from the configuration. 1. Edit bigip.conf. 2. Look for analytics objects that have the scheduled-report in the declaration: analytics application-security scheduled-report /Common/... { 3. Remove the object and the configuration will load.
Improved validation mechanism to disallow creating one type (predefined virtual server, multi-leveled) of scheduled-report with fields of the other one set to it. GUI does not set fields of multi-leveled scheduled-report when creating a predefined-scheduled-report.
