Last Modified: Oct 19, 2025
Affected Product(s):
BIG_IP_NEXT(VE/HW) Install/Upgrade, TMOS
Fixed In:
20.3.0
Opened: Jun 26, 2024 Severity: 1-Blocking
After the first node of an HA pair has been upgraded, failover is triggered, either automatically by CM or manually by the user, and CM reports failover has failed due to "401 Failed to authenticate." even though failover has occurred.
CM shows BIG-IP Next HA status as Unhealthy though the actual BIG-IP Next status is healthy.
-- BIG-IP Next HA pair is upgraded using CM. -- VMware environment
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 older version. 2.1 The cluster health API could also be used here via 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 steps. 4. When upgrade has finished the HA instance in the Instance list grid will show the upgraded version and cluster will be healthy.
None