Bug ID 441512: ConfigSync failing with sFlow error

Last Modified: Aug 19, 2026

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

Known Affected Versions:
11.5.1, 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, 11.5.2 hf1, 11.5.3, 11.5.3 hf1, 11.5.3 hf2, 11.5.4, 11.5.4 hf1, 11.5.4 hf2, 11.5.4 hf3, 11.5.4 hf4, 11.5.5, 11.5.6, 11.5.7, 11.5.8, 11.5.9, 11.5.10, 11.6.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.6.1, 11.6.1 hf1, 11.6.1 hf2, 11.6.2, 11.6.2 hf1, 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

Fixed In:
12.0.0

Opened: Dec 23, 2013

Severity: 3-Major

Related Article: K15840

Symptoms

An sFlow error may occur during sync of a device.

Impact

Sync might fail, which can impact connection mirroring, and other system operations. The system posts an sflow message similar to the following: 'Can't save/checkpoint DB object, class:sflow_http_virtual_data_source status:13'.

Conditions

Exact conditions are unknown and difficult to reproduce, but some possible conditions include sync operations following delete/create of a virtual server or profiles (either directly or by deleting/creating an iApp), sync following failover,

Workaround

Force the mcpd process to reload the BIG-IP configuration. For more information, see SOL13030, Forcing the mcpd process to reload the BIG-IP configuration, available here: Link: https://support.f5.com/kb/en-us/solutions/public/13000/000/sol13030.html.

Fix Information

Sync now completes successfully, without sflow error.

Behavior Change

Guides & references

K10134038: F5 Bug Tracker Filter Names and Tips