Bug ID 1014361: Config sync fails after provisioning APM or changing BIG-IP license

Last Modified: Apr 26, 2024

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

Known Affected Versions:,,, 13.1.4,, 13.1.5,,,,,, 14.1.3,, 14.1.4,,,,,,, 14.1.5,,,,,, 15.1.0,,,,,, 15.1.1, 15.1.2,, 15.1.3,, 15.1.4,, 15.1.5,, 15.1.6,, 15.1.7, 15.1.8,,, 15.1.9,, 15.1.10,,,, 16.1.0, 16.1.1, 16.1.2,,, 16.1.3,,,,,, 16.1.4,,,, 17.0.0,,, 17.1.0,,,, 17.1.1,,,

Opened: Apr 26, 2021

Severity: 2-Critical


Clustered high availability (HA) devices cannot establish ConfigSync connection, and the prompt status reports disconnected. MCPD is logging a message similar to this repeatedly, even though all TMMs are up and running: err mcpd[4247]: 0107142f:3: Can't connect to CMI peer, TMM outbound listener not yet created


BIG-IP devices are not able to perform ConfigSync operations.


This can occur under either of the following conditions: -- Some provisioning operations (i.e. provisioning APM), when TMM restarts during the provisioning. This has primarily been seen with BIG-IP instances running in Google Cloud. -- Changing the license of a BIG-IP VE when the new license changes the number of TMM instances that will run on the BIG-IP (i.e. upgrading from a 1Gbps to 3Gbps VE license)


Restart MCPD on the affected system. Note: This will disrupt traffic while system services restart.

Fix Information


Behavior Change

Guides & references

K10134038: F5 Bug Tracker Filter Names and Tips