Last Modified: Mar 21, 2026
Affected Product(s):
BIG-IP LTM
Known Affected Versions:
17.1.1.2, 17.1.1.3, 17.1.1.4, 17.1.2, 17.1.2.1, 17.1.2.2, 17.1.3, 17.1.3.1
Opened: Feb 17, 2026 Severity: 2-Critical
In an extremely rare scenario where one or more blade goes offline when the active system controller of the tenant is pulled out, there is no corresponding drop in HA score on the tenant and failover does not occur.
1) No tenant failover happens though the number of working trunk members went down
1) Active controller on the tenant is pulled out 2) One or more blades go offline erroneously after this 3) HA group on the tenant is configured with F5OS_INTERNAL trunk component with an appropriate weight
In this condition, restart sod by using the below command bigstart restart sod
None