sleep 5

/usr/bin/arping -U -c 10 -I eth0 Virtual_IP_1

/usr/bin/arping -U -c 10 -I eth0 Virtual_IP_2

/usr/bin/arping -U -c 10 -I eth0 Virtual_IP_3

/usr/bin/arping -U -c 10 -I eth0 Virtual_IP_4

/usr/bin/arping -U -c 10 -I eth0 Virtual_IP_5

/usr/bin/arping -U -c 10 -I eth0 Virtual_IP_6

When the cluster switches, the new master sends a gratuitous ARP packet to the network to indicate networking devices that the MAC for the IP has changed. For some reason, this kind of packetets are discarded by your switches. 

I would recommend you to play with the arping command in the new MASTER once the cluser switches doing some changes to the command 

/usr/bin/arping -A -c 2 -I eth0 Virtual_IP_1

/usr/bin/arping -A -c 2 -I eth0 Virtual_IP_2

/usr/bin/arping -A -c 2 -I eth0 Virtual_IP_3

/usr/bin/arping -A -c 2 -I eth0 Virtual_IP_4

/usr/bin/arping -A -c 2 -I eth0 Virtual_IP_5

/usr/bin/arping -A -c 2 -I eth0 Virtual_IP_6

by (send arping package in unsolicited mode -U, instead of answered mode, -A)  

/usr/bin/arping -U -c 2 -I eth0 Virtual_IP_1

/usr/bin/arping -U -c 2 -I eth0 Virtual_IP_2

/usr/bin/arping -U -c 2 -I eth0 Virtual_IP_3

/usr/bin/arping -U -c 2 -I eth0 Virtual_IP_4

/usr/bin/arping -U -c 2 -I eth0 Virtual_IP_5

/usr/bin/arping -U -c 2 -I eth0 Virtual_IP_6

You can do some troubleshooting in your switches and identify why these packets are not managed. But as I said the issue seems to be related to your network as the cluster works as expected and do the desired. 

Thanks!

I added the command in the file you told me and is updated on the other node automatically, I supposed is because of the HA configuration, but the issue is the same, the node 2 shows interfaces are up, but we lost communication to the virutal interfaces. I add a new document with the evidence, also run the command you sent last week

Did you apply the workaround I explained in my previous comment 26/02/2025 8:37 am  ? 

Add the following lines to /usr/local/skudonet/config/zlb-start (both nodes of the cluster)

/usr/bin/arping -A -c 2 -I eth0 Virtual_IP_1

/usr/bin/arping -A -c 2 -I eth0 Virtual_IP_2

/usr/bin/arping -A -c 2 -I eth0 Virtual_IP_3

/usr/bin/arping -A -c 2 -I eth0 Virtual_IP_4

/usr/bin/arping -A -c 2 -I eth0 Virtual_IP_5

/usr/bin/arping -A -c 2 -I eth0 Virtual_IP_6

Later repeat the tests and share the results with us. 

Additionally, some information is missing in the description.

-When the failover is done to node2, are the virtual interfaces configured and Up in the node2? you can check this with commands like:

ifconfig

ip route list

ip route list table table_eth0

-When the failover is done to node2 are the farms UP and running in this node2? 

if you run HTTP profiles then check if "pound" binaries are running:

ps -ef | grep pound

if you run l4xnat profiles then check if nft is loaded with the rules

nft list ruleset

This information is mandatory to let me understand if the issue is a bug in the switching or an issue in your network configuration. 

Regards!

This is the issue:

We have a cluster with 2 nodes, master (10.1.1.140), backup (10.1.1.141) and cluster (10.1.1.142), everything seems working fine, the replication and failover is working, we created 4 virtual interfaces: 

10.1.1.143

10.1.1.144

10.1.1.145

10.1.1.146

but here's the problem:

when we make the failover to the node 2 some of the virtual interfaces stop working, hence the farms also stop working and we need to make the failover back to the node 1, so we are not able to bring up that virtual intrfaces on node 2, but the weird thing is that, if we create those virtual interfaces in another LB we got, they start working.

I am a little bit lost, sorry. 

Any additional information that would help me figure out what is going on would be appreciated. 

Regards!