Bug ID 806937: CPM policy stops matching after adding rule

Last Modified: Sep 13, 2023

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

Known Affected Versions:
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

Opened: Jul 18, 2019

Severity: 3-Major

Symptoms

LTM Centralized Policy Matching (CPM) policy conditions stop matching some traffic.

Impact

This might cause the policy to stop matching for nearly all rules, including the rule that check for 'All Traffic'.

Conditions

-- Very specific LTM policy configuration. -- Adding a matching rule. For this case, an example scenario might involve a rule with two conditions and two actions. The two conditions check for one of two HTTP hosts, and checking that the HTTP URI path starts with some substring. The two actions are typically disabling server SSL, and forwarding to a specific pool. The last rule is called DropAll and matches all traffic.

Workaround

None.

Fix Information

None

Behavior Change

Guides & references

K10134038: F5 Bug Tracker Filter Names and Tips