Bug ID 565231: Importing a previously exported policy which had two object names may fail

Last Modified: Jul 18, 2026

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

Known Affected Versions:
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, 12.0.0, 12.0.0 hf1, 12.0.0 hf2, 12.0.0 hf3, 12.0.0 hf4

Fixed In:
12.1.0

Opened: Dec 31, 2015

Severity: 3-Major

Symptoms

If an exported access policy includes two object names profile_name-aaa and aaa, import that policy may fail or be incorrect.

Impact

Rare case, but the import of such a policy may fail.

Conditions

For example: access policy name "test" access policy item name "test-empty" access policy item name "empty" For example: access policy name "test" access policy item name "test-empty" macro name "empty"

Workaround

One of the objects could be renamed in the bigip.conf file to avoid such a naming pattern.

Fix Information

Objects are being exported correctly without error.

Behavior Change

Guides & references

K10134038: F5 Bug Tracker Filter Names and Tips