Bug ID 807933: Cloning a Virtual Server between two non-default partitions fails when ASM policy is applied

Last Modified: Apr 28, 2025

Affected Product(s):
BIG-IQ Web App Security (ASM)(all modules)

Known Affected Versions:
6.1.0, 7.0.0, 7.0.0.1, 7.0.0.2, 7.1.0, 7.1.0.1, 7.1.0.2, 7.1.0.3, 7.1.6, 7.1.6.1, 7.1.7, 7.1.7.1, 7.1.7.2, 7.1.8, 7.1.8.1, 7.1.8.2, 7.1.8.3, 7.1.8.4, 7.1.8.5, 7.1.9, 7.1.9.7, 7.1.9.8, 7.1.9.9

Opened: Jul 22, 2019

Severity: 3-Major

Symptoms

Cloning a Virtual server that has an ASM Security Policy attached to it in the LTM space will fail to deploy.

Impact

Unable to deploy the cloned Virtual Server with ASM Security Policy from the LTM space.

Conditions

This is encountered when cloning a Virtual server.

Workaround

ASM Policies relation to Virutal Servers are managed in the Web Application Security section on BIG-IQ. When cloning an LTM virtual server, a shadow virtual server will be created under Web Application Security Section. After cloning the Virtual Server, the "auto" LTM policy should be removed from the LTM Virtual Server and the desired ASM Policy attached to the Web Application Security Virtual Server. After the above steps, deploy LTM which will deploy the new Virtual Server to the BIG-IP, and then deploy Web Application Security which will deploy the association between the ASM Policy and the Virtual Server.

Fix Information

None

Behavior Change

Guides & references

K10134038: F5 Bug Tracker Filter Names and Tips