Last Modified: Sep 13, 2023
Affected Product(s):
BIG-IP AVR
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.5.2 HF1, 11.5.3 HF1, 11.5.3 HF2, 11.5.4 HF1, 11.5.4 HF2, 11.5.4 HF3, 11.5.4 HF4, 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 HF4
Opened: Aug 03, 2014 Severity: 2-Critical
IP addresses are not properly cleaned from lookup tables, so there might be no room for new IP addresses to be collected. System might post many messages in the avrd log, including ones similar to the following: -- AVRDATA_QUERY|WARNING|... lib/avrdata/query/http_main_query.c:0547| HTTP Main, got an entity with invalid key: 2, 3, 0 -- AVRDATA_QUERY|WARNING|... lib/avrdata/query/http_main_query.c:0841| Skip the entity with invalid key
New IP addresses might not be collected. It is possible that AVR statistics could be incorrect, or could fail to report any statistics.
This occurs when using AVR when the system is idle after traffic IP lookups.
None.
IP addresses are now properly cleaned from lookup tables, making room so new IP addresses can be collected.