Last Modified: Oct 17, 2023
Affected Product(s):
BIG-IP All
Known Affected Versions:
11.5.0, 11.5.1, 11.5.2, 11.5.3, 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.1.0, 12.1.1, 12.1.2, 12.1.3, 12.1.3.1, 12.1.3.2, 12.1.3.3, 12.1.3.4, 12.1.3.5, 12.1.3.6, 12.1.3.7, 12.1.4, 12.1.4.1, 12.1.5, 12.1.5.1, 12.1.5.2, 12.1.5.3, 12.1.6, 13.0.0, 13.0.0 HF1, 13.0.0 HF2, 13.0.0 HF3, 13.0.1, 13.1.0, 13.1.0.1, 13.1.0.2, 13.1.0.3, 13.1.0.4, 13.1.0.5, 13.1.0.6, 13.1.0.7, 13.1.0.8, 13.1.1, 13.1.1.2, 13.1.1.3, 13.1.1.4, 13.1.1.5, 13.1.3, 13.1.3.1, 13.1.3.2, 13.1.3.3, 13.1.3.4, 13.1.3.5, 13.1.3.6, 13.1.4, 13.1.4.1, 13.1.5, 13.1.5.1, 14.0.0, 14.0.0.1, 14.0.0.2, 14.0.0.3, 14.0.0.4, 14.0.0.5, 14.0.1, 14.0.1.1
Opened: Apr 13, 2016 Severity: 5-Cosmetic
Throughput statistics on a multi-slot vCMP guest are not accurate when tcpdump is running. Specifically, the BIG-IP Administrator may find that starting a tcpdump command causes the Throughput figures to double or even triple (both In and Out). When the tcpdump command is stopped, the Throughput figures return to normal. This issue affects all systems reporting Throughput figures (i.e. the performance graphs in the configuration utility, TMSH, SNMP, etc.). TMM Throughput figures, however, are not affected by this issue and remain accurate while tcpdump is being run.
The impact is cosmetic, in the sense that the system is fully functional and performing as intended during the issue. However, the incorrect reporting of Throughput figures may confuse and alarm BIG-IP Administrators, causing them to take unnecessary remedial actions (restart, failover, expand the guest, burst to the cloud, etc.). In this case, there is no remedial action needed.
A tcpdump command is started on a multi-slot vCMP guest.
None needed. When the tcpdump command stops, the Throughput figures return to normal.
None