Last Modified: Sep 13, 2023
Affected Product(s):
BIG-IP ASM, Install/Upgrade
Known Affected Versions:
11.2.1, 11.4.1, 11.5.0, 11.5.1, 11.5.2, 11.5.3, 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
Fixed In:
14.0.0
Opened: Oct 25, 2015 Severity: 4-Minor
In some rare cases a Logging Profile which had remote logging configuration and was then updated to only log locally may be left with the old remote logging data attached. This leads to an invalid state during upgrade.
All ASM configuration will not be upgraded and will be lost.
Upgrading from before 11.2.x, to 11.5.x, 11.6.x, or 12.0.0 through 12.1.1 A Logging Profile with the following attributes: 1) Anomaly logging enabled 2) Remote logging disabled 3) A row exists in LOGPROF_REMOTE_CONFIG for the Logging Profile
Make a spurious change to the problematic Logging Profile and save. This will remove the data inconsistency.
Upgrade no longer fails due to the data inconsistency.