BugZero | F5 BugID 882609 - ConfigSync status remains 'Disconnected' after set...

F5 - Defect ID: 882609

ConfigSync status remains 'Disconnected' after setting ConfigSync IP to 'none' and back

F5 - Defect ID: 882609

ConfigSync status remains 'Disconnected' after setting ConfigSync IP to 'none' and back

Last updated on February 27th, 2026

BugZero Risk Score
6.9 Medium

Overall: 6.9

Severity: 7.3

Community: 4.2

Lifecycle: 8.7

What is the BugZero Risk Score?

F5 Integration

Learn more about where this data comes from

F5 Integration

Learn more

BugZero Plan

Streamline upgrades with automated vendor bug scrubs

BugZero Plan

Learn more

BugZero Prevent

Wish you caught this bug sooner? Get proactive today.

BugZero Prevent

Learn more

Bug Details

Priority: 3-Major
Status: Resolved
Impact Category: TMOS
Views: 6

Description

Symptoms

After setting a device's ConfigSync IP to 'none' and then back to an actual IP address, the device remains in a disconnected state, and cannot establish ConfigSync connections to other BIG-IP systems in its trust domain. MCPD periodically logs messages in /var/log/ltm: err mcpd[27610]: 0107142f:3: Can't connect to CMI peer a.b.c.d, TMM outbound listener not yet created.

Impact

Devices unable to ConfigSync.

Conditions

--- BIG-IP system is in a trust domain with other BIG-IP systems. --- Local device's ConfigSync IP is set to 'none', and then back to an actual IP address.

Workaround

This workaround will disrupt traffic while TMM restarts: 1. Ensure the local ConfigSync IP is set to an IP address. 2. Restart TMM: bigstart restart tmm This workaround should not disrupt traffic: Copy and paste the following command into the Advanced Shell (bash) on a BIG-IP system, and then run it. This sets the ConfigSync IP for all device objects to 'none', and then back to their correct values. TMPFILE=$(mktemp -p /var/tmp/ ID882609.XXXXXXX); tmsh -q list cm device configsync-ip > "$TMPFILE"; sed 's/configsync-ip .*$/configsync-ip none/g' "$TMPFILE" > "$TMPFILE.none"; tmsh load sys config merge file "$TMPFILE.none"; echo "reverting back to current"; tmsh load sys config merge file "$TMPFILE"

Fix Information

None

Change history

2026-02-27 Added: 21.0.0, 17.5.1, 17.5.0, 17.1.2, 17.1.1, 17.1.0

2025-12-31 Added: 11.6.5.3, 12.1.5.3, 13.1.3.5, 13.1.3.6, 13.1.4.1, 13.1.5, 13.1.5.1, 14.1.2.8, 14.1.3.1, 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.2.1, 15.1.3.1, 15.1.4.1, 15.1.5.1, 15.1.6.1, 15.1.8.1, 15.1.8.2, 15.1.9, 15.1.9.1, 15.1.10, 15.1.10.2, 15.1.10.3, 15.1.10.4, 15.1.10.5, 15.1.10.6, 15.1.10.7, 15.1.10.8, 16.0.0.1, 16.0.1.1, 16.0.1.2, 16.1.1, 16.1.2, 16.1.2.1, 16.1.2.2, 16.1.3, 16.1.3.1, 16.1.3.2, 16.1.3.3, 16.1.3.4, 16.1.3.5, 16.1.4, 16.1.4.1, 16.1.4.2, 16.1.4.3, 16.1.5, 16.1.5.1, 16.1.5.2, 16.1.6, 16.1.6.1, 17.0.0.1, 17.0.0.2, 17.1.0, 17.1.0.1, 17.1.0.2, 17.1.0.3, 17.1.1, 17.1.1.1, 17.1.1.2, 17.1.1.3, 17.1.1.4, 17.1.2, 17.1.2.1, 17.1.2.2, 17.1.3, 17.5.0, 17.5.1, 17.5.1.2, 17.5.1.3, 21.0.0

2025-12-31 Added: 21.0.0, 17.5.1, 17.5.0, 17.1.2, 17.1.1, 17.1.0

2025-11-29 Added: 21.0.0, 17.5.1, 17.5.0, 17.1.2, 17.1.1, 17.1.0

2025-11-15 Added: 21.0.0, 17.5.1, 17.5.0, 17.1.2, 17.1.1, 17.1.0

