FWM process on one Multi-Domain Management Server is unable to establish stable communication with the FWM on the H/A peer, the processes are not receiving response from each other in time. The scenario may be verified by stopping services (# mdsstop) on MDS 2, after that there is no more flapping on MDS 1. The state of the Primary CMA remain Started and does not change.
One or more internal settings on the Secondary CMA are corrupted, either due to errors during the creation process, or corruption that occurred later on. In the above example the CMA did not seem to have a valid certificate and properly initiated SIC - even though it was possible to reset and re-initiate SIC.