Last Modified: Oct 16, 2023
Affected Product(s):
BIG-IP Install/Upgrade, TMOS, vCMP
Known Affected Versions:
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, 13.0.0, 13.0.0 HF1, 13.0.0 HF2, 13.0.0 HF3, 13.0.1, 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
Fixed In:
14.1.0, 14.0.0, 13.1.3, 12.1.4.1
Opened: Mar 09, 2018 Severity: 3-Major
When devices in a Device Service Cluster (DSC) are upgraded, multiple devices might become Active simultaneously. During upgrade, the process erroneously clears the management-ip during reboot, and then synchronizes to other members of the DSC. If the system is not performing an upgrade, the error is repaired as the device starts up, and has no visible effect. If an upgrade is being performed, the management-ip cannot be repaired, and the DSC members lose contact with each other, so they all become Active.
When multiple devices become Active simultaneously, traffic is disrupted.
-- Running on VIPRION chassis systems, either natively, or as a vCMP guest. -- Upgrading from any affected versions (TMOS v12.1.3, TMOS v13.0.0, TMOS v13.0.1, TMOS v13.1.0), to any other version.
There is no workaround other than to remain in Active/Active state until upgrade is complete on all chassis in the DSC are finished. See K43990943: VIPRION systems configured for high availability may become active-active during the upgrade process :: https://support.f5.com/csp/article/K43990943 for more information on how to mitigate this issue.
The erroneous management-ip change is not made, and the HA failover mechanism operates correctly across upgrade.