Bug ID 597972: Inconsistent treatment for sFlow configuration in CLI and GUI.

Last Modified: Sep 13, 2023

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

Known Affected Versions:
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.0.0, 12.0.0 HF1, 12.1.0 HF1, 12.0.0 HF2, 12.1.0 HF2, 12.0.0 HF3, 12.0.0 HF4, 12.1.1 HF1, 12.1.1 HF2, 12.1.2 HF1, 12.1.2 HF2, 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

Fixed In:
13.1.0

Opened: Jun 08, 2016

Severity: 3-Major

Related Article: K49512487

Symptoms

When using the GUI to configure sFlow settings on a VLAN, HTTP profile, or interface, specifying a poll interval or sample rate of '0' works as follows: -- The GUI treats as "Default" an sFlow poll interval / sample rate of "0". -- TMSH treats "0" as the 0 (zero) value. What that means is that if you use tmsh to configure those values to "0", and then go into the GUI to reconfigure those objects, even if you don't change the poll interval / sample rate), the system resets those values to use the default (inherit from the global sFlow settings).

Impact

The BIG-IP system sets sFlow settings of an object to the global sFlow configuration's values.

Conditions

Using the tmsh to set sFlow poll interval / sample rate of "0", and then using the GUI to update anything in the configuration.

Workaround

Use tmsh to view and modify sFlow configuration settings when you plan to set the poll-interval to 0.

Fix Information

Ensure Polling Interval and Sample Rate State values are consistently persisted in the GUI.

Behavior Change

Guides & references

K10134038: F5 Bug Tracker Filter Names and Tips