Bug ID 635939: Replacing scrubber virtual server / route domain causes incorrect scrubbing threshold

Last Modified: Oct 17, 2023

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

Known Affected Versions:
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: Dec 28, 2016

Severity: 3-Major

Symptoms

When replacing a scrubber virtual server or scrubber route domain, some of the scrubbing values are affected: (1) example of replacing scrubber virtual server 'vs-name' to 'VS2': tmsh modify security scrubber profile scrubber-profile-default scrubber-virtual-server modify { vs1 { vs-name VS2 } } (2) where impacted values can be observed (Time to Live, Observed Rate): tmsh show security scrubber dwbl-scrubber-stat

Impact

The throughput capacity will be incorrect.

Conditions

You may encounter this when modifying a virtual or route domain containing a scrubber profile.

Workaround

Instead of doing replace, do a delete/add: tmsh modify security scrubber profile scrubber-profile-default scrubber-virtual-server delete { vs1 }. tmsh modify security scrubber profile scrubber-profile-default scrubber-virtual-server add { vs1 { vs-name VS2 } }.

Fix Information

None

Behavior Change

Guides & references

K10134038: F5 Bug Tracker Filter Names and Tips