Bug ID 648917: Need to re-provision vCMP after upgrading to 13.1.x or later on the BIG-IP 10350F platform

Last Modified: Apr 29, 2023

Affected Product(s):
BIG-IP Install/Upgrade, TMOS, vCMP(all modules)

Known Affected Versions:
13.1.0, 13.1.0.1, 13.1.0.2, 13.1.0.3, 13.1.0.4, 13.1.0.5, 13.1.0.6, 13.1.0.7, 13.1.0.8, 13.1.1, 13.1.1.2, 13.1.1.3, 13.1.1.4, 13.1.1.5, 13.1.3, 13.1.3.1, 13.1.3.2, 13.1.3.3, 13.1.3.4, 13.1.3.5, 13.1.3.6, 13.1.4, 13.1.4.1, 13.1.5, 13.1.5.1, 14.0.0, 14.0.0.1, 14.0.0.2, 14.0.0.3, 14.0.0.4, 14.0.0.5, 14.0.1, 14.0.1.1, 14.1.0, 14.1.0.1, 14.1.0.2, 14.1.0.3, 14.1.0.5, 14.1.0.6, 14.1.2, 14.1.2.1, 14.1.2.2, 14.1.2.3, 14.1.2.4, 14.1.2.5, 14.1.2.6, 14.1.2.7, 14.1.2.8, 14.1.3, 14.1.3.1, 14.1.4, 14.1.4.1, 14.1.4.2, 14.1.4.3, 14.1.4.4, 14.1.4.5, 14.1.4.6, 14.1.5, 14.1.5.1, 14.1.5.2, 14.1.5.3, 14.1.5.4

Opened: Mar 03, 2017

Severity: 3-Major

Symptoms

With vCMP provisioned, upgrading to 13.1.x or later release will not enable IOMMU support after the upgrade.

Impact

Guests configured with FIPS functionality will fail to start until IOMMU is enabled.

Conditions

-- Upgrading to 13.1.x or later. -- vCMP already provisioned. -- Running on the BIG-IP 10350F platform.

Workaround

You can use either of the following workarounds: -- Re-provision vCMP after the upgrade to enable IOMMU support. 1. Modify the value of the DB variable kernel.iommu to 'enable'. 2. Restart the BIG-IP system.

Fix Information

None

Behavior Change

Guides & references

K10134038: F5 Bug Tracker Filter Names and Tips