Bug ID 565534: Some failover configuration items may fail to take effect

Last Modified: Sep 13, 2023

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

Known Affected Versions:
11.5.1 HF1, 11.5.1 HF2, 11.5.1 HF3, 11.5.1 HF4, 11.5.1 HF5, 11.5.1 HF6, 11.5.1 HF7, 11.5.1 HF8, 11.5.1 HF9, 11.5.1 HF10, 11.5.1 HF11, 11.5.2 HF1, 11.5.3 HF1, 11.5.3 HF2, 11.5.4 HF1, 11.2.1, 11.4.0, 11.4.1, 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.1.1 HF1, 12.1.1 HF2, 12.1.2 HF1, 12.1.2 HF2

Fixed In:
12.1.0, 12.0.0 HF3, 11.6.1 HF1, 11.5.4 HF2

Opened: Jan 04, 2016

Severity: 3-Major

Related Article: K40254066

Symptoms

These symptoms apply to version 12.0.0 and later: When only multicast failover is configured, traffic-groups are active on all devices in the device-group. If unicast failover is also configured, the traffic-group unexpectedly switches to a different device. These symptoms can occur on all versions: When the unicast address list is changed at the same time as other device properties, sod (the failover daemon) may fail to recognize one of the other changes.

Impact

When only multicast failover is configured, traffic-groups may become active on all devices in the device-group. If unicast failover is also configured, the traffic-group might switch to a different device.

Conditions

For version 12.0.0 and later: Multicast failover is configured and the system loads the configuration from the configuration files. For example during the first boot of a new boot location, or after performing the procedure in K13030: Forcing the mcpd process to reload the BIG-IP configuration https://support.f5.com/csp/article/K13030. For all versions: A change is made to the cm device configuration that includes a unicast-address change along with something else.

Workaround

Mitigation for v12.0.0 (and later) symptom: To restore multicast failover, disable and re-enable multicast failover. To do so, perform the following procedure on the the local device. 1. Determine which interface is being used for multicast failover by running the following tmsh command: list cm device device1 multicast-interface. 3. Disable and re-enable multicast failover by running the following tmsh commands: modify cm device device1 { multicast-interface none }. modify cm device device1 { multicast-interface eth0 }. Mitigation for all versions symptoms: Do not make cm device unicast-address changes simultaneously with changes to other cm device properties.

Fix Information

With the fix, sod now sends out multicast FO heartbeat datagrams under the same condition.

Behavior Change

Guides & references

K10134038: F5 Bug Tracker Filter Names and Tips