We had very similar symptoms with one customer. In our case, the cluster of 2 VMCs worked properly for over a year, and suddenly there were problems.
"show lc-cluster group-membership" said on each VMC self - isolated, peer - disconected. On each VMC in the log we could see that cluster-members are continuously connected and disconnected. There were definitely no configuration changes in the WLAN environment.
After long interviews, we discovered that new Windows Server VMs were deployed to the ESX host, overbooking the host CPU.
After moving new VMs to other ESX hosts, everything worked immediately. Cluster was l2 connected, AP and user load balancig was immediately active. Without a configuration change in the VMCs.
So check RAM and CPU usage on the ESX host.
I hope it helps.
------------------------------
Regards,
Waldemar
ACCX # 1377, ACEP, ACA - Network Security
If you find my answer useful, consider giving kudos and/or mark as solution
------------------------------
Original Message:
Sent: Apr 24, 2023 05:49 AM
From: steffen_i
Subject: Aruba 8 VMC Cluster Problem
yes of course:
Also here is the output of CLI of one of the VMCs. The output from the other one is the same.
(....<NAME-of-VMC01>....) [MDC] #show lc-cluster group-membershipCluster Enabled, Profile Name = "Cluster-D..........."Redundancy Mode OnActive Client Rebalance Threshold = 50%Standby Client Rebalance Threshold = 75%Unbalance Threshold = 5%Heartbeat Threshold = 900 msecAP Load Balancing: EnabledActive AP Rebalance Threshold = 20%Active AP Unbalance Threshold = 5%Active AP Rebalance AP Count = 50Active AP Rebalance Timer = 1 minutesCluster Info Table------------------Type IPv4 Address Priority Connection-Type STATUS---- --------------- -------- --------------- ------self 10.35.xxx.xxx 128 N/A ISOLATED (Leader)peer 10.35.xxx.yyy 128 N/A DISCONNECTED(....<NAME-of-VMC01>....) [MDC] #show crypto ipsec sa peer 10.35.xxx.yyy% No active IPSEC SA for 10.35.xxx.yyy
------------------------------
Steffen
------------------------------
Original Message:
Sent: Apr 23, 2023 02:45 PM
From: DB86
Subject: Aruba 8 VMC Cluster Problem
Nothing different other than you called out about promiscuous mode, forged transmit, etc..
Excluded VLANs are VLANs that are not shared to both controllers. VLAN probes gets sent between the vMCs to check L2 reachability in order to be a L2-Connected Cluster, which offers a faster and more seamless failover when a vMC goes down. Can you share how you have the cluster service set up at the folder level and at the vMC level?
------------------------------
Dustin Burns
Lead Mobility Engineer @Worldcom Exchange, Inc.
ACCX 1271| ACMX 509| ACSP | ACDA | MVP Guru 2022-2023
If my post was useful accept solution and/or give kudos