Bug ID 541427: Toggling the type of an entity between Explicit and Wildcard can lead to Set Active Failure

Last Modified: Sep 13, 2023

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

Known Affected Versions:
11.4.1, 11.5.1, 11.5.2, 11.5.3, 11.5.4, 11.5.5, 11.5.6, 11.5.7, 11.5.8, 11.5.9, 11.5.10, 11.6.1, 11.6.2, 11.6.3,,,,, 11.6.4, 11.6.5,,,, 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

Fixed In:

Opened: Aug 23, 2015

Severity: 4-Minor


Wildcard entities must each have a unique order for their pattern processing. Through a series of configuration changes it is possible for the user to get into a situation where it has assigned the same order number to multiple wildcard entities. This leads to a failure when attempting to Apply the Policy.


Policy is unable to be applied.


Multiple configuration changes are made to objects, flipping their state from wildcard to explicit and vice-versa, while creating new wildcard entities in-between.


Export/Import the policy

Fix Information

Wildcard order is correctly adjusted when an object's type is set to wildcard.

Behavior Change

Guides & references

K10134038: F5 Bug Tracker Filter Names and Tips