Bug ID 479537: Force to Standby does not work with HA Groups configured.

Last Modified: Sep 13, 2023

Affected Product(s):
BIG-IP TMOS(all modules)

Known Affected Versions:
11.4.1, 11.5.0, 11.5.1, 11.5.2, 11.5.3, 11.5.4, 11.5.5, 11.5.6, 11.5.7, 11.5.8, 11.5.9, 11.5.10, 11.6.0, 11.6.1, 11.6.2, 11.6.3, 11.6.3.1, 11.6.3.2, 11.6.3.3, 11.6.3.4, 11.6.4, 11.6.5, 11.6.5.1, 11.6.5.2, 11.6.5.3, 12.0.0, 12.0.0 HF1, 12.1.0 HF1, 12.0.0 HF2, 12.1.0 HF2, 12.0.0 HF3, 12.0.0 HF4, 12.1.1 HF1, 12.1.1 HF2, 12.1.2 HF1, 12.1.2 HF2, 12.1.0, 12.1.1, 12.1.2, 12.1.3, 12.1.3.1, 12.1.3.2, 12.1.3.3, 12.1.3.4, 12.1.3.5, 12.1.3.6, 12.1.3.7, 12.1.4, 12.1.4.1, 12.1.5, 12.1.5.1, 12.1.5.2, 12.1.5.3, 12.1.6, 13.0.0, 13.0.0 HF1, 13.0.0 HF2, 13.0.0 HF3, 13.0.1

Fixed In:
13.1.0

Opened: Sep 16, 2014

Severity: 4-Minor

Symptoms

Using Force to Standby does not work if HA Groups are configured. In older releases, the operation is allowed, but has no effect, or is unreliable. In newer releases, the operation is disallowed.

Impact

Administrator must make configuration changes (disable HA Groups) in order to force a particular device to become Active.

Conditions

Configure HA Group scoring for a traffic-group.

Workaround

Workaround is to disable the HA Group on the Active device, perform the failover, and then re-enable the HA Group. For more information, see K14515: The Force to Standby feature should not be used when the HA group feature is enabled, available at https://support.f5.com/csp/article/K14515.

Fix Information

Force to Standby is allowed for traffic-groups configured with HA Group scoring.

Behavior Change

Previously, traffic-group Force to Standby was disallowed if HA Groups are configured, it is now allowed.

Guides & references

K10134038: F5 Bug Tracker Filter Names and Tips