@nikade
It is solved.
Reinstalled the nodes since the setup is not in production yet.
Bond worked fine and the switch ports went from LACP fall back into LACP active/active.

Why is the Rolling pool update not available when using Xostor?

@nikade
It is solved.
Reinstalled the nodes since the setup is not in production yet.
Bond worked fine and the switch ports went from LACP fall back into LACP active/active.

Have the same problem.
We use LACP fallback in the switch so if the ports in the LACP not receive LACP one port goes into standard mode/non LACP. That's what is active now.

Trying to create a bond with the eth0 (currently used to manage) and eth1 but can't select bond mode.

Have also in the switch enabled native vlan that is the manage vlan.

Can the backed-up machines in Synology Active Backup for business be imported into XCP-ng and spined up as VMs?
They can be started as VMs in Synology Virtual Machine Manager.

https://www.synology.com/en-global/dsm/7.2/software_spec/abb

Some questions about XOSTOR

Storage between the servers is not shared as a large file system like Gluster. Right?
So for example, each 4 hosts has 2TB storage then the max HD space is 2TB (widely)

Is the NIC speed of the storage network important? Is 2x40G on each server for this overkill?

What software raid on the NVME disks is recommended?

/Christian

@ajpri1998
Having centralized storage sounds dangerous from the perspective of failure.
(We already have a 2PB all flash Vast storage.)

Hi, any comments about this setup?

https://www.supermicro.com/en/aplus/system/2u/2124/as-2124bt-hntr.cfm
With 3-4 nodes.
4 data NVMe and XPC-ng on SATA or M2 (raid1?).
Backend pool sync between nodes, 2x40G or 2x10G? 2 x standalone local MLAG switches. Jumbo frames?
Data from each node 2x10G to the core network.