Last Modified: Sep 13, 2023
Opened: Jul 09, 2021 Severity: 1-Blocking
-- High availability (HA) mirroring might not function correctly. -- Health monitors might fail intermittently (though this symptom is not always seen). -- Application response latency might increase slightly. -- Running 'tmctl -d blade tmm/sdaglib_hash_table' on the BIG-IP tenant shows a different sequence of values in the hash table when compared to the output of "show dag-states" in the F5OS Partition CLI. (Though the former renders the values using zero-based indexing, while the latter uses one-based indexing.)
High availability (HA) mirroring might not function correctly. Degraded application traffic.
-- VELOS chassis in use. -- High availability (HA) pair is formed using BIG-IP tenants. -- 'tmsh list cm device mirror-ip' shows a mirror-ip set for each BIG-IP. -- sys db statemirror.clustermirroring is set to 'between'.
None. To recover, set sys db statemirror.clustermirroring to 'within' and restart tmm on all slots of the affected tenant.
Fixed high availability (HA) mirroring.