Bug ID 2482505: HA (High Availability) peers are unable to connect when ConfigSync uses the management IP

Last Modified: Oct 06, 2026

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

Known Affected Versions:
17.1.3.4, 17.5.1.8, 21.0.0.3, 21.1.0.1

Fixed In:
21.1.0.2, 17.5.1.9, 17.1.3.5

Opened: Aug 24, 2026

Severity: 3-Major

Symptoms

-- HA (High Availability) peers in a device group are shown as Disconnected. -- SSL handshake failures are logged between the peer address and a device's internal TMM address. -- Errors appear in var/log/gtm similar to: err big3d[10046]: 012b300e:3: SSL Error: error:14094410:SSL routines:ssl3_read_bytes:sslv3 alert handshake failure on connection to ::ffff:127.1.1.4:58366. -- Peer certificate verification errors referring to a self-signed certificate appear in /var/log/ltm, and the connection to the CMI peer is subsequently removed. This issue has previously been reported under ID2450009 and ID2450017.

Impact

-- Configuration synchronization between HA (High Availability) peers fails. -- HA peer devices cannot connect. -- Device Group members show a Status of Disconnected. -- Configuration changes are not synchronized between devices.

Conditions

-- BIG-IP systems in an HA (High Availability) configuration. -- ConfigSync is configured to use the management IP address on both devices: -- sys db configsync.allowmanagement value enable -- management-ip is configured as the device configsync-ip

Workaround

Configure the device Config Sync address to use a self IP, not the device's Management IP.

Fix Information

HA (High Availability) peers connect successfully and Config Sync succeeds when the device's Management IP is configured as the device Config Sync address.

Behavior Change

Guides & references

K10134038: F5 Bug Tracker Filter Names and Tips