@carloum70 said:
Some update:
After removing the ip-address from eth4 the following messages disappeared
[warn] SC: (script_service_do_query_liveset) reporting "heartbeat approaching timeout". host[1].time_since_last_hb=30408.
[info] SC: (script_service_do_query_liveset) "Heartbeat approaching timeout" turned FALSE
By the way I forgot to mention that each time I enable HA the following warning appears in xha.log
Sep 29 13:31:56 CEST 2026 [warn] BM: cannot open bonding status file (/proc/net/bonding/bond0). (2)
Sep 29 13:31:56 CEST 2026 [info] BM: this is not bonded. Terminating bonding thread.
bond0 (eth2 + eth3) is the management interface and also used for the HA.
Warning: Unconfigured Backup/Migration Networks Trigger HA Reboots
Watch out if a dedicated backup or migration network is not configured in Vates VMS, all of that traffic defaults to the management network. This will especially occur on highly busy and congested instances of Vates VMS.
When massive backup jobs or VM migrations saturate the management interface, it chokes the High Availability (HA) cluster heartbeats. This network congestion causes packet loss, triggers false split-brain conditions, and forces the host into a spontaneous reboot (self-fencing). While sysctl ARP filtering patches the routing leak, it cannot fix physical network saturation.
The Long-Term Fix: Quad-Port Ethernet Upgrades
I highly recommend upgrading all server LAN cards (especially XCP-ng hosts) to quad-port modules across multiple slots or daughter cards. Abundant physical interfaces allow you to build dedicated LACP or Active-Backup bonds, ensuring complete infrastructure isolation:
• Dedicated HA & Management: Keeps critical XAPI orchestration and heartbeat checks isolated from heavy data bursts.
• Dedicated Storage: Keeps iSCSI, NFS, or XOSTOR disk I/O running smoothly on its own low-latency pipe.
• Dedicated VM Traffic: Isolates production guest network traffic from infrastructure management tasks.
• Dedicated Backup & Migration: Physical ports can be carved out exclusively for VM motions and backup windows—or at least provide a dedicated, shared channel away from HA traffic.
