Last Modified: Nov 07, 2022
Affected Product(s):
BIG-IP AFM, ASM, AVR
Known Affected Versions:
11.5.1, 11.5.1 HF1, 11.5.1 HF10, 11.5.1 HF11, 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.10, 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.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, 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
Fixed In:
13.0.0, 12.1.1 HF2, 12.1.1 HF1, 11.6.1 HF1
Opened: Feb 22, 2016 Severity: 2-Critical Related Article:
K54931123
In certain configurations, Analytics statistics on virtual server activity may not be reported correctly.
As a result, Analytics reports show an Aggregated Virtual Server or an incorrect one instead of displaying the correct virtual servers.
This occurs for virtual servers that are configured in one of these ways: 1. Two virtual servers have the same IP-Port-RouteDomain setting, but they use different protocols (such as TCP for one and UDP for the other) or different sources. 2. A virtual server is defined with a masked IP address rather than an explicit address (for example, 10.10.10.0/24).
None.
Correct identification of the virtual server and the activity reported in the charts is displaying to the right virtual server.