2025-11-15 Added: 11.6.5.3, 12.1.5.3, 13.1.3.5, 13.1.3.6, 13.1.4.1, 13.1.5, 13.1.5.1, 14.1.2.8, 14.1.3.1, 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.2.1, 15.1.3.1, 15.1.4.1, 15.1.5.1, 15.1.6.1, 15.1.8.1, 15.1.8.2, 15.1.9, 15.1.9.1, 15.1.10, 15.1.10.2, 15.1.10.3, 15.1.10.4, 15.1.10.5, 15.1.10.6, 15.1.10.7, 15.1.10.8, 16.0.0.1, 16.0.1.1, 16.0.1.2, 16.1.1, 16.1.2, 16.1.2.1, 16.1.2.2, 16.1.3, 16.1.3.1, 16.1.3.2, 16.1.3.3, 16.1.3.4, 16.1.3.5, 16.1.4, 16.1.4.1, 16.1.4.2, 16.1.4.3, 16.1.5, 16.1.5.1, 16.1.5.2, 16.1.6, 16.1.6.1, 17.0.0.1, 17.0.0.2, 17.1.0, 17.1.0.1, 17.1.0.2, 17.1.0.3, 17.1.1, 17.1.1.1, 17.1.1.2, 17.1.1.3, 17.1.1.4, 17.1.2, 17.1.2.1, 17.1.2.2, 17.1.3, 17.5.0, 17.5.1, 17.5.1.2, 17.5.1.3, 21.0.0

2025-11-11 Added: 21.0.0, 17.5.1, 17.5.0, 17.1.2, 17.1.1, 17.1.0

2025-04-28 Added: 17.0.0, 16.1.0, 16.0.1, 16.0.0, 15.1.8, 15.1.7, 15.1.6, 15.1.5, 15.1.4, 15.1.3, 15.1.2, 15.1.1, 15.1.0.5, 15.1.0.4, 15.1.0.3, 15.1.0.2, 15.1.0.1, 15.1.0, 14.1.4, 14.1.3, 14.1.2.7, 14.1.2.6, 14.1.2.5, 13.1.4, 13.1.3.4, 12.1.6, 12.1.5.2, 12.1.5.1, 11.6.5.2

Relevant Products

Click on a version to see all relevant bugs

Affected versions:21.0.0, 17.5.1, 17.5.0, 17.1.2, 17.1.1, 17.1.0, 17.0.0, 16.1.0, 16.0.1, 16.0.0, 15.1.8, 15.1.7, 15.1.6, 15.1.5, 15.1.4, 15.1.3, 15.1.2, 15.1.1, 15.1.0.5, 15.1.0.4, 15.1.0.3, 15.1.0.2, 15.1.0.1, 15.1.0, 14.1.4, 14.1.3, 14.1.2.7, 14.1.2.6, 14.1.2.5, 13.1.4, 13.1.3.4, 12.1.6, 12.1.5.2, 12.1.5.1, 11.6.5.2

Fixed versions: No known fixed versions

Relevant Products

Click on a version to see all relevant bugs

Fixed versions: No known fixed versions

Top F5 Defects

9.7Defect ID: 1505789
VPN connection fails with Edge client 7.2.4.6 with error "Network is vulnerable"
9.4Defect ID: 1785385
Intermittent traffic failures when tenant is running BIG-IP v17.1.2 or above and host is on version prior to F5OS-A 1.8.0 or F5OS-C 1.8.0
9.4Defect ID: 2292013
Admin users cannot create or view virtual servers and other objects in non-Common partitions in TMUI
9.4Defect ID: 2291757
Cannot login through ssh or console after upgrading to 17.5.1.6
9.4Defect ID: 970269
Install fails as lind keeps failing due to "Fatal error: block id new probe failed - device file:/dev/cdrom"

Ready to prevent the next vendor outage?

Get a demo

F5 - Defect ID: 882609

ConfigSync status remains 'Disconnected' after setting ConfigSync IP to 'none' and back

F5 - Defect ID: 882609

ConfigSync status remains 'Disconnected' after setting ConfigSync IP to 'none' and back

Last updated on February 27th, 2026

BugZero Risk Score6.9 Medium

Bug Details

Symptoms

Impact

Conditions

Workaround

Fix Information

Top F5 Defects

Ready to prevent the next vendor outage?

Links

BugZero Risk Score
6.9 Medium