Proxmox Cluster Over Pfsense Ovpn

knicos

New Member
Feb 11, 2017
4
0
1
38
Hoping someone would be able to assist,

I'm trying to configure a 3 node cluster, 2 nodes on the same physical network, and another node remotely.

this other node sits behind a Pfsense firewall that has a site-to-site vpn connection to my pfsense router.

i'm able to cluster the first two nodes, but have an issue with the 3rd node (remote node), i think it has something to do with the multicast as i get the "waiting for quorom" time out issue when trying to add the 3rd node.

i even tried the unicast method for clustering, but failed. any suggestions ?
 
Yes, it is due to multicast. You need a solution that allows multicast to pass through your tunnel.

Once you have that done, you also need a low latency connection between your cluster and your remote nodes. Else you might have issues of "node-flapping" which gets annoying fast.

We do currently have multi Datacenter proxmox clusters in production at work, the latency is never more than 15 ms tho.
The last time I did something like this (using larger latencies) was using proxmox 3.x, a hetzner, a french OVH and a Canadian OVH server and it was most terrible.
 
Yes, it is due to multicast. You need a solution that allows multicast to pass through your tunnel.

Once you have that done, you also need a low latency connection between your cluster and your remote nodes. Else you might have issues of "node-flapping" which gets annoying fast.

We do currently have multi Datacenter proxmox clusters in production at work, the latency is never more than 15 ms tho.
The last time I did something like this (using larger latencies) was using proxmox 3.x, a hetzner, a french OVH and a Canadian OVH server and it was most terrible.


thabks for making that clear, I was able to resolve this by getting multicast working over the OVPN, now facing some other issues with NFS where my Remote node (accessed over VPN) loosing connection to our internal network (where the NFS server lives) and it becomes locked out until I reboot that node. can these settings be modified so that if there is any connection lost to the NFS share, Node DO NOT get locked out ? Or at the very least is there a service I might be able to restart on the node as opposed to restarting the node entirely ? Thanks in advanced