Bug ID 882609: ConfigSync status remains 'Disconnected' after setting ConfigSync IP to 'none' and back

Last Modified: Jul 11, 2024

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

Known Affected Versions:
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, 14.1.4, 14.1.3,,,, 13.1.4,, 12.1.6,,,

Opened: Feb 19, 2020

Severity: 3-Major


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.


Devices unable to ConfigSync.


--- 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.


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


Behavior Change

Guides & references

K10134038: F5 Bug Tracker Filter Names and Tips