redundant qdevice network

[Waldo]

I have following setup - 2 node cluster with qdevice.

For cluster I configured 2 networks for redundancy:
1 - fast network over Wireguard
2 - slow backup network
Currently my qdevice is only at fast Wireguard network.

Is that possible to configure redundant network for qdevice?

If that is not possible can I move qdevice to network with lower priority?

 

[Johannes S]

Why do you have a fast network via wireguard? With a local network a direct connection will je faster than wg.

 

[SteveITS]

possible to configure redundant network for qdevice

AFAICT, no, it is designed to not be as latency sensitive. It can be a remote IP, it just needs to be able to communicate/vote: https://forum.proxmox.com/threads/qdevice-deployment.173182/post-805609

I'm guessing your two nodes are not in the same location? What is the latency over the Wireguard VPN?

 

[Waldo]

Yes, my nodes are in different locations. They are interconnected by fast, low latency (below 1ms) public network. Since network is public, all traffic goes via wireguard tunnel.

Primary network access is handled by virtual firewall VMs running on each node. Also I use my cluster network for replication and live migration.

Backup network is done via small physical hardware routers using different network connection (latency 2-3 ms). They can handle cluster traffic but are too slow for replication/migration.

This setup works very well except when I reboot my nodes. After reboot to start wireguard tunnel I need to start firewall VM which fails due to lack of quorum. This made me think if I can make QDevice network redundant. In case that is not possible can I put QDevice on network with lower priority?

 

[UdoB]

can I put QDevice on network with lower priority?

Higher latency?

I've tested this some weeks ago. While that is not recommended, it worked fine in my test: https://forum.proxmox.com/threads/qdevice-deployment.173182/post-805735