Bug ID 601536: Analytics load error stops load of configuration

Last Modified: Sep 13, 2023

Affected Product(s):
BIG-IP AVR, Install/Upgrade(all modules)

Known Affected Versions:
11.5.4, 11.5.5, 11.5.6, 11.5.7, 11.5.8, 11.5.9, 11.5.10, 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.0.0, 12.0.0 HF1, 12.1.0 HF1, 12.0.0 HF2, 12.1.0 HF2, 12.0.0 HF3, 12.0.0 HF4, 12.1.1 HF1, 12.1.1 HF2, 12.1.2 HF1, 12.1.2 HF2, 12.1.0, 12.1.1, 12.1.2

Fixed In:
13.0.0, 12.1.3

Opened: Jun 27, 2016

Severity: 2-Critical

Related Article: K42802455

Symptoms

After upgrading, the configuration fails to load and you see this log message: 01071ac1:3: Non-Comulative metric (max-request-throughput) cannot be calculated per single entity (pool-member). Unexpected Error: Validating configuration process failed.

Impact

Configuration fails to load, will not pass traffic.

Conditions

This can occur any time the analytics configuration was valid in a previous release and is no longer valid. For example, if you have an analytics profile set at pool-member granularity, it will load in 12.0.0 but will fail to load on 12.1.0 as granularity must be set at the virtual-server level, not the pool level.

Workaround

Fixing the configuration manually is the only option when this occurs. In the pool-member granularity example, you can check all your analytics profiles for granularity pool-member and set them to granularity virtual-server.

Fix Information

An analytics configuration that was valid in a previous release now loads successfully in the current release.

Behavior Change

Guides & references

K10134038: F5 Bug Tracker Filter Names and Tips