Last Modified: Apr 28, 2025
Affected Product(s):
BIG-IP vCMP
Known Affected Versions:
11.4.0, 11.4.1, 11.5.0, 11.5.1, 11.5.1 HF1, 11.5.1 HF2, 11.5.1 HF3, 11.5.1 HF4, 11.5.1 HF5, 11.5.1 HF6, 11.5.1 HF7, 11.5.1 HF8, 11.5.1 HF9, 11.5.1 HF10, 11.5.1 HF11, 11.6.0, 11.6.0 HF1, 11.6.0 HF2, 11.6.0 HF3, 11.6.0 HF4, 11.6.0 HF5, 11.6.0 HF6, 11.6.0 HF7, 11.6.0 HF8, 11.6.1, 11.6.1 HF1, 11.6.1 HF2, 11.6.2, 11.6.2 HF1, 11.6.3, 11.6.3.1, 11.6.3.2
Fixed In:
12.0.0, 11.6.3.3, 11.5.2
Opened: Oct 31, 2014 Severity: 3-Major Related Article:
K16250
Mcpd restarts continuously when a new blade is inserted into a chassis running vCMP.
The newly inserted blade is unable to join the BIG-IP cluster.
This issue can occur when a vCMP guest is deployed to a blade which is then replaced as in an RMA situation or if the blade has its BIG-IP image reinstalled.
If the new blade is rebooted manually, it is able to properly cluster with the rest of the chassis after restart.
An issue has been resolved which could cause mcpd to continuously restart after a chassis blade replacement.