Operational Defect Database
BugZero found this defect 1068 days ago.
Data sources
All data on this page is proprietary to BugZero® or gathered from public sources
F5 | 1014361
Config sync fails after provisioning APM or changing BIG-IP license
Last update date:
4/26/2024
Affected products:
BIG-IP
BIG-IP APM
BIG-IP TMOS
Affected releases:
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
14.1.2.5
14.1.2.6
14.1.2.7
14.1.2.8
14.1.3
Fixed releases:
No fixed releases provided.
Description:
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) ... Restart MCPD on the affected system. ... Note: This will disrupt traffic while system services restart. ... Fix Information
