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

Last Modified: Mar 08, 2019

Bug Tracker

Affected Product:  See more info
BIG-IP vCMP(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.1, 13.1.1.2, 13.1.1.3, 13.1.1.4, 14.1.0, 14.1.0.1

Fixed In:
14.1.0.2

Opened: Feb 16, 2018
Severity: 2-Critical

Symptoms

- clusterd restarts on secondary blade - /var/log/ltm: "Management IP (<guest_management-ip>) already in use by (vcmp guest <guest_name>)"

Impact

- Secondary slot on viprion hypervisor is in "INOPERATIVE" state

Conditions

1. blade power off/on using bladectl command allows to reproduce ~80% of the time 2. not sure if this is specific to platform: - was able to reproduce easily on (B2100 - A109), - issue reproduced multiple times in cusomter environment on (B2150 - A113) - not able to reproduce with the same steps and version on 4800 (PB300) viprion

Workaround

On the VMCP Host, copy the file /shared/db/cluster.conf from the primary to all secondary cluster members. For a four slot chassis, issue this command from the primary: $ for i in 1 2 3 4; scp /shared/db/cluster.conf slot$i:shared/db/cluster.conf ; done Clusterd should then recover from the restart loop on secondary blades.

Fix Information

None

Behavior Change