Bug ID 624992: LTM Configuration Found after Provisioning VCMP

Last Modified: May 29, 2024

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

Known Affected Versions:
11.5.4, 11.5.5, 11.5.6, 11.5.7, 11.5.8, 11.5.9, 11.5.10, 11.6.0, 11.6.1, 11.6.2, 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.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, 12.1.0, 12.1.1, 12.1.2, 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, 13.0.0, 13.0.0 HF1, 13.0.0 HF2, 13.0.0 HF3, 13.0.1

Fixed In:
13.1.0

Opened: Oct 26, 2016

Severity: 2-Critical

Symptoms

When provisioning VCMP on a previously enabled LTM unit, the existing LTM configuration is not automatically removed.

Impact

The behavior of the BIG-IP is undefined when VCMP is provisioned and LTM is configured. The impact can range from none to intermittent or total traffic loss.

Conditions

VCMP provisioned with LTM configuration.

Workaround

Delete pool members, pools, and virtual servers before provisioning VCMP.

Fix Information

Virtual servers will be disabled when VCMP is provisioned. If VCMP is already provisioned virtual servers can't be created unless they are created as a disabled virtual.

Behavior Change

Guides & references

K10134038: F5 Bug Tracker Filter Names and Tips