Bug ID 707013: vCMP host secondary member's cluster.conf file may replaced by that of vCMP guest

Last Modified: Jul 12, 2023

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

Known Affected Versions:
13.1.0,,,,,,,,, 13.1.1,,,, 14.0.0,,,,,, 14.0.1, 14.1.0,

Fixed In:

Opened: Feb 16, 2018

Severity: 2-Critical


-- clusterd restarts on secondary blade. -- Messages similar to the following are logged in each secondary blade's /var/log/ltm file as clusterd restarts: Management IP (<guest_management_ip>) already in use by (vcmp guest <guest_name>) -- Messages similar to the following are logged in the primary blade's /var/log/ltm file when clusterd restarts on a secondary blade: notice clusterd[3676]: 013a0006:5: Hello from slot 1. notice clusterd[3676]: 013a0006:5: Informing MCP about slot ID 1 member status. notice clusterd[3676]: 013a0006:5: Goodbye from slot 1.


Secondary slot on VIPRION hypervisor is in 'INOPERATIVE' state.


-- Power-cycling a blade reproduces the issue most of the time. -- Possibly specific to platform: + This issue has been seen multiple hardware platforms, including B2100, B2150, B2250, and PB300. + Issue does not reproduce under the same conditions on a VIPRION 4800.


On the vCMP Host, copy the file /shared/db/cluster.conf from the primary to each secondary cluster members. For each secondary blade's slot, use a command similar to the following: scp /shared/db/cluster.conf slot<slot number>:/shared/db/cluster.conf Note: Implementing the workaround does not prevent the issue from recurring. An upgrade to an unaffected version is recommended.

Fix Information


Behavior Change

Guides & references

K10134038: F5 Bug Tracker Filter Names and Tips