Last Modified: Dec 07, 2023
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, 15.1.0, 15.1.0.1, 15.1.0.2, 15.1.0.3, 15.1.0.4, 15.1.0.5, 15.1.1, 15.1.2, 15.1.2.1, 15.1.3, 15.1.3.1, 15.1.4, 15.1.4.1, 15.1.5, 15.1.5.1, 15.1.6, 15.1.6.1, 15.1.7
Fixed In:
17.1.0, 15.1.8
Opened: Apr 12, 2022 Severity: 2-Critical
There might be problems in DAG context synchronization in high availability (HA) mirroring on VELOS platform. The problem can be observed as a long sequence of logs similar to: notice SDAG CDP: Selected DAG state from primary PG 0 for CMP state 07 with clock 4622
Traffic is disrupted when failover occurs.
-- An high availability (HA) pair is setup -- The problem is currently known to manifest itself particularly for tenants with 3 blades.
-- The system should eventually heal itself after up to a few minutes -- Force a high availability (HA) reconnect, for example by modifying sys db statemirror.clustermirroring to "within" then back to "between".
Fixed DAG context synchronization problem in high availability (HA) mirroring on VELOS platforms.