Last Modified: Oct 19, 2025
Affected Product(s):
BIG_IP_NEXT(CM) TMOS
Known Affected Versions:
20.3.0
Opened: Sep 10, 2024 Severity: 1-Blocking
The BIG-IP Next Central Manager displays a Failed status for High Availability when a third node is added to the group.
The BIG-IP Next Central Manager displays a Failed status in the High Availability. The last node needs to be removed and replaced with refreshed node or a new node to achieve a healthy High Availability state.
This issue occurs when nodes are added to a standalone BIG-IP Next Central Manager to form a High Availability group.
When adding a third node to the High Availability cluster, if the status displays as "Failed", the last node needs to be removed, and a refreshed node or a new node needs to be added back to the Central Manager High Availability group. The steps are as follows: 1. Log in to the Central Manager UI and remove the last node. 2. Reset the impacted node by running k3s_reset_cluster.py and rebooting it. Clear the contents of /var/lib/f5/infra-manager/registration-details.json. 3. Add the node back to the Central Manager High Availability group.
None