Bug ID 601035: TCP-Analytics can fail to collect all the activity

Last Modified: Oct 16, 2023

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

Known Affected Versions:
12.1.0, 12.1.1

Fixed In:
13.0.0, 12.1.2

Opened: Jun 23, 2016

Severity: 3-Major

Symptoms

When the traffic reaching the BIG-IP system comes from a very large number of different client IP addresses and subnets, the TCP-Analytics table can get full, which leads to ignoring the activity that follows, until next snapshot of data.

Impact

TCP Analytics is showing only some of the activity, not all of it. In addition, numerous log messages might fill the logs.

Conditions

-- TCP-Analytics profile is attached to a virtual server. -- Incoming traffic represents a large amount of client IP addresses and subnets (the exact number that causes the full table condition depends on machine type and provisioned modules).

Workaround

Disable TCP-Analytics.

Fix Information

Aggregation method of TCP Analytics was fixed, so the system no longer reaches the full table situation, no matter the distribution of the client IP addresses.

Behavior Change

Guides & references

K10134038: F5 Bug Tracker Filter Names and Tips