2 node cluster

Maher Khalil

Member
Jul 11, 2021
232
10
23
43
Hello
Can I connect 2 nodes not on the same LAN to cluster?
please note that each node has its on IP
the purpose of clustering is motioning and management and not live migration
 
You need at least 3 hosts for a cluster. And they should be at the same location/datacenter (high latency over the internet should be avoided).
 
3 hosts for high availability as per the documentation
I need only to join both nodes in 1 cluster to see them in one GUI interface
I am only getting this problem
"unable to create directory '/etc/pve/nodes' - permission denied
Please note that I use nginx on the first node which has the cluster created
 
3 hosts for high availability as per the documentation
Not only for HA. There will be no quorum when 1 of those nodes is offline, so the other one will stop working too. With just 2 voters you got a cluster where no server ever may be started/shutdown/fail. Not great if you need to reboot a host after a kernel upgrade or shutdown one node for maintaince.
 
Last edited:
I will install proxmox on virtual machine to provide 3rd node until I can physically provide new server.
Do I need a dedicated network for cluster. I will not do any migration and I will not be able to provide private network right now.
the cluster shall be required to monitor nodes only from 1 view
 
I will install proxmox on virtual machine to provide 3rd node

If this VM runs on one of your two nodes, this makes absolutely no sense, since you still lose quorum if this node is down / gets restarted...

Read the requirements:

But yeah, do what you want and gain your own experiences...
 
I am going to provide new server
my question now is:
Do I need a dedicated network for cluster. I will not do any migration , the cluster shall be required for monitor nodes only from 1 view?
do install cluster without dedicated network affect performance of system internet speed?
 
While it isn't needed, it is highly recommneded to use a dedicated NIC just for corosync communication, as corosync needs very low latency (best <1ms). If corosync shares a NIC with other traffic and you saturate your NIC (for example while doing a backup) the latency might get too high and corosync packets will have to wait resulting in a cluster that got no quorum.
 

About

The Proxmox community has been around for many years and offers help and support for Proxmox VE, Proxmox Backup Server, and Proxmox Mail Gateway.
We think our community is one of the best thanks to people like you!

Get your subscription!

The Proxmox team works very hard to make sure you are running the best software and getting stable updates and security enhancements, as well as quick enterprise support. Tens of thousands of happy customers have a Proxmox subscription. Get yours easily in our online shop.

Buy now!