Bug ID 669255: An enabled sFlow receiver can cause poor TMM performance on certain BIG-IP platforms

Last Modified: Nov 07, 2022

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

Known Affected Versions:
12.1.0, 12.1.0 HF1, 12.1.0 HF2, 12.1.1, 12.1.1 HF1, 12.1.1 HF2, 12.1.2, 12.1.2 HF1, 12.1.2 HF2, 12.1.3,, 13.0.0, 13.0.0 HF1, 13.0.0 HF2, 13.0.0 HF3, 13.0.1

Fixed In:

Opened: Jun 14, 2017

Severity: 3-Major

Related Article: K20100613


If the BIG-IP configuration includes at least one enabled sFlow receiver, certain platforms will experience poor TMM performance. Symptoms will include one or more of the following: - Higher than normal ping latency to the BIG-IP Self-IP addresses. - Higher than normal latency for applications flowing through BIG-IP virtual servers. - TMM clock advanced messages in the /var/log/ltm file. - Continuous activation and then quick deactivation of the idle enforcer for all TMM instances in the /var/log/kern.log file.


The BIG-IP system operates at a suboptimal performance level.


The BIG-IP configuration must include at least one enabled sFlow receiver (it doesn't matter whether this is reachable or not) and the platform type must be one of the following: - BIG-IP i10000 series - BIG-IP i7000 series - BIG-IP i5000 series - BIG-IP i4000 series - BIG-IP i2000 series - VIPRION B4450 blade


If the sFlow receiver is not strictly necessary for the correct functioning of your deployment, this can be disabled or removed to work around the issue.

Fix Information

Performance is no longer degraded on certain platforms when the configuration includes enabled sFlow receivers.

Behavior Change

Guides & references

K10134038: F5 Bug Tracker Filter Names and Tips