Forum
Notifications
Clear all
Topic starter
25/02/2025 6:33 pm
Hi everyone.
We were working smoothly with our cluster, but we have found that memory suddenly goes up and that we needed to make a failover, but as soon as we did that some interfaces stopped working, I mean we only have 4 virutal interfaces, when working on node1 everything was ok, with the failover to node2, 2 interfaces stopped working even with an ok status, but we couldnt use the farms that were on those interfaces, Do you know what could be happening?
Thanks in advance
26/02/2025 8:37 am
Good day @rgonzaleza,
When Community Cluster switches the other node takes control activating the virtual IP configured in variable $cluster_ip, so to clarify, can you confirm if this IP is reachable (you can run ping) in the other node (new MASTER) at the moment the cluster switches?
If not, ARP broadcast packages are not allowed in your network (it is quite common to drop packets in Cloud services). If you run on-premise please allow that kind of packets.
if after a cluster switch the $cluster_ip is reachable but the other virtual IPs are not reachable then do the following:
Open the file /usr/local/skudonet/config/zlb-start and add the following line (anyway you can do this from the new MASTER for test purposes as this command announces to the network the MAC change):
/usr/bin/arping -A -c 2 -I eth0 Virtual_IP_1
I assume Virtual_IP_1 runs over eth0, if not, please change eth0 based on your config.
Repeat the line per Virtual IP.
When arping is executed ARP packages are sent to the network to announce the MAC change of Virtual_IP_1, and your switches have to update the ARP table. If not please check your network.
Any update will be welcomed.
Regards!
