Bug ID 472117: Analytics scheduled report: "predefinedReportName" and "multiLeveledReport" are mutually exclusive

Last Modified: Apr 28, 2025

Affected Product(s):
BIG-IP AVR(all modules)

Known Affected Versions:
11.3.0, 11.4.0, 11.4.1, 11.5.0, 11.5.1, 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.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.5.10, 11.6.0, 11.6.0 HF1, 11.6.0 HF2, 11.6.0 HF3, 11.6.0 HF4, 11.6.0 HF5

Fixed In:
12.0.0, 11.6.0 HF6

Opened: Jul 17, 2014

Severity: 3-Major

Symptoms

Analytics scheduled report: You create a non-loadable configuration by changing "predefinedReportName" to "multiLeveledReport", or the reverse for an "analytics application-security scheduled-report".

Impact

The entire system configuration is not loaded.

Conditions

Trying to modify an existing scheduled-report type from predefined to multi-leveled or vice versa caused error message. This was true for both tmsh and REST-API.

Workaround

Manually edit /config/bigip.conf so that "predefinedReportName" and "multiLeveledReport" do not appear together in the same Analytics scheduled report.

Fix Information

REST API: You can now modify a scheduled-report type, and it will automatically reset the other type's attribute ("predefinedReportName" or "multiLeveledReport").

Behavior Change

Guides & references

K10134038: F5 Bug Tracker Filter Names and Tips