@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.
Watch out if backup network isn’t configured, all of your host’s backups will be sent through the management network! The same also for migrations of VMs. Like you said a dedicated bond for HA will help, as it will keep the heavy backups, VM migrations and general storage away from this traffic.
I’d recommend that all of the servers LAN cards (especially XCP-ng hosts) have all of their Ethernet as quad ports. Will give you more than enough connections, in order to have dedicated HA, Storage, VM and management networks. Doing this may also allow for physical dedicated backup and/or migration networks, or at least a shared channel for this.