Hi, We have similar problem whith cluster in Version 3.2.4. (Already opened a case)
Records like this in cluster logs:
"PAM-CM-0451: ServerReachabilityMonitor.run Server '***.***.***.***' reachability changed: 443=<removed> (filtered), 3306=<removed> (filtered), 5900=<removed> "
Finally at any time, we don´t know , the cluster gets down.
As a work around, CA technologies Techinician has change the next parameter : Configuration/Clustering/tuning/Max number of...from 10000 to 20000
But still going down sudenly.
I´ll tell you all if it gets solved