Bug ID 1447389: Dag context may not match the current cluster state

Last Modified: Sep 18, 2024

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

Fixed In:
17.1.1.2

Opened: Dec 13, 2023

Severity: 3-Major

Symptoms

When the cluster state changes during synchronization of dag context in a HA pair, dag context may not match the current cluster state. This is a rare-occurance problem and happens only during frequent updates of the cluster state.

Impact

- one blade is not present in the dag context

Conditions

- HA pair is configured, the system role is the next-active - The cluster state changes during the synchronization of the dag state.

Workaround

Restart TMM

Fix Information

Fixed an error that leads to a dag context not matching the current cluster state.

Behavior Change

Guides & references

K10134038: F5 Bug Tracker Filter Names and Tips