Last Modified: Sep 13, 2023
Affected Product(s):
BIG-IP LTM
Known Affected Versions:
10.2.3, 10.2.4, 11.0.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.5.1 HF1, 11.6.1 HF1, 11.5.1 HF2, 11.6.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.6.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, 11.1.0, 11.2.0, 11.2.1, 11.3.0, 11.4.0, 11.4.1
Fixed In:
11.5.0
Opened: Oct 24, 2013 Severity: 3-Major Related Article:
K14963
After TCP virtual server statistics are reset, the counters for open connections, close_wait, fin_wait, time_wait, and accepts remained too high.
The customers cannot rely on our TCP statistics: you may have for example 100 open connections, but if you reset virtual server stats enough times, the system may report 1 billion open connections. Additionally, this doesn't affect only our customers. We have hundreds of support engineers that every day try to solve cases with the data contained in our qkviews. Having incorrect statistics about the TCP connections can be misleading for F5 support personnel too.
The TCP virtual server statistics were reset while the counters for open connections, close_wait, fin_wait, time_wait or accept were not zero.
Don't reset the TCP virtual server statistics.
A reset of statistics for a TCP virtual server will no longer cause the counters for the number of open connections, close_wait, fin_wait, time_wait or accepts to remain high.