Last Modified: Oct 19, 2025
Affected Product(s):
BIG_IP_NEXT(CM) TMOS
Known Affected Versions:
20.2.1
Opened: Jun 27, 2024 Severity: 1-Blocking
On VELOS, upgrade of first node has completed, and when failover is triggered, either automatically by CM or manually, the CM reports that the failover has failed due to 401 Failed to authenticate. Even with CM reporting failure, the failover operation will proceed on the instance.
CM shows BIG-IP Next HA status as Unhealthy though the actual BIG-IP Next status is healthy.
During BIG-IP Next upgrade using CM.
Use the following steps as a workaround: 1. Open the properties drawer for the instance and go to the HA section. 2. Confirm that the nodes have swapped roles in the cluster. The new active should be at the upgraded version and the standby should be at the earlier version. 2.1 Also, the cluster health API can be used through postman to confirm that failover has finished. GET https://{{CM-address}}/api/v1/spaces/default/instances/{{Big-IP-Next-ID}}/health The response should show the nodes have swapped roles, and one is ACTIVE and the other is STANDBY. 3. Disable the toggle for "Enable automatic failover" and click upgrade for the standby node and follow normal upgrade workflow procedure. 4. When upgrade has finished, in the Instance list page, the HA instance will show the upgraded version and the cluster will be healthy.
None