Last Modified: Nov 17, 2026
Affected Product(s):
BIG-IP LTM
Known Affected Versions:
14.1.0, 14.1.0.1, 14.1.0.2, 14.1.0.3, 14.1.0.5, 14.1.0.6, 14.1.2, 14.1.2.1, 14.1.2.2, 14.1.2.3, 14.1.2.4, 14.1.2.5, 14.1.2.6, 14.1.2.7, 14.1.2.8, 14.1.3, 14.1.3.1, 14.1.4, 14.1.4.1, 14.1.4.2, 14.1.4.3, 14.1.4.4, 14.1.4.5, 14.1.4.6, 14.1.5, 14.1.5.1, 14.1.5.2, 14.1.5.3, 14.1.5.4, 14.1.5.6, 17.1.1, 17.1.1.1, 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, 17.1.3.2, 17.1.3.4, 17.1.3.5, 17.1.3.6, 17.1.3.7, 17.5.1, 17.5.1.2, 17.5.1.3, 17.5.1.4, 17.5.1.5, 17.5.1.6, 17.5.1.8, 17.5.1.9, 17.5.1.10, 17.5.1.11
Opened: Jun 13, 2023 Severity: 3-Major
After a clusterd partition event and subsequent failover due to min-up-cluster-mbr action the blade that detected the partition reports as HA active and not standby like the other members.
Invalid HA state
After configuring two multi-blade chassis or vCMP guest in HA, and configuring the /sys Custer default min-up-members to the number of blades/slots and min-up-members-enabled to true on both devices (eg: tmsh modify /sys cluster default min-up-members-enabled yes min-up-members 4 (a secondary) If packets gets dropped on the secondary blade, then one cluster member reports as HA active as seen in tmsh /sys cluster, while other correctly report as standby when all cluster members should report as HA standby.
Restart clusterd on impacted blade
None