Bug ID 441952: Inability to name a policy when importing or creating from template

Last Modified: Sep 13, 2023

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

Known Affected Versions:
11.4.1, 12.1.0 HF1, 12.1.0 HF2, 12.1.1 HF1, 12.1.1 HF2, 12.1.2 HF1, 12.1.2 HF2

Fixed In:
12.0.0

Opened: Jan 02, 2014

Severity: 3-Major

Related Article: K17205

Symptoms

The user is unable to give a custom name to the security policy during deployment wizard in case of "New Virtual Server/Existing Virtual Server" deployment scenario.

Impact

User is unable to give a custom name to the security policy during deployment wizard in case of "New Virtual Server/Existing Virtual Server" deployment scenario.

Conditions

Enter to the deployment wizard and choose "New Virtual Server/Existing Virtual Server" deployment scenario. Try to configure the security policy name.

Workaround

To work around this issue, configure all local traffic configuration manually, without using the Deployment Wizard.

Fix Information

The user is now able to give a custom name to the security policy during deployment wizard in case of "New Virtual Server/Existing Virtual Server" deployment scenario.

Behavior Change

Guides & references

K10134038: F5 Bug Tracker Filter Names and Tips