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

Last Modified: Jan 06, 2023

Bug Tracker

Affected Product:  See more info
BIG-IP APM, TMOS(all modules)

Known Affected Versions:
13.1.0, 13.1.0.1, 13.1.0.2, 13.1.0.3, 13.1.0.4, 13.1.0.5, 13.1.0.6, 13.1.0.7, 13.1.0.8, 13.1.1, 13.1.1.2, 13.1.1.3, 13.1.1.4, 13.1.1.5, 13.1.3, 13.1.3.1, 13.1.3.2, 13.1.3.3, 13.1.3.4, 13.1.3.5, 13.1.3.6, 13.1.4, 13.1.4.1, 13.1.5, 13.1.5.1, 15.1.0, 15.1.0.1, 15.1.0.2, 15.1.0.3, 15.1.0.4, 15.1.0.5, 15.1.1, 15.1.2, 15.1.2.1, 15.1.3, 15.1.3.1, 15.1.4, 15.1.4.1, 15.1.5, 15.1.5.1, 15.1.6, 15.1.6.1, 15.1.7, 15.1.8, 15.1.8.1

Opened: Apr 26, 2021
Severity: 2-Critical

Symptoms

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 192.0.2.1, TMM outbound listener not yet created

Impact

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

Conditions

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)

Workaround

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

Fix Information

None

Behavior Change