Bug ID 2208821: VIPRION cluster becomes INOPERATIVE and fails to load configuration after software upgrade

Last Modified: Feb 03, 2026

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

Known Affected Versions:
17.5.0, 17.5.1, 17.5.1.2, 17.5.1.3, 17.5.1.4, 21.0.0, 21.0.0.1

Opened: Jan 21, 2026

Severity: 2-Critical

Symptoms

After upgrading BIG-IP software on a VIPRION system, the device may fail to load the configuration and enter an INOPERATIVE state. The system remains stuck during the configuration load phase, preventing normal operation.

Impact

The VIPRION cluster becomes INOPERATIVE and is unable to load the configuration. Traffic is impacted as the system cannot process or pass traffic until the issue is resolved.

Conditions

1. VIPRION platform with clustered configuration. 2. Performing a BIG-IP software upgrade. 3. System attempts to load post-upgrade configuration during boot or blade role transition

Workaround

Restarting the system with a different blade set as primary, or reverting to the previously working software version, allows the configuration to load successfully. In some cases, re-attempting the upgrade after correcting the blade role transition also resolves the issue.

Fix Information

None

Behavior Change

Guides & references

K10134038: F5 Bug Tracker Filter Names and Tips